Hour audit: 2026-09-25T09
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-25T09 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-25T09:00:00.000012164+00:00 · last event 2026-09-25T09:59:59.999820373+00:00
VOLUME 125,538,182 rows · 1,355,515,829 bytes (1.26 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured i: 124,313,076 · k: 124,306,394 · c: 118,706,301 · h: 114,490,768 · g: 111,001,729 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 1,523,880 (1.21%) · k: 12,129,577 (9.66%) · c: 109,223,061 (87.00%) · h: 2,477,917 (1.97%) · g: 183,747 (0.15%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 125,538,182 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 9ba05b33907658ca24f958fff307fa39a608418f98035cc8a901f66d02e674cc
the corpus checksum ledger names this file with the same digest
joined 125,540,448 to merged 125,538,182, minus 2,266 (minus 0.0018%)
boundary drops 2,266 · 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-25T11:48:15Z as cghik
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 status feed unobserved for this hour. Our incident register was last checked against the venue's feed at 2026-09-23T20:35Z, before this hour ended, so nothing has looked yet. This is a could-not-look and never an all-clear.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 12,272,410 142,557,617 0-46 6cc0c2959c1973fc545d62a2c1fbbbeefe2546b342717f4dad4a06432c378482 book 1,278,557 77,551,913 47-51 d7e05d22022ec49d4667e7564a186f93fdac539c5957eb597956803e61014ce5 last_trade_price 51,224 2,917,369 52-52 d9f0f19da9f9743d4393fd44c8a71a91451fbbc852281950a4faeb0e480fbc4d market_resolved 622 81,857 53-53 42fb889bd55ef14323a7995a90c5419e165c8cef758e31c3e0420d330590da07 new_market 837 77,861 54-54 ed1400f88d2eb075c01e3baa099e155dff374d4bcef9a6b106abd34539cf6ecb price_change 111,932,160 1,130,815,527 55-481 72fe775a137a8ad3e0f490fcd1ef74deb656a04e9dbee2bdbdacf4ed3ea8391c tick_size_change 2,372 88,054 482-482 04539bb8dfbc4e90ec7d4bbb80b7d935be00991d5dec6a5d96ce1fd4b2c2d23c EVENT MIX count share price_change 111,932,160 89.16% best_bid_ask 12,272,410 9.78% book 1,278,557 1.02% last_trade_price 51,224 0.04% tick_size_change 2,372 <0.01% new_market 837 <0.01% market_resolved 622 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,272,682 12,272,410 272 2,958 FULL book 1,278,589 1,278,557 32 207,261 FULL last_trade_price 51,224 51,224 0 352 FULL market_resolved 622 622 0 17 FULL new_market 837 837 0 0 FULL price_change 111,934,122 111,932,160 1,962 2,475 FULL tick_size_change 2,372 2,372 0 95 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,726,481 10,886,220 5ms 12ms 85ms 7.0s 0 transport_latency_assumed best_bid_ask g 11,013,530 381 79ms 98ms 257ms 11.1s 0 transport_latency_assumed best_bid_ask h 11,138,568 138,413 19ms 36ms 113ms 6.5s 0 transport_latency_assumed best_bid_ask i 12,271,129 129,473 21ms 28ms 101ms 4.3s 0 transport_latency_assumed best_bid_ask k 12,271,070 1,117,923 12ms 20ms 85ms 5.6s 0 transport_latency_assumed book c 521,305 250,610 5.4min 3.6d 33.8d 118.5d 0 book_staleness book g 590,414 173,116 7.5min 3.6d 36.8d 118.5d 0 book_staleness book h 932,858 837,873 7.8min 4.1d 40.8d 118.5d 0 book_staleness book i 105,837 3,486 23ms 118ms 37.8min 100.0d 0 book_staleness book k 107,043 13,472 15ms 64ms 11.9h 99.9d 0 book_staleness last_trade_price c 48,075 43,300 6ms 22ms 153ms 1.4s 0 transport_latency_assumed last_trade_price g 44,445 26 83ms 305ms 4.7s 11.0s 0 transport_latency_assumed last_trade_price h 46,934 1,052 20ms 57ms 289ms 6.2s 0 transport_latency_assumed last_trade_price i 50,958 861 22ms 74ms 786ms 3.9s 0 transport_latency_assumed last_trade_price k 50,947 5,985 13ms 36ms 218ms 1.2s 0 transport_latency_assumed market_resolved c 499 462 5ms 65ms 4.8min 5.8min 0 transport_latency_assumed market_resolved g 487 16 90ms 53.9s 8.0min 9.4min 0 transport_latency_assumed market_resolved h 509 60 25ms 5.0min 11.1min 11.3min 0 transport_latency_assumed market_resolved i 494 49 22ms 113ms 48.3s 48.3s 0 transport_latency_assumed market_resolved k 494 35 13ms 43ms 28.8s 54.4s 0 transport_latency_assumed new_market c 504 348 29ms 8.5s 6.4min 6.4min 0 transport_latency_assumed new_market g 501 122 419ms 5.0min 5.3min 5.5min 0 transport_latency_assumed new_market h 517 129 77ms 26.5s 6.2min 6.7min 0 transport_latency_assumed new_market i 494 143 47ms 16.1s 1.2min 1.9min 0 transport_latency_assumed new_market k 494 95 92ms 14.2s 1.2min 1.6min 0 transport_latency_assumed price_change c 106,407,125 98,039,989 5ms 14ms 109ms 7.0s 0 transport_latency_assumed price_change g 99,350,136 10,086 80ms 108ms 746ms 11.3s 0 transport_latency_assumed price_change h 102,369,234 1,500,378 19ms 40ms 163ms 6.5s 0 transport_latency_assumed price_change i 111,881,792 1,389,868 21ms 32ms 187ms 4.3s 0 transport_latency_assumed price_change k 111,873,974 10,991,839 12ms 22ms 111ms 5.8s 0 transport_latency_assumed tick_size_change c 2,312 2,132 5ms 11ms 169ms 251ms 0 transport_latency_assumed tick_size_change g 2,216 not meas. 79ms 94ms 236ms 454ms 0 transport_latency_assumed tick_size_change h 2,148 12 19ms 30ms 222ms 252ms 0 transport_latency_assumed tick_size_change i 2,372 not meas. 20ms 26ms 62ms 210ms 0 transport_latency_assumed tick_size_change k 2,372 228 12ms 18ms 47ms 70ms 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-25/09/2026-09-25T09.parquet sha256sum 2026-09-25T09.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.