Hour audit: 2026-09-20T12
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-20T12 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-20T12:00:00.000674718+00:00 · last event 2026-09-20T12:59:59.999896918+00:00
VOLUME 128,196,024 rows · 1,405,889,251 bytes (1.31 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 126,761,022 · e: 126,708,769 · f: 122,398,068 · g: 122,020,134 · c: 113,833,198 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 18,614,818 (14.52%) · e: 1,597,015 (1.25%) · f: 577,940 (0.45%) · g: 163,323 (0.13%) · c: 107,242,928 (83.66%) (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 128,196,024 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 b11725f7ef26c0c3146aebb919392301510453f275392b0aa40fe88f0a8e1d93
the corpus checksum ledger names this file with the same digest
joined 128,199,113 to merged 128,196,024, minus 3,089 (minus 0.0024%)
boundary drops 3,089 · 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-20T14:39:39Z 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 12,419,125 143,747,149 0-47 1a8ecf6b6b8981d30dca96b892551e8d3add54432281fdc08bdf887e55ed5ea8 book 1,504,233 86,530,374 48-53 b7e20335ec8c3d5b4d61ff0cf0098dde0a6428665e672e7dd4039a4d764fd736 last_trade_price 70,847 4,106,790 54-54 618df84fd76fe0c3b3fa8b30880b5211dd4473a2064ad6e1c986639a6ca04da7 market_resolved 1,307 203,812 55-55 be58b8c3f8f8736a8281c78b17cc08a907f951167376ad51016707be23a36d97 new_market 1,256 135,188 56-56 fbef7e72eb45b3940baec30f49613a13722baf1a556868da5f843a11e634f75b price_change 114,192,172 1,169,456,107 57-492 8abd04a9c5bf7f490bc41424eb79bbe8952f42a82a99e0175f931135334fe017 tick_size_change 7,084 252,801 493-493 342de4168a5fa344b61bac2efad26ff43901dc1d476d1d571f5f9244e36bbbdd EVENT MIX count share price_change 114,192,172 89.08% best_bid_ask 12,419,125 9.69% book 1,504,233 1.17% last_trade_price 70,847 0.06% tick_size_change 7,084 <0.01% market_resolved 1,307 <0.01% new_market 1,256 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,419,355 12,419,125 230 1,606 FULL book 1,504,255 1,504,233 22 168,504 FULL last_trade_price 70,848 70,847 1 430 FULL market_resolved 1,307 1,307 0 143 FULL new_market 1,256 1,256 0 3 FULL price_change 114,195,008 114,192,172 2,836 669 FULL tick_size_change 7,084 7,084 0 316 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,052,158 10,441,903 5ms 15ms 122ms 8.1s 0 transport_latency_assumed best_bid_ask e 12,415,196 146,143 41ms 54ms 201ms 16.6s 0 transport_latency_assumed best_bid_ask f 11,933,598 33,183 47ms 61ms 227ms 18.9s 0 transport_latency_assumed best_bid_ask g 11,902,780 1,793 79ms 100ms 427ms 20.7s 0 transport_latency_assumed best_bid_ask h 12,417,190 1,796,103 18ms 35ms 167ms 56.9s 0 transport_latency_assumed book c 1,211,936 1,127,107 4.7min 1.9d 39.8d 113.6d 0 book_staleness book e 159,036 11,929 45ms 7.0s 4.5d 113.6d 0 book_staleness book f 545,779 200,404 1.8min 1.5d 38.7d 113.6d 0 book_staleness book g 539,029 140,461 1.8min 1.5d 38.7d 113.6d 0 book_staleness book h 146,251 24,332 22ms 87ms 11.7min 95.0d 0 book_staleness last_trade_price c 61,902 57,774 6ms 23ms 203ms 2.0s 0 transport_latency_assumed last_trade_price e 70,060 1,192 44ms 149ms 2.2s 16.6s 0 transport_latency_assumed last_trade_price f 67,358 308 49ms 221ms 2.5s 18.9s 0 transport_latency_assumed last_trade_price g 66,495 31 86ms 351ms 6.0s 20.5s 0 transport_latency_assumed last_trade_price h 70,539 11,542 19ms 60ms 460ms 27.8s 0 transport_latency_assumed market_resolved c 1,216 1,168 5ms 15ms 5.6min 6.3min 0 transport_latency_assumed market_resolved e 1,264 3 43ms 119ms 344ms 607ms 0 transport_latency_assumed market_resolved f 1,208 4 47ms 123ms 346ms 675ms 0 transport_latency_assumed market_resolved g 1,212 not meas. 80ms 215ms 443ms 1.1s 0 transport_latency_assumed market_resolved h 1,264 132 19ms 55ms 128ms 2.4s 0 transport_latency_assumed new_market c 888 606 93ms 14.4s 2.1h 8.1h 0 transport_latency_assumed new_market e 882 130 200ms 11.8s 36.7s 1.6h 0 transport_latency_assumed new_market f 880 117 190ms 12.8s 38.1s 11.4h 0 transport_latency_assumed new_market g 887 108 279ms 14.8s 59.9min 16.1h 0 transport_latency_assumed new_market h 882 295 135ms 12.0s 38.2s 7.1h 0 transport_latency_assumed price_change c 101,498,982 95,608,650 5ms 17ms 136ms 8.1s 0 transport_latency_assumed price_change e 114,055,247 1,437,520 42ms 62ms 343ms 17.1s 0 transport_latency_assumed price_change f 109,842,389 343,894 47ms 71ms 431ms 19.0s 0 transport_latency_assumed price_change g 109,502,911 20,930 80ms 117ms 1.0s 20.8s 0 transport_latency_assumed price_change h 114,117,812 16,781,178 18ms 39ms 199ms 1.0min 0 transport_latency_assumed tick_size_change c 6,116 5,720 5ms 19ms 92ms 347ms 0 transport_latency_assumed tick_size_change e 7,084 98 42ms 58ms 164ms 443ms 0 transport_latency_assumed tick_size_change f 6,856 30 47ms 64ms 158ms 449ms 0 transport_latency_assumed tick_size_change g 6,820 not meas. 79ms 98ms 214ms 465ms 0 transport_latency_assumed tick_size_change h 7,084 1,236 18ms 38ms 180ms 4.4s 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-20/12/2026-09-20T12.parquet sha256sum 2026-09-20T12.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.