Hour audit: 2026-09-12T08
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-12T08 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-12T08:00:00.000017944+00:00 · last event 2026-09-12T08:59:59.999919855+00:00
VOLUME 114,635,929 rows · 1,212,762,556 bytes (1.13 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured g: 110,615,343 · h: 110,429,102 · f: 110,400,223 · e: 110,383,535 · c: 64,584,111 (each machine's own feed; these overlap and do not sum to the file)
supplied g: 154,558 (0.13%) · h: 50,345,673 (43.92%) · f: 238,175 (0.21%) · e: 1,605,313 (1.40%) · c: 62,292,210 (54.34%) (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 114,635,929 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 2a27b851e1be5cabd332204eff18a45164e37664b8d6c6f1e5f751a4e3a95347
the corpus checksum ledger names this file with the same digest
joined 114,659,918 to merged 114,635,929, minus 23,989 (minus 0.0209%)
boundary drops 23,989 · 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-12T10:35:16Z 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 10,382,056 114,083,834 0-39 707550831dd9af1bc94b76e2e2c4dfcfce02b6d7c5bf3e14ab8bf02ed50a3943 book 4,532,292 136,436,671 40-57 aed23bc3b88d664bc356602d0d313125577e08ae9a65dd3be9353b0812c3bcb9 last_trade_price 51,836 2,996,536 58-58 38589af87555bb54fdb96d34608d12d5b1120ffa1927fa16b5eabb0bca6ea75b market_resolved 1,805 96,276 59-59 e88e46e97bdc1315e6dd480a9879aaa81588105177247151ca37d2f8e2e8bd24 new_market 1,677 77,283 60-60 cf90bf4903310d8bfae017a35f77bea7a99fc05603ce14e47b2dc75c1ca9028e price_change 99,663,971 957,678,288 61-441 3cbd6ade462561670d8dd5349e9803e1a57c534c9c28591d434ea46b0fcc2698 tick_size_change 2,292 85,726 442-442 76d35334636ed333de412cbdb73e3810520e960c1efbd06b9005fe12cb6f489f EVENT MIX count share price_change 99,663,971 86.94% best_bid_ask 10,382,056 9.06% book 4,532,292 3.95% last_trade_price 51,836 0.05% tick_size_change 2,292 <0.01% market_resolved 1,805 <0.01% new_market 1,677 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,382,241 10,382,056 185 10,129 FULL book 4,553,846 4,532,292 21,554 183,081 FULL last_trade_price 51,836 51,836 0 1,017 FULL market_resolved 1,805 1,805 0 79 FULL new_market 1,723 1,677 46 132 FULL price_change 99,666,175 99,663,971 2,204 7,407 FULL tick_size_change 2,292 2,292 0 260 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 5,674,460 5,479,451 5ms 11ms 51ms 974ms 0 transport_latency_assumed best_bid_ask e 10,380,049 138,693 38ms 42ms 91ms 3.6s 0 transport_latency_assumed best_bid_ask f 10,379,862 13,168 47ms 51ms 113ms 5.0s 0 transport_latency_assumed best_bid_ask g 10,375,373 704 84ms 101ms 252ms 29.8s 0 transport_latency_assumed best_bid_ask h 10,380,504 4,750,040 18ms 22ms 67ms 19.3s 0 transport_latency_assumed book c 4,275,725 4,103,738 27.2min 14.9h 31.6d 105.4d 0 book_staleness book e 310,263 76,693 1.3min 11.1h 20.8d 105.4d 0 book_staleness book f 325,853 75,878 1.7min 11.6h 20.8d 105.4d 0 book_staleness book g 599,062 145,608 8.5min 14.6h 27.8d 105.4d 0 book_staleness book h 342,453 130,375 2.0min 12.1h 20.8d 105.4d 0 book_staleness last_trade_price c 28,092 26,807 11ms 40ms 172ms 4.9s 0 transport_latency_assumed last_trade_price e 51,806 978 44ms 101ms 504ms 5.0s 0 transport_latency_assumed last_trade_price f 51,803 238 54ms 111ms 445ms 5.0s 0 transport_latency_assumed last_trade_price g 51,702 22 98ms 215ms 821ms 29.9s 0 transport_latency_assumed last_trade_price h 51,804 23,791 23ms 57ms 204ms 5.0s 0 transport_latency_assumed market_resolved c 1,576 1,566 13.0min 27.4min 39.2min 40.8min 0 transport_latency_assumed market_resolved e 447 8 40ms 156ms 33.6s 1.0min 0 transport_latency_assumed market_resolved f 447 2 49ms 186ms 33.6s 1.0min 0 transport_latency_assumed market_resolved g 447 1 95ms 269ms 577ms 1.4min 0 transport_latency_assumed market_resolved h 447 228 19ms 62ms 140ms 163ms 0 transport_latency_assumed new_market c 1,694 1,453 8.4min 23.1min 29.2min 35.1min 0 transport_latency_assumed new_market e 309 29 70ms 13.4s 22.3s 1.4min 0 transport_latency_assumed new_market f 309 63 81ms 14.5s 22.2s 1.4min 0 transport_latency_assumed new_market g 309 47 103ms 15.0s 54.2s 1.2min 0 transport_latency_assumed new_market h 309 85 54ms 13.0s 22.1s 22.8s 0 transport_latency_assumed price_change c 54,601,308 52,677,955 6ms 12ms 58ms 1.7s 0 transport_latency_assumed price_change e 99,638,369 1,388,864 38ms 43ms 122ms 4.5s 0 transport_latency_assumed price_change f 99,639,661 148,826 48ms 52ms 140ms 5.0s 0 transport_latency_assumed price_change g 99,586,158 8,176 85ms 104ms 300ms 30.0s 0 transport_latency_assumed price_change h 99,651,293 45,440,150 18ms 23ms 76ms 20.1s 0 transport_latency_assumed tick_size_change c 1,256 1,240 5ms 11ms 20ms 41ms 0 transport_latency_assumed tick_size_change e 2,292 48 38ms 41ms 79ms 162ms 0 transport_latency_assumed tick_size_change f 2,288 not meas. 48ms 51ms 81ms 101ms 0 transport_latency_assumed tick_size_change g 2,292 not meas. 84ms 97ms 229ms 384ms 0 transport_latency_assumed tick_size_change h 2,292 1,004 18ms 23ms 67ms 76ms 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-12/08/2026-09-12T08.parquet sha256sum 2026-09-12T08.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.