Hour audit: 2026-09-12T02
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-12T02 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-12T02:00:00.000032726+00:00 · last event 2026-09-12T02:59:59.999964064+00:00
VOLUME 122,199,720 rows · 1,307,600,058 bytes (1.22 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 119,526,180 · f: 119,522,851 · h: 119,490,273 · g: 114,640,555 · c: 88,776,808 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 1,562,842 (1.28%) · f: 402,497 (0.33%) · h: 34,289,931 (28.06%) · g: 188,947 (0.15%) · c: 85,755,503 (70.18%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 122,199,720 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 0d08dd5c52f4a307fda5953528c5e6bc447375bfdba67208b3ac9b896a2d519d
the corpus checksum ledger names this file with the same digest
joined 122,203,073 to merged 122,199,720, minus 3,353 (minus 0.0027%)
boundary drops 3,353 · 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-12T04:37:25Z 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,931,350 122,827,039 0-41 92e886856da4c4056bc18b0498bb3cacb63ba7810308fbd7c0604d39fa9a9d81 book 2,721,806 110,725,398 42-52 3b6ba4138dbaee4fe0d7be225a770af21b0e450288f7967502cf8937994ef095 last_trade_price 43,214 2,460,022 53-53 438e437417a9974e9c04f68629120206be3c0896e138f963083de8720914ec3b market_resolved 3,128 392,264 54-54 8511b5e12ba196c32a946650eb2976e88681b3edcea8c8693b3fd9dbc76559f4 new_market 546 53,047 55-55 dcb7ff67e599bb3a932006d558212bed0512e04062d9e2e8d81e5ecd9fe78f5a price_change 108,495,576 1,069,602,524 56-469 a2af97659504b48184f4da76a2fc11d6a1b6c5d8bf249232a443676b246c7f72 tick_size_change 4,100 149,588 470-470 ac9676b70316d69e4b57bd66a1792a4eab4868b84ce136b18751ccffe81e64bb EVENT MIX count share price_change 108,495,576 88.79% best_bid_ask 10,931,350 8.95% book 2,721,806 2.23% last_trade_price 43,214 0.04% tick_size_change 4,100 <0.01% market_resolved 3,128 <0.01% new_market 546 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,931,648 10,931,350 298 6,005 FULL book 2,722,360 2,721,806 554 209,199 FULL last_trade_price 43,215 43,214 1 517 FULL market_resolved 3,128 3,128 0 115 FULL new_market 546 546 0 12 FULL price_change 108,498,076 108,495,576 2,500 2,408 FULL tick_size_change 4,100 4,100 0 167 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 7,903,885 7,665,235 5ms 9ms 68ms 3.0s 0 transport_latency_assumed best_bid_ask e 10,929,764 136,406 40ms 45ms 93ms 2.7s 0 transport_latency_assumed best_bid_ask f 10,929,937 30,806 45ms 51ms 124ms 1.9s 0 transport_latency_assumed best_bid_ask g 10,436,491 1,104 83ms 100ms 231ms 10.9s 0 transport_latency_assumed best_bid_ask h 10,930,643 3,097,799 17ms 24ms 81ms 7.8s 0 transport_latency_assumed book c 2,595,389 2,526,953 11.4min 8.9h 31.3d 105.2d 0 book_staleness book e 90,963 2,505 42ms 78ms 6.9min 86.6d 0 book_staleness book f 91,128 1,349 47ms 91ms 5.2min 86.6d 0 book_staleness book g 532,055 163,204 6.2min 8.6h 27.6d 105.2d 0 book_staleness book h 90,722 27,795 20ms 46ms 5.7s 86.7d 0 book_staleness last_trade_price c 30,790 29,048 10ms 44ms 236ms 5.0s 0 transport_latency_assumed last_trade_price e 42,940 697 47ms 94ms 437ms 5.0s 0 transport_latency_assumed last_trade_price f 43,017 206 51ms 102ms 483ms 5.0s 0 transport_latency_assumed last_trade_price g 40,998 5 95ms 195ms 1.4s 10.1s 0 transport_latency_assumed last_trade_price h 43,156 13,258 23ms 60ms 226ms 5.0s 0 transport_latency_assumed market_resolved c 2,646 2,380 5ms 7.5min 15.0min 16.0min 0 transport_latency_assumed market_resolved e 2,373 38 42ms 118ms 259ms 45.4s 0 transport_latency_assumed market_resolved f 2,373 1 47ms 123ms 281ms 33.6s 0 transport_latency_assumed market_resolved g 2,361 212 91ms 503ms 5.7min 5.8min 0 transport_latency_assumed market_resolved h 2,373 497 19ms 43ms 126ms 1.1min 0 transport_latency_assumed new_market c 412 258 143ms 7.2min 1.6h 3.0h 0 transport_latency_assumed new_market e 311 65 101ms 13.8s 4.3min 15.9min 0 transport_latency_assumed new_market f 311 82 118ms 13.5s 18.6s 21.8min 0 transport_latency_assumed new_market g 311 14 152ms 12.1s 17.5s 20.8min 0 transport_latency_assumed new_market h 311 127 92ms 13.9s 17.6s 5.9min 0 transport_latency_assumed price_change c 78,240,254 75,528,311 5ms 9ms 107ms 3.9s 0 transport_latency_assumed price_change e 108,455,729 1,423,064 40ms 46ms 127ms 3.3s 0 transport_latency_assumed price_change f 108,451,985 370,036 46ms 52ms 161ms 2.2s 0 transport_latency_assumed price_change g 103,624,375 24,408 83ms 101ms 288ms 12.7s 0 transport_latency_assumed price_change h 108,418,968 31,149,757 18ms 25ms 105ms 20.5s 0 transport_latency_assumed tick_size_change c 3,432 3,318 5ms 10ms 45ms 135ms 0 transport_latency_assumed tick_size_change e 4,100 67 41ms 45ms 60ms 156ms 0 transport_latency_assumed tick_size_change f 4,100 17 45ms 49ms 88ms 120ms 0 transport_latency_assumed tick_size_change g 3,964 not meas. 84ms 123ms 228ms 453ms 0 transport_latency_assumed tick_size_change h 4,100 698 18ms 29ms 68ms 2.3s 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/02/2026-09-12T02.parquet sha256sum 2026-09-12T02.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.