Hour audit: 2026-09-09T03
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-09T03 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-09T03:00:00.000017015+00:00 · last event 2026-09-09T03:59:59.999986381+00:00
VOLUME 100,099,813 rows · 984,468,376 bytes (938.86 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 99,973,210 · c: 99,913,986 · g: 99,873,305 · h: 99,833,866 · e: 99,806,853 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 193,009 (0.19%) · c: 96,495,052 (96.40%) · g: 38,368 (0.04%) · h: 3,049,582 (3.05%) · e: 323,802 (0.32%) (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 100,099,813 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 5013d00cd261af6d867c855bb0b09d19902f6cd5fc4ea30e12910a0324fb140e
the corpus checksum ledger names this file with the same digest
joined 100,102,333 to merged 100,099,813, minus 2,520 (minus 0.0025%)
boundary drops 2,520 · 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-09T04:57:04Z 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 9,775,230 105,337,734 0-37 e76c0c610f05d5f8bd44db0f4f91e481513462ddb93573a2669aedd0f569847d book 216,246 19,716,739 38-38 a17275c251a189b84208fe8a82e1aa012b8f93ab1f3c74384417463b9e1f9f83 last_trade_price 54,182 2,987,474 39-39 961ac75fb8e3f02b5b25fca2d21e73ea990d1c5444ff7ad52b078d86952ea5cf market_resolved 1,309 213,116 40-40 c834585937eec8be4d12aaa3fd7b27ba51eb92cfdc468238a6cec73e93c6d494 new_market 1,510 155,119 41-41 f402b769e05fb605b540e7c062b6bf9f9828c8c55b5bc9054fe209fffa12bd84 price_change 90,048,948 854,829,034 42-385 f3a036f25fa55d5e4ce34fcea42f548cae0d9ba24dfa5683c65a41fe5c89b8ba tick_size_change 2,388 87,283 386-386 3df6c32f633a5ef4afd49594e1c76cf8b5a447235e84eba969036665e1b8c711 EVENT MIX count share price_change 90,048,948 89.96% best_bid_ask 9,775,230 9.77% book 216,246 0.22% last_trade_price 54,182 0.05% tick_size_change 2,388 <0.01% new_market 1,510 <0.01% market_resolved 1,309 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,775,404 9,775,230 174 138 FULL book 216,258 216,246 12 34,380 FULL last_trade_price 54,184 54,182 2 1 FULL market_resolved 1,309 1,309 0 0 FULL new_market 1,510 1,510 0 0 FULL price_change 90,051,280 90,048,948 2,332 466 FULL tick_size_change 2,388 2,388 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,774,604 9,452,383 5ms 9ms 95ms 5.5s 0 transport_latency_assumed best_bid_ask e 9,773,742 29,547 39ms 45ms 143ms 4.3s 0 transport_latency_assumed best_bid_ask f 9,773,123 10,556 46ms 53ms 159ms 3.1s 0 transport_latency_assumed best_bid_ask g 9,772,106 1,375 84ms 104ms 321ms 25.5s 0 transport_latency_assumed best_bid_ask h 9,774,442 281,369 18ms 23ms 130ms 20.4s 0 transport_latency_assumed book c 121,294 114,654 6ms 79ms 13.9h 83.7d 0 book_staleness book e 116,508 4,056 41ms 125ms 1.8h 100.6d 0 book_staleness book f 193,463 80,052 73ms 6.3h 16.5d 102.2d 0 book_staleness book g 124,480 11,005 90ms 3.6s 1.1d 102.2d 0 book_staleness book h 114,459 6,479 21ms 49ms 8.1s 83.6d 0 book_staleness last_trade_price c 54,099 51,690 9ms 38ms 205ms 5.0s 0 transport_latency_assumed last_trade_price e 54,118 181 45ms 94ms 1.1s 5.5s 0 transport_latency_assumed last_trade_price f 54,067 63 52ms 103ms 1.0s 5.0s 0 transport_latency_assumed last_trade_price g 54,048 9 93ms 182ms 6.4s 25.6s 0 transport_latency_assumed last_trade_price h 54,102 2,239 23ms 55ms 329ms 9.0s 0 transport_latency_assumed market_resolved c 1,299 1,227 5ms 12ms 49.5s 1.0min 0 transport_latency_assumed market_resolved e 1,299 28 42ms 133ms 44.9s 1.0min 0 transport_latency_assumed market_resolved f 1,299 not meas. 50ms 161ms 44.9s 1.0min 0 transport_latency_assumed market_resolved g 1,299 2 90ms 261ms 55.5s 58.5s 0 transport_latency_assumed market_resolved h 1,299 52 25ms 61ms 45.2s 1.0min 0 transport_latency_assumed new_market c 1,010 652 67ms 16.0s 57.4s 2.5min 0 transport_latency_assumed new_market e 1,010 155 137ms 21.8s 58.4s 4.1min 0 transport_latency_assumed new_market f 1,010 168 135ms 16.4s 59.4s 1.7min 0 transport_latency_assumed new_market g 1,010 133 231ms 18.1s 57.5s 2.5min 0 transport_latency_assumed new_market h 1,010 402 110ms 16.1s 54.1s 2.3min 0 transport_latency_assumed price_change c 89,959,292 86,872,104 5ms 9ms 100ms 6.1s 0 transport_latency_assumed price_change e 89,857,788 289,831 40ms 47ms 175ms 4.4s 0 transport_latency_assumed price_change f 89,947,860 102,170 46ms 56ms 194ms 3.1s 0 transport_latency_assumed price_change g 89,917,974 25,840 83ms 110ms 385ms 25.6s 0 transport_latency_assumed price_change h 89,886,166 2,759,003 18ms 25ms 140ms 21.1s 0 transport_latency_assumed tick_size_change c 2,388 2,342 5ms 9ms 66ms 141ms 0 transport_latency_assumed tick_size_change e 2,388 4 39ms 44ms 108ms 242ms 0 transport_latency_assumed tick_size_change f 2,388 not meas. 46ms 51ms 83ms 199ms 0 transport_latency_assumed tick_size_change g 2,388 4 82ms 98ms 298ms 574ms 0 transport_latency_assumed tick_size_change h 2,388 38 18ms 23ms 83ms 506ms 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-09/03/2026-09-09T03.parquet sha256sum 2026-09-09T03.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.