Hour audit: 2026-09-12T05
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-12T05 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-12T05:00:00.000133273+00:00 · last event 2026-09-12T05:59:59.999974062+00:00
VOLUME 110,196,081 rows · 1,144,676,769 bytes (1.07 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured g: 107,739,497 · f: 107,734,966 · e: 107,726,290 · h: 107,660,404 · c: 82,911,761 (each machine's own feed; these overlap and do not sum to the file)
supplied g: 52,791 (0.05%) · f: 313,252 (0.28%) · e: 1,785,794 (1.62%) · h: 28,030,137 (25.44%) · c: 80,014,107 (72.61%) (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 110,196,081 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 0262f6ed9b083e04ae665a15c94d0f81368c3506957fd100e987f6b63d9922ee
the corpus checksum ledger names this file with the same digest
joined 110,201,431 to merged 110,196,081, minus 5,350 (minus 0.0049%)
boundary drops 5,350 · 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-12T07:50:51Z 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,589,059 114,832,025 0-40 74786a33103377b4f0befb3f3570370995ed46de312b48d1d6fd7b2245bf8e9d book 2,551,931 104,445,844 41-50 652db061c6668378e554909061440b8dd377507fc254c21b289d1a4bbb7ac23b last_trade_price 60,222 3,336,474 51-51 ec6f8789772f38a4706825ca3507dddd163aa2aade33bb039796ccf62b83a12f market_resolved 2,239 195,860 52-52 41cc493916c70bb8932acd81fc86bff892a3d45fd430fc939b15b88b9b5200c1 new_market 1,470 113,852 53-53 2f0c583310fd7b0639b80e891154c1cb9542c8070a59830f1469d26e78b572bb price_change 96,989,628 920,440,921 54-423 18b71ecb06a5998330276b625ce5bc3f78fffe1158cde525b2ac95f5dbdde91e tick_size_change 1,532 56,749 424-424 5f9cf21d5329ece0edeecf25d7e1acfe165db9bbc21980220be700bb7600a954 EVENT MIX count share price_change 96,989,628 88.02% best_bid_ask 10,589,059 9.61% book 2,551,931 2.32% last_trade_price 60,222 0.05% market_resolved 2,239 <0.01% tick_size_change 1,532 <0.01% new_market 1,470 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,589,309 10,589,059 250 4,860 FULL book 2,554,738 2,551,931 2,807 205,679 FULL last_trade_price 60,224 60,222 2 500 FULL market_resolved 2,239 2,239 0 107 FULL new_market 1,615 1,470 145 217 FULL price_change 96,991,774 96,989,628 2,146 1,762 FULL tick_size_change 1,532 1,532 0 94 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 7,967,989 7,711,028 5ms 9ms 91ms 6.0s 0 transport_latency_assumed best_bid_ask e 10,587,598 159,844 39ms 43ms 114ms 3.5s 0 transport_latency_assumed best_bid_ask f 10,587,216 22,346 46ms 50ms 132ms 9.9s 0 transport_latency_assumed best_bid_ask g 10,584,267 1,850 84ms 106ms 280ms 14.7s 0 transport_latency_assumed best_bid_ask h 10,588,055 2,693,991 18ms 23ms 105ms 37.7s 0 transport_latency_assumed book c 2,491,936 2,476,492 13.8min 11.7h 31.4d 105.3d 0 book_staleness book e 130,242 4,400 41ms 88ms 51.7s 86.8d 0 book_staleness book f 133,552 3,254 48ms 122ms 3.0h 86.8d 0 book_staleness book g 184,944 25,745 99ms 2.4h 6.7d 86.8d 0 book_staleness book h 135,284 42,040 21ms 63ms 8.2h 97.6d 0 book_staleness last_trade_price c 41,939 39,974 10ms 39ms 211ms 4.9s 0 transport_latency_assumed last_trade_price e 60,033 1,406 45ms 99ms 465ms 4.9s 0 transport_latency_assumed last_trade_price f 60,033 304 52ms 105ms 490ms 5.0s 0 transport_latency_assumed last_trade_price g 59,961 44 99ms 223ms 1.0s 6.8s 0 transport_latency_assumed last_trade_price h 60,062 18,494 23ms 58ms 199ms 7.2s 0 transport_latency_assumed market_resolved c 1,807 1,774 6.0min 13.6min 18.2min 22.3min 0 transport_latency_assumed market_resolved e 1,136 52 41ms 120ms 439ms 55.8s 0 transport_latency_assumed market_resolved f 1,136 35 48ms 129ms 57.5s 59.2s 0 transport_latency_assumed market_resolved g 1,136 not meas. 94ms 250ms 723ms 56.9s 0 transport_latency_assumed market_resolved h 1,136 378 20ms 62ms 58.3s 59.9s 0 transport_latency_assumed new_market c 1,391 980 7.0min 16.9min 17.8min 18.0min 0 transport_latency_assumed new_market e 505 141 136ms 19.4s 35.4s 1.2min 0 transport_latency_assumed new_market f 505 71 127ms 19.5s 32.1s 1.1min 0 transport_latency_assumed new_market g 505 54 240ms 19.3s 32.5s 1.4min 0 transport_latency_assumed new_market h 505 224 82ms 18.3s 35.5s 1.1min 0 transport_latency_assumed price_change c 72,405,543 69,782,747 5ms 10ms 140ms 9.2s 0 transport_latency_assumed price_change e 96,945,244 1,619,886 39ms 43ms 170ms 3.6s 0 transport_latency_assumed price_change f 96,950,992 287,234 46ms 52ms 185ms 10.0s 0 transport_latency_assumed price_change g 96,907,152 25,098 85ms 115ms 361ms 14.8s 0 transport_latency_assumed price_change h 96,873,830 25,274,663 18ms 25ms 152ms 43.4s 0 transport_latency_assumed tick_size_change c 1,156 1,112 5ms 13ms 263ms 526ms 0 transport_latency_assumed tick_size_change e 1,532 65 39ms 46ms 394ms 580ms 0 transport_latency_assumed tick_size_change f 1,532 8 47ms 65ms 537ms 725ms 0 transport_latency_assumed tick_size_change g 1,532 not meas. 85ms 106ms 709ms 1.1s 0 transport_latency_assumed tick_size_change h 1,532 347 18ms 54ms 262ms 541ms 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/05/2026-09-12T05.parquet sha256sum 2026-09-12T05.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.