Hour audit: 2026-09-08T00
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-08T00 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-08T00:00:00.000047495+00:00 · last event 2026-09-08T00:59:59.999931548+00:00
VOLUME 99,153,898 rows · 1,027,459,831 bytes (979.86 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 98,772,179 · f: 98,740,040 · e: 98,736,806 · g: 98,733,407 · c: 94,955,785 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 8,562,145 (8.64%) · f: 87,948 (0.09%) · e: 276,474 (0.28%) · g: 21,328 (0.02%) · c: 90,206,003 (90.98%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 99,153,898 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 9449ecb467068a1a8e1b21894fcfdfe80e98b25e55f7df360345a057ba57d7c4
the corpus checksum ledger names this file with the same digest
joined 99,156,184 to merged 99,153,898, minus 2,286 (minus 0.0023%)
boundary drops 2,286 · 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-08T01:56:12Z 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 11,790,671 127,490,210 0-44 26ec758adb0697655c7a76b950cd750dd78de859672a85022b48077f0a04b370 book 499,061 52,699,752 45-46 6b7e8a1b0ecedbd8153d8b4d33871609661fdda8f35a0e16d4b90003442f397f last_trade_price 60,282 3,350,887 47-47 cbb1aba05594029fe16d616b0d9163fbd194c25922f9d67d8750346d032f5ed3 market_resolved 691 105,775 48-48 5ae7a1dcf62470473ac435af0de95d8b4c5bb1e20271da6f74935ad34561a31d new_market 1,041 101,700 49-49 60000e364131f6ffe68ecabf7296e7ebd99b34de92ab500ba018667d65d9c839 price_change 86,799,856 842,496,706 50-381 9406b062293c9c952b8d9c1915a13524935a28874652bbaa42324b3878f35eb7 tick_size_change 2,296 85,172 382-382 533e2b276475b97a1c7a137e039a87caac3f1ce8577ebc51a1b989d9ae0e6d87 EVENT MIX count share price_change 86,799,856 87.54% best_bid_ask 11,790,671 11.89% book 499,061 0.50% last_trade_price 60,282 0.06% tick_size_change 2,296 <0.01% new_market 1,041 <0.01% market_resolved 691 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,790,797 11,790,671 126 1,255 FULL book 499,083 499,061 22 177,821 FULL last_trade_price 60,282 60,282 0 101 FULL market_resolved 691 691 0 29 FULL new_market 1,041 1,041 0 1 FULL price_change 86,801,994 86,799,856 2,138 676 FULL tick_size_change 2,296 2,296 0 44 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,291,315 10,774,260 5ms 8ms 73ms 2.9s 0 transport_latency_assumed best_bid_ask e 11,788,199 23,263 41ms 45ms 124ms 2.9s 0 transport_latency_assumed best_bid_ask f 11,788,063 8,953 46ms 53ms 156ms 3.8s 0 transport_latency_assumed best_bid_ask g 11,787,410 1,006 83ms 102ms 277ms 13.5s 0 transport_latency_assumed best_bid_ask h 11,789,590 983,189 12ms 15ms 85ms 17.2s 0 transport_latency_assumed book c 482,575 472,582 2.7min 13.6h 29.5d 101.1d 0 book_staleness book e 127,640 2,580 43ms 100ms 3.9min 82.5d 0 book_staleness book f 126,696 1,362 48ms 120ms 2.4s 82.4d 0 book_staleness book g 134,772 6,239 90ms 598ms 12.9h 82.6d 0 book_staleness book h 126,768 16,298 15ms 34ms 2.1s 82.4d 0 book_staleness last_trade_price c 56,446 52,945 10ms 38ms 190ms 5.0s 0 transport_latency_assumed last_trade_price e 60,189 270 47ms 92ms 540ms 5.0s 0 transport_latency_assumed last_trade_price f 60,213 56 52ms 111ms 1.1s 5.0s 0 transport_latency_assumed last_trade_price g 60,249 6 97ms 212ms 5.3s 13.5s 0 transport_latency_assumed last_trade_price h 60,259 7,005 17ms 49ms 253ms 6.2s 0 transport_latency_assumed market_resolved c 628 582 5ms 22ms 4.7min 4.8min 0 transport_latency_assumed market_resolved e 657 2 42ms 188ms 44.7s 1.0min 0 transport_latency_assumed market_resolved f 657 10 48ms 195ms 44.6s 1.0min 0 transport_latency_assumed market_resolved g 657 not meas. 85ms 272ms 1.1s 1.5s 0 transport_latency_assumed market_resolved h 657 97 12ms 36ms 98ms 324ms 0 transport_latency_assumed new_market c 650 295 94ms 17.2s 37.2s 1.2min 0 transport_latency_assumed new_market e 651 149 124ms 13.8s 38.1s 1.2min 0 transport_latency_assumed new_market f 651 167 164ms 22.3s 36.1s 3.9min 0 transport_latency_assumed new_market g 651 77 273ms 19.4s 38.7s 1.1min 0 transport_latency_assumed new_market h 651 353 94ms 15.4s 36.9s 47.6s 0 transport_latency_assumed price_change c 83,122,047 78,903,251 5ms 9ms 105ms 3.2s 0 transport_latency_assumed price_change e 86,757,174 250,208 41ms 48ms 179ms 2.9s 0 transport_latency_assumed price_change f 86,761,464 77,400 46ms 56ms 223ms 3.8s 0 transport_latency_assumed price_change g 86,747,376 14,000 84ms 104ms 380ms 13.5s 0 transport_latency_assumed price_change h 86,791,958 7,554,997 12ms 17ms 124ms 18.0s 0 transport_latency_assumed tick_size_change c 2,124 2,088 5ms 7ms 22ms 55ms 0 transport_latency_assumed tick_size_change e 2,296 2 41ms 45ms 114ms 311ms 0 transport_latency_assumed tick_size_change f 2,296 not meas. 46ms 51ms 83ms 177ms 0 transport_latency_assumed tick_size_change g 2,292 not meas. 83ms 100ms 210ms 345ms 0 transport_latency_assumed tick_size_change h 2,296 206 12ms 17ms 96ms 156ms 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-08/00/2026-09-08T00.parquet sha256sum 2026-09-08T00.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.