Hour audit: 2026-09-06T11
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-06T11 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-06T11:00:00.051417533+00:00 · last event 2026-09-06T11:59:59.999997673+00:00
VOLUME 119,214,457 rows · 1,264,213,107 bytes (1.18 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured g: 117,069,778 · f: 117,053,149 · h: 117,051,793 · e: 116,885,645 · c: 91,339,785 (each machine's own feed; these overlap and do not sum to the file)
supplied g: 60,800 (0.05%) · f: 437,275 (0.37%) · h: 28,742,476 (24.11%) · e: 1,836,805 (1.54%) · c: 88,137,101 (73.93%) (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 119,214,457 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 435aaaffc9a39aa7f45a0be35ca0bd81b2bc8830660a1e287ab9451ecdf8e84c
the corpus checksum ledger names this file with the same digest
joined 119,216,893 to merged 119,214,457, minus 2,436 (minus 0.0020%)
boundary drops 2,436 · 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-06T21:40:34Z 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 11,478,310 129,433,119 0-43 e73ebef5a271504e2202c59b7bbbb80ad26b402579e6bbd215ae1a91479f14b7 book 2,216,429 88,497,428 44-52 30afee5adc68bfedb70bcdef87beb64598d5a3ad5849538a7318e0594bad56ba last_trade_price 62,651 3,584,550 53-53 5e2a2b29ae1654105c957878c04553906153973b9652b40ded64f7cbcd84fbd2 market_resolved 1,643 207,738 54-54 47da01de4e7d9fc6660b1d9b518d26817b5f0d57106ac7489a27185b5e7f8fd2 new_market 2,739 261,148 55-55 d3b52a12389eacd3c45234eab7b9021509335312fce167caa1673654438bd999 price_change 105,446,865 1,040,658,415 56-458 0037e117498dcac82f6902d00971d892194e91ea16bb21f6767489260c4dc408 tick_size_change 5,820 213,869 459-459 ccb68b75cc0997bbebe40c8977349d11c88cbcd31eb5a35b07119623d0cdaf58 EVENT MIX count share price_change 105,446,865 88.45% best_bid_ask 11,478,310 9.63% book 2,216,429 1.86% last_trade_price 62,651 0.05% tick_size_change 5,820 <0.01% new_market 2,739 <0.01% market_resolved 1,643 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,478,534 11,478,310 224 4,303 FULL book 2,216,449 2,216,429 20 171,811 FULL last_trade_price 62,651 62,651 0 534 FULL market_resolved 1,647 1,643 4 74 FULL new_market 2,739 2,739 0 0 FULL price_change 105,449,053 105,446,865 2,188 2,248 FULL tick_size_change 5,820 5,820 0 248 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,697,602 8,407,441 5ms 10ms 95ms 3.9s 0 transport_latency_assumed best_bid_ask e 11,475,089 176,254 40ms 46ms 223ms 6.6s 0 transport_latency_assumed best_bid_ask f 11,474,778 40,729 48ms 58ms 261ms 5.8s 0 transport_latency_assumed best_bid_ask g 11,473,909 4,793 80ms 101ms 535ms 29.2s 0 transport_latency_assumed best_bid_ask h 11,475,183 2,849,093 19ms 28ms 236ms 50.3s 0 transport_latency_assumed book c 2,176,953 2,169,745 5.4min 21.2h 35.0d 99.6d 0 book_staleness book e 131,587 5,232 42ms 125ms 3.1s 80.9d 0 book_staleness book f 131,885 2,636 51ms 145ms 3.8s 81.0d 0 book_staleness book g 138,299 4,208 85ms 764ms 12.3h 81.0d 0 book_staleness book h 131,701 34,608 23ms 68ms 3.5s 81.0d 0 book_staleness last_trade_price c 46,490 44,491 10ms 41ms 251ms 5.0s 0 transport_latency_assumed last_trade_price e 62,630 1,275 46ms 102ms 1.0s 6.6s 0 transport_latency_assumed last_trade_price f 62,596 436 54ms 117ms 1.2s 5.8s 0 transport_latency_assumed last_trade_price g 62,580 20 90ms 222ms 9.1s 29.1s 0 transport_latency_assumed last_trade_price h 62,506 16,429 24ms 64ms 422ms 39.2s 0 transport_latency_assumed market_resolved c 1,379 1,342 6ms 7.4min 15.9min 17.0min 0 transport_latency_assumed market_resolved e 1,266 17 40ms 183ms 544ms 59.1s 0 transport_latency_assumed market_resolved f 1,266 8 49ms 199ms 563ms 59.1s 0 transport_latency_assumed market_resolved g 1,269 1 85ms 283ms 1.0s 1.5s 0 transport_latency_assumed market_resolved h 1,266 275 19ms 81ms 316ms 1.2min 0 transport_latency_assumed new_market c 1,836 1,276 66ms 59.3s 3.4h 9.4h 0 transport_latency_assumed new_market e 1,684 399 169ms 20.4s 36.2s 2.5h 0 transport_latency_assumed new_market f 1,684 286 192ms 20.1s 33.1s 6.3h 0 transport_latency_assumed new_market g 1,684 157 285ms 21.0s 31.0s 3.6h 0 transport_latency_assumed new_market h 1,684 621 157ms 20.7s 40.8s 2.2h 0 transport_latency_assumed price_change c 80,410,697 77,508,161 5ms 11ms 111ms 4.0s 0 transport_latency_assumed price_change e 105,207,569 1,653,547 40ms 50ms 276ms 6.6s 0 transport_latency_assumed price_change f 105,375,120 393,164 49ms 62ms 308ms 5.9s 0 transport_latency_assumed price_change g 105,386,217 51,621 81ms 109ms 685ms 29.2s 0 transport_latency_assumed price_change h 105,373,633 25,840,372 19ms 30ms 249ms 50.4s 0 transport_latency_assumed tick_size_change c 4,828 4,645 5ms 10ms 349ms 515ms 0 transport_latency_assumed tick_size_change e 5,820 81 40ms 45ms 315ms 670ms 0 transport_latency_assumed tick_size_change f 5,820 16 48ms 55ms 354ms 694ms 0 transport_latency_assumed tick_size_change g 5,820 not meas. 79ms 95ms 661ms 10.3s 0 transport_latency_assumed tick_size_change h 5,820 1,078 18ms 25ms 346ms 3.4s 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-06/11/2026-09-06T11.parquet sha256sum 2026-09-06T11.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.