Hour audit: 2026-09-09T05
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-09T05 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-09T05:00:00.000026622+00:00 · last event 2026-09-09T05:59:59.999900395+00:00
VOLUME 98,165,955 rows · 978,520,743 bytes (933.19 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 97,910,553 · e: 97,797,501 · c: 97,752,270 · g: 97,725,371 · h: 97,632,017 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 221,453 (0.23%) · e: 401,418 (0.41%) · c: 94,981,313 (96.76%) · g: 30,584 (0.03%) · h: 2,531,187 (2.58%) (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 98,165,955 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 b58ea937b7be66ec582400b69d9fc98f00166053378d8880362546a89665fcf7
the corpus checksum ledger names this file with the same digest
joined 98,169,075 to merged 98,165,955, minus 3,120 (minus 0.0032%)
boundary drops 3,120 · 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-09T06:55:41Z 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,192,156 98,349,616 0-35 3b1a14c53c58675abd77c79b9fb7070d7b19b4f1ba338b4e697ea928bd71ffae book 434,657 45,514,543 36-37 d3bc119c11166cdd0345c82131b08f70b31d73932b89d09645b2905d0903d373 last_trade_price 53,645 2,980,898 38-38 da7fdaa29cfdbd4c57e34ea6d563101b193dd8273fb079e8d38910cbee2506de market_resolved 1,082 171,361 39-39 0bf800d15d84f27633074f54a0dbcd0d5c88555d8739540ffa10c7d4de70c5e8 new_market 763 89,115 40-40 3f5f35c4c002c52d783568ad277cf2ecd327b0171f8046aab1b565bb70a1d9e1 price_change 88,481,492 830,213,754 41-378 c7058bca16d647cb0bf9ddb270a6077b5c90866ec0fdba2953ecb018b9f4280b tick_size_change 2,160 79,988 379-379 32083425880426a0cb2516a7dbd497b9029c3d56c3d5e43c9e8484737bd1def4 EVENT MIX count share price_change 88,481,492 90.13% best_bid_ask 9,192,156 9.36% book 434,657 0.44% last_trade_price 53,645 0.05% tick_size_change 2,160 <0.01% market_resolved 1,082 <0.01% new_market 763 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,192,366 9,192,156 210 117 FULL book 434,669 434,657 12 142,580 FULL last_trade_price 53,645 53,645 0 1 FULL market_resolved 1,082 1,082 0 0 FULL new_market 763 763 0 0 FULL price_change 88,484,390 88,481,492 2,898 479 FULL tick_size_change 2,160 2,160 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,191,578 8,942,931 4ms 8ms 70ms 3.4s 0 transport_latency_assumed best_bid_ask e 9,188,754 19,825 39ms 43ms 120ms 3.7s 0 transport_latency_assumed best_bid_ask f 9,188,879 5,940 47ms 52ms 135ms 2.7s 0 transport_latency_assumed best_bid_ask g 9,190,196 523 84ms 96ms 236ms 15.3s 0 transport_latency_assumed best_bid_ask h 9,191,302 222,937 20ms 24ms 91ms 6.8s 0 transport_latency_assumed book c 115,470 109,865 6ms 34ms 7.8h 83.8d 0 book_staleness book e 321,869 162,490 1.7min 13.5h 17.7d 102.3d 0 book_staleness book f 307,378 147,749 1.3min 12.7h 17.7d 102.3d 0 book_staleness book g 120,065 9,074 88ms 382ms 20.1h 83.8d 0 book_staleness book h 111,446 5,479 23ms 48ms 2.8s 44.5d 0 book_staleness last_trade_price c 53,522 51,356 9ms 36ms 188ms 5.0s 0 transport_latency_assumed last_trade_price e 53,561 249 44ms 85ms 374ms 5.0s 0 transport_latency_assumed last_trade_price f 53,554 96 53ms 98ms 418ms 5.0s 0 transport_latency_assumed last_trade_price g 53,569 14 93ms 164ms 593ms 7.1s 0 transport_latency_assumed last_trade_price h 53,552 1,930 25ms 55ms 211ms 5.0s 0 transport_latency_assumed market_resolved c 1,057 1,007 5ms 12ms 196ms 1.0min 0 transport_latency_assumed market_resolved e 1,057 35 40ms 183ms 59.9s 1.0min 0 transport_latency_assumed market_resolved f 1,057 1 48ms 200ms 59.9s 1.0min 0 transport_latency_assumed market_resolved g 1,057 1 87ms 255ms 808ms 56.9s 0 transport_latency_assumed market_resolved h 1,057 38 21ms 75ms 59.9s 1.0min 0 transport_latency_assumed new_market c 571 401 51ms 324ms 30.7s 1.9min 0 transport_latency_assumed new_market e 571 80 110ms 13.2s 32.7s 2.3min 0 transport_latency_assumed new_market f 571 43 137ms 11.9s 31.0s 12.8min 0 transport_latency_assumed new_market g 571 31 222ms 15.1s 38.2s 3.3min 0 transport_latency_assumed new_market h 571 208 80ms 9.5s 37.7s 1.2min 0 transport_latency_assumed price_change c 88,387,912 85,873,645 5ms 9ms 75ms 4.8s 0 transport_latency_assumed price_change e 88,229,529 218,739 39ms 45ms 152ms 3.7s 0 transport_latency_assumed price_change f 88,356,954 67,624 47ms 55ms 171ms 3.7s 0 transport_latency_assumed price_change g 88,357,753 20,941 83ms 98ms 292ms 15.3s 0 transport_latency_assumed price_change h 88,271,929 2,300,543 20ms 26ms 104ms 6.8s 0 transport_latency_assumed tick_size_change c 2,160 2,108 5ms 9ms 48ms 189ms 0 transport_latency_assumed tick_size_change e 2,160 not meas. 39ms 43ms 109ms 124ms 0 transport_latency_assumed tick_size_change f 2,160 not meas. 46ms 50ms 84ms 346ms 0 transport_latency_assumed tick_size_change g 2,160 not meas. 83ms 95ms 134ms 263ms 0 transport_latency_assumed tick_size_change h 2,160 52 19ms 24ms 57ms 146ms 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/05/2026-09-09T05.parquet sha256sum 2026-09-09T05.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.