Hour audit: 2026-09-09T09
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-09T09 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-09T09:00:00.003511376+00:00 · last event 2026-09-09T09:59:59.999999113+00:00
VOLUME 105,532,384 rows · 1,083,899,152 bytes (1.01 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 104,992,004 · f: 104,974,696 · g: 104,953,312 · h: 104,900,282 · c: 100,474,937 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 337,130 (0.32%) · f: 106,852 (0.10%) · g: 25,392 (0.02%) · h: 9,636,060 (9.13%) · c: 95,426,950 (90.42%) (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 105,532,384 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 9c75b8b6d0c3fbc16d0400bdfda5ea959e526db8af3245d781943c7dbf28e3f2
the corpus checksum ledger names this file with the same digest
joined 105,535,936 to merged 105,532,384, minus 3,552 (minus 0.0034%)
boundary drops 3,552 · 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-09T10:57:45Z 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,470,768 103,611,876 0-36 79b42c1cb3272b6d6212e459769f4fc723134d309266602523767caa902387af book 535,967 57,320,336 37-39 4b560401a7e73ba300bd96a81b450c16368055df426423bc7f4e581bbaeb9476 last_trade_price 57,710 3,261,320 40-40 0e079b25264edb2d14d60625fd57fc7b1f133fb9c230be4dfd7cbf23323d82f8 market_resolved 832 131,888 41-41 dd273135cbef9497ac152137cc3a79d513973c3f668c129de23773ffb298896c new_market 975 109,079 42-42 4f09bc970e8c945fa2b19e69da24af7c2af6b51987d8d055d4ab714c434120c7 price_change 95,463,112 918,146,708 43-407 40dbbf745d2f0d8af29ab5b7f0d35e61b575cccd07e8143506c0bd0729f7aa92 tick_size_change 3,020 111,067 408-408 8e902a8a5b9b5516ecf1fd0848532c6c9e6b6090baed91bd7c9d04174d41eb74 EVENT MIX count share price_change 95,463,112 90.46% best_bid_ask 9,470,768 8.97% book 535,967 0.51% last_trade_price 57,710 0.05% tick_size_change 3,020 <0.01% new_market 975 <0.01% market_resolved 832 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,470,968 9,470,768 200 536 FULL book 535,979 535,967 12 191,934 FULL last_trade_price 57,710 57,710 0 69 FULL market_resolved 832 832 0 0 FULL new_market 975 975 0 0 FULL price_change 95,466,452 95,463,112 3,340 665 FULL tick_size_change 3,020 3,020 0 50 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,022,930 8,585,015 5ms 10ms 92ms 8.6s 0 transport_latency_assumed best_bid_ask e 9,468,792 28,063 34ms 39ms 149ms 7.2s 0 transport_latency_assumed best_bid_ask f 9,468,696 8,909 46ms 52ms 162ms 6.2s 0 transport_latency_assumed best_bid_ask g 9,466,867 842 86ms 99ms 338ms 15.3s 0 transport_latency_assumed best_bid_ask h 9,469,212 847,939 13ms 18ms 110ms 54.4s 0 transport_latency_assumed book c 509,945 500,480 5.4min 19.5h 27.8d 102.5d 0 book_staleness book e 130,424 6,421 37ms 1.3s 23.2h 84.0d 0 book_staleness book f 123,602 2,836 49ms 222ms 5.1h 83.9d 0 book_staleness book g 144,427 14,000 95ms 26.4min 2.0d 84.0d 0 book_staleness book h 120,592 12,230 17ms 51ms 4.7min 37.9d 0 book_staleness last_trade_price c 55,149 51,741 10ms 38ms 223ms 4.9s 0 transport_latency_assumed last_trade_price e 57,680 305 40ms 121ms 1.6s 7.2s 0 transport_latency_assumed last_trade_price f 57,668 94 53ms 141ms 3.5s 6.2s 0 transport_latency_assumed last_trade_price g 57,274 9 98ms 257ms 4.6s 15.4s 0 transport_latency_assumed last_trade_price h 57,530 5,561 18ms 55ms 385ms 8.9s 0 transport_latency_assumed market_resolved c 767 708 5ms 44ms 5.3min 5.8min 0 transport_latency_assumed market_resolved e 763 34 36ms 193ms 1.0min 1.1min 0 transport_latency_assumed market_resolved f 763 not meas. 48ms 208ms 1.0min 1.1min 0 transport_latency_assumed market_resolved g 763 22 86ms 258ms 630ms 940ms 0 transport_latency_assumed market_resolved h 763 68 14ms 91ms 1.0min 1.1min 0 transport_latency_assumed new_market c 717 352 94ms 13.7s 1.6min 1.8min 0 transport_latency_assumed new_market e 717 107 165ms 15.2s 23.1s 1.0min 0 transport_latency_assumed new_market f 717 82 177ms 11.9s 24.4s 1.3min 0 transport_latency_assumed new_market g 717 133 344ms 13.4s 25.2s 1.3min 0 transport_latency_assumed new_market h 717 301 113ms 11.5s 24.5s 1.0min 0 transport_latency_assumed price_change c 90,882,609 86,285,973 5ms 10ms 101ms 8.6s 0 transport_latency_assumed price_change e 95,330,608 302,181 35ms 42ms 205ms 7.2s 0 transport_latency_assumed price_change f 95,320,230 94,919 47ms 56ms 219ms 6.2s 0 transport_latency_assumed price_change g 95,280,244 10,386 86ms 103ms 485ms 15.4s 0 transport_latency_assumed price_change h 95,248,448 8,769,653 14ms 20ms 127ms 54.6s 0 transport_latency_assumed tick_size_change c 2,820 2,681 5ms 10ms 106ms 197ms 0 transport_latency_assumed tick_size_change e 3,020 19 35ms 51ms 146ms 283ms 0 transport_latency_assumed tick_size_change f 3,020 12 47ms 73ms 162ms 332ms 0 transport_latency_assumed tick_size_change g 3,020 not meas. 86ms 115ms 250ms 5.6s 0 transport_latency_assumed tick_size_change h 3,020 308 14ms 23ms 84ms 1.2s 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/09/2026-09-09T09.parquet sha256sum 2026-09-09T09.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.