Hour audit: 2026-09-17T03
back to the files for this hour · how the archive is audited
Every number on this page is a stored measurement read from this hour's own records: its
manifest.json, its witness
statistics sidecar, and the corpus attestation. Nothing here is computed from the served
bytes at the time you load the page, so no line below claims the bytes are correct. The
digest and the one command that checks them are printed instead.
No findings
Every check that could be evaluated for this hour passed. That is not the same as the hour being perfect: it means the records this archive keeps about it agree with each other and with the corpus ledger.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-17T03 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-17T03:00:00.000011926+00:00 · last event 2026-09-17T03:59:59.999988744+00:00
VOLUME 120,253,837 rows · 1,250,606,650 bytes (1.16 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 119,110,669 · e: 119,109,377 · f: 114,541,624 · c: 114,333,446 · g: 109,565,226 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 9,880,244 (8.22%) · e: 674,968 (0.56%) · f: 557,613 (0.46%) · c: 108,588,045 (90.30%) · g: 552,967 (0.46%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 120,253,837 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 62bbb47a942aa49de77fc30e081a2412ea6d0c118277c39fe401674d1b76dd60
the corpus checksum ledger names this file with the same digest
joined 120,261,198 to merged 120,253,837, minus 7,361 (minus 0.0061%)
boundary drops 7,361 · guard cache
SIDECARS none: this hour's manifest has no v31 key. The v3.1 sidecars are optional, and hours before them have none
MARKETS not measured (the per-hour market census runs on the capture host and its output is not published per hour)
HISTORY merged 2026-09-17T05:00:07Z as cefgh
layout union-event-sorted-v1
re-merges not measured (the merge ledger records the merge that produced this file, not the history of attempts)
supersessions not measured (supersession is recorded per corpus in the storage registry, not in the hour manifest)
CHECKS 8/8 pass
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
PASS every expected machine contributed
PASS the checksum ledger names this file
PASS the hour is whole
PASS a boundary guard ran
UPSTREAM our incident register was checked against the venue's own status feed at 2026-09-23T20:35Z and names no event in this hour. That is a statement about what they published, not a check that every message they sent reached us.The words in this report
Each line in the CHECKS block states what was found, not what was
hoped for: a check that passes is named for the thing that is true, and a check that does
not is renamed to the thing that is wrong. So FINDING never sits beside a
sentence asserting the opposite of the one below it.
The report above is fixed-width text, so nothing in it can be clicked. The same terms are linked here instead. Its verdict is a statement about minutes and nothing else. The row it reports comes from this hour's own manifest and its witness-statistics sidecar, and the completeness line comes from the corpus attestation. The gap between the joined and merged counts is deduplication, not loss, and the boundary drops are the duplicates discarded at the seam with the hour before. Where the history line names a supersession, this hour was rebuilt to a better state after it was first published. The precision is the timestamp resolution these files carry.
Detail
The same records, per product. A product holding no rows renders its zero rather than
being dropped: dropped and empty are indistinguishable to a reader, and only one of them is
a defect. A cell reading not meas. is one nothing published, which is a third
thing again and never a zero.
The class column is the merger's own verdict for that product, and it is
keyed to CONTRIBUTION rather than presence. FULL means every machine expected to
be capturing this hour delivered rows for that product; PARTIAL means some did
and some did not; SINGLE-BY-DESIGN means only one machine was ever expected, and
SINGLE-BY-DEFECT means several were and one delivered. So PARTIAL
here is a statement about the fleet, not about the product being damaged or truncated: the
rows that are present are whole.
PRODUCT rows bytes row groups sha256 best_bid_ask 14,045,215 153,066,047 0-53 934b3054a6a1c91fb06be86806a72b5311870cbd877512002454f7763c708491 book 1,311,575 82,344,915 54-59 e2b6c75f8bfd891657a00f4d2fd629ade05be74404de6321bf5cc37d2c909189 last_trade_price 46,078 2,590,351 60-60 8fa62f093f3297dcfd3bf550595201ab920d65d736f5a987d11e95e4a17779af market_resolved 2,122 315,422 61-61 af23e3625103ce5619b69026549a06a95e76c674cdb06b3fbdc576636e857f3b new_market 585 66,710 62-62 db58c2b0860645e9cd33e45c5703c45c0d4e7f96d0a124f339caad203dca0c08 price_change 104,841,982 1,010,626,401 63-462 e983b26ce913bb8c2b09daba73b816b766520e6bad7ba5ae6cf8f7ccc371b736 tick_size_change 6,280 228,913 463-463 216971fc6e15d980c14734273ff131883c78dcd788de5b74e98a4ffeadd9f13d EVENT MIX count share price_change 104,841,982 87.18% best_bid_ask 14,045,215 11.68% book 1,311,575 1.09% last_trade_price 46,078 0.04% tick_size_change 6,280 <0.01% market_resolved 2,122 <0.01% new_market 585 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 14,045,564 14,045,215 349 1,657 FULL book 1,315,975 1,311,575 4,400 149,659 FULL last_trade_price 46,078 46,078 0 220 FULL market_resolved 2,122 2,122 0 195 FULL new_market 585 585 0 1 FULL price_change 104,844,594 104,841,982 2,612 221 FULL tick_size_change 6,280 6,280 0 200 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 13,471,568 12,893,868 4ms 10ms 76ms 2.3s 0 transport_latency_assumed best_bid_ask e 14,041,997 54,459 37ms 44ms 127ms 7.5s 0 transport_latency_assumed best_bid_ask f 13,462,995 16,516 45ms 54ms 158ms 4.1s 0 transport_latency_assumed best_bid_ask g 12,857,831 3,707 80ms 97ms 240ms 12.5s 0 transport_latency_assumed best_bid_ask h 14,041,828 1,076,665 17ms 24ms 92ms 10.2s 0 transport_latency_assumed book c 514,048 279,957 2.6min 1.2d 36.4d 110.2d 0 book_staleness book e 241,001 86,145 25.0s 50.5min 25.6d 110.2d 0 book_staleness book f 501,630 344,700 2.8min 1.1d 36.4d 110.2d 0 book_staleness book g 845,523 489,398 3.8min 2.5d 36.4d 110.2d 0 book_staleness book h 259,709 111,375 35.2s 1.2h 25.6d 110.2d 0 book_staleness last_trade_price c 42,853 40,268 10ms 46ms 194ms 4.8s 0 transport_latency_assumed last_trade_price e 45,866 446 44ms 100ms 438ms 7.7s 0 transport_latency_assumed last_trade_price f 43,911 173 52ms 112ms 438ms 4.9s 0 transport_latency_assumed last_trade_price g 41,785 41 91ms 190ms 753ms 12.5s 0 transport_latency_assumed last_trade_price h 45,755 5,150 23ms 64ms 240ms 6.7s 0 transport_latency_assumed market_resolved c 1,948 1,860 5ms 19ms 5.4min 5.9min 0 transport_latency_assumed market_resolved e 1,952 9 109ms 160ms 415ms 658ms 0 transport_latency_assumed market_resolved f 1,886 12 117ms 144ms 525ms 5.1min 0 transport_latency_assumed market_resolved g 1,899 121 203ms 344ms 5.1min 6.3min 0 transport_latency_assumed market_resolved h 1,952 120 36ms 56ms 141ms 2.4s 0 transport_latency_assumed new_market c 437 340 38ms 219ms 4.2min 44.2min 0 transport_latency_assumed new_market e 435 31 134ms 369ms 35.9s 12.8min 0 transport_latency_assumed new_market f 435 57 139ms 14.3s 6.5min 53.8min 0 transport_latency_assumed new_market g 437 50 185ms 14.6s 10.2min 2.2h 0 transport_latency_assumed new_market h 435 107 64ms 20.9s 54.4s 12.8min 0 transport_latency_assumed price_change c 100,296,532 95,366,156 5ms 12ms 105ms 2.6s 0 transport_latency_assumed price_change e 104,771,846 533,874 37ms 49ms 214ms 7.6s 0 transport_latency_assumed price_change f 100,524,859 196,154 45ms 60ms 257ms 4.1s 0 transport_latency_assumed price_change g 95,811,687 59,650 80ms 102ms 365ms 12.5s 0 transport_latency_assumed price_change h 104,754,710 8,686,148 17ms 28ms 141ms 10.3s 0 transport_latency_assumed tick_size_change c 6,060 5,596 5ms 12ms 51ms 299ms 0 transport_latency_assumed tick_size_change e 6,280 4 38ms 115ms 418ms 540ms 0 transport_latency_assumed tick_size_change f 5,908 1 45ms 51ms 110ms 148ms 0 transport_latency_assumed tick_size_change g 6,064 not meas. 79ms 93ms 146ms 250ms 0 transport_latency_assumed tick_size_change h 6,280 679 17ms 22ms 55ms 108ms 0 transport_latency_assumed
Captured and supplied are different numbers
Captured is how many rows each machine's own feed carried. Redundant capture means these OVERLAP, heavily and on purpose, so they do not partition the file and their sum is larger than it. Two machines each capturing nearly every event is the archive working, not double counting.
Supplied is how many rows of the merged file actually came from that machine. This one does partition: it sums to the file's row count exactly. But it is decided by the merge's tie-break, so a machine can capture almost everything and supply almost nothing. Read alone, either number tells a false story about the fleet, which is why both are printed and neither is called "the witness share".
What the skew columns mean
Arrival skew is the receipt timestamp minus the venue timestamp, in milliseconds. For six of the seven products the sidecar interprets it as transport latency, and marks that interpretation assumed: it rests on the venue timestamp being emit time, which we cannot verify from outside.
book is not latency and must not be read as latency. Its
venue timestamp is the last time the book changed, so the sidecar interprets it as book
staleness and warns in its own note that large values mean a quiet book rather than slow
transport. Its maximum runs to weeks for that reason. This is why the table above gives a
row per product per machine and never one figure for the hour: percentiles do not average,
and these seven do not measure the same quantity.
Check it yourself
The digest above is a claim. This is how you refuse to take our word for it:
curl -O https://archive.pendulumflow.com/v3/2026-09-17/03/2026-09-17T03.parquet sha256sum 2026-09-17T03.parquet # compare with the sha256 line in the report above
A range digest certifies bytes. That those bytes are the product the manifest names comes from the manifest, which is why both are published and both are checkable.