Hour audit: 2026-09-06T18
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-06T18 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-06T18:00:00.069165678+00:00 · last event 2026-09-06T18:59:59.999994335+00:00
VOLUME 122,698,005 rows · 1,325,464,535 bytes (1.23 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 120,816,318 · h: 120,681,288 · e: 120,644,216 · g: 116,221,749 · c: 98,389,928 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 532,347 (0.43%) · h: 27,476,427 (22.39%) · e: 1,705,838 (1.39%) · g: 183,685 (0.15%) · c: 92,799,708 (75.63%) (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,698,005 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 78061b2f35eeee6b5685a89dfcf034ad12b6e20342b7cdc98f578993491d6453
the corpus checksum ledger names this file with the same digest
joined 122,700,472 to merged 122,698,005, minus 2,467 (minus 0.0020%)
boundary drops 2,467 · 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-07T00:54:50Z 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,914,705 136,392,985 0-45 7b89b92efb3a3737e7fa7b191217c215c5a26cebb4ab4e76c5e14d38ab690e26 book 1,918,165 84,971,505 46-53 82067210f658f6dc19242491aa4171214ffd9a13faf24d98b07fe8c28abf7c4b last_trade_price 64,551 3,736,903 54-54 8dfc7f0f908875fcb5dfe5cec57cc4283be3a34acd171fbc816a81d071c638d0 market_resolved 4,316 497,151 55-55 ac1049e0dbe86de9f60cefd7e0d56a703da18d1c366e1596f8afab1cf0a6526e new_market 4,488 422,897 56-56 4a0f5d9ae50e87b6cf6e981749432d38999a726fb7da9155549797cc0710f29a price_change 108,785,280 1,097,812,133 57-471 675cde0ff2b5115da0574ab2d7301a1e07c405e9532d4b4ca1f36a7e30bf4c83 tick_size_change 6,500 236,186 472-472 a6464605e17caf122e8fd26946377617c12021053463aec24a88aedf485d5a46 EVENT MIX count share price_change 108,785,280 88.66% best_bid_ask 11,914,705 9.71% book 1,918,165 1.56% last_trade_price 64,551 0.05% tick_size_change 6,500 <0.01% new_market 4,488 <0.01% market_resolved 4,316 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,914,972 11,914,705 267 3,354 FULL book 1,918,327 1,918,165 162 172,144 FULL last_trade_price 64,551 64,551 0 443 FULL market_resolved 4,316 4,316 0 105 FULL new_market 4,488 4,488 0 7 FULL price_change 108,787,318 108,785,280 2,038 1,770 FULL tick_size_change 6,500 6,500 0 369 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,494,991 8,968,819 5ms 15ms 246ms 10.5s 0 transport_latency_assumed best_bid_ask e 11,910,096 168,949 38ms 54ms 340ms 12.0s 0 transport_latency_assumed best_bid_ask f 11,909,827 50,059 45ms 64ms 349ms 16.6s 0 transport_latency_assumed best_bid_ask g 11,418,943 3,621 83ms 151ms 849ms 33.1s 0 transport_latency_assumed best_bid_ask h 11,911,098 2,723,257 18ms 33ms 428ms 1.4min 0 transport_latency_assumed book c 1,874,077 1,734,603 4.8min 24.0h 35.3d 99.9d 0 book_staleness book e 137,633 5,238 41ms 250ms 6.0s 37.4d 0 book_staleness book f 137,703 2,853 48ms 259ms 4.9s 81.3d 0 book_staleness book g 491,333 142,871 1.3min 15.3h 31.9d 99.8d 0 book_staleness book h 137,597 32,600 23ms 103ms 4.0s 81.3d 0 book_staleness last_trade_price c 50,864 47,597 11ms 54ms 432ms 5.0s 0 transport_latency_assumed last_trade_price e 64,496 1,121 45ms 181ms 3.4s 12.0s 0 transport_latency_assumed last_trade_price f 64,511 356 52ms 191ms 3.0s 16.7s 0 transport_latency_assumed last_trade_price g 61,448 44 95ms 414ms 10.0s 33.1s 0 transport_latency_assumed last_trade_price h 64,483 15,433 24ms 79ms 919ms 38.1s 0 transport_latency_assumed market_resolved c 3,526 3,386 7ms 9.4min 14.4min 14.8min 0 transport_latency_assumed market_resolved e 2,997 159 42ms 253ms 55.0s 1.1min 0 transport_latency_assumed market_resolved f 2,997 15 48ms 214ms 49.7s 1.0min 0 transport_latency_assumed market_resolved g 2,940 2 90ms 377ms 1.2s 54.4s 0 transport_latency_assumed market_resolved h 2,997 754 22ms 90ms 57.1s 1.0min 0 transport_latency_assumed new_market c 2,765 1,694 147ms 22.1s 36.6min 2.9h 0 transport_latency_assumed new_market e 2,672 660 205ms 17.9s 44.9s 4.9d 0 transport_latency_assumed new_market f 2,672 572 217ms 17.5s 44.9s 1.3h 0 transport_latency_assumed new_market g 2,666 460 378ms 18.8s 46.3s 4.9d 0 transport_latency_assumed new_market h 2,672 1,102 174ms 18.9s 44.8s 1.3h 0 transport_latency_assumed price_change c 86,958,681 82,038,841 5ms 16ms 261ms 11.0s 0 transport_latency_assumed price_change e 108,519,822 1,529,610 39ms 63ms 408ms 12.2s 0 transport_latency_assumed price_change f 108,692,108 478,474 45ms 72ms 406ms 16.7s 0 transport_latency_assumed price_change g 104,238,211 36,687 84ms 169ms 1.1s 33.7s 0 transport_latency_assumed price_change h 108,555,941 24,701,668 18ms 36ms 441ms 1.4min 0 transport_latency_assumed tick_size_change c 5,024 4,768 5ms 12ms 159ms 365ms 0 transport_latency_assumed tick_size_change e 6,500 101 38ms 44ms 161ms 522ms 0 transport_latency_assumed tick_size_change f 6,500 18 45ms 51ms 173ms 430ms 0 transport_latency_assumed tick_size_change g 6,208 not meas. 81ms 118ms 375ms 728ms 0 transport_latency_assumed tick_size_change h 6,500 1,613 18ms 30ms 145ms 1.9s 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/18/2026-09-06T18.parquet sha256sum 2026-09-06T18.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.