Hour audit: 2026-09-05T09
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-05T09 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-05T09:00:00.023872743+00:00 · last event 2026-09-05T09:59:59.999998034+00:00
VOLUME 105,179,475 rows · 1,057,991,487 bytes (1008.98 MiB) · 7 products, all holding rows
WITNESSES bcefgh — 6 machines contributed rows
captured c: 104,660,719 · e: 104,649,756 · h: 104,621,906 · b: 104,619,406 · f: 11,768,938 · g: 9,865,560 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 6,017 (0.01%) · e: 93,240,264 (88.65%) · h: 14,944 (0.01%) · b: 6,863 (0.01%) · f: 2,045,831 (1.95%) · g: 9,865,556 (9.38%) (rows of the merged file that came from it; these partition it)
6 product-machine pairs publish no supplied count; the figures above still sum to the file's 105,179,475 rows exactly, so those pairs supplied none
6 expected, all 6 contributed
INTEGRITY sha256 430451f5e649446e156fd0a079ce8f1549b230a628b747ff0bbe1f3229d97b02
the corpus checksum ledger names this file with the same digest
joined 105,181,799 to merged 105,179,475, minus 2,324 (minus 0.0022%)
boundary drops 2,324 · 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-05T17:56:35Z as bcefgh
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,818,248 105,744,589 0-37 7b97389470209f66abac43c8b12fe94b3fba1ba9c2f460a57e079970791105e0 book 632,771 62,319,424 38-40 81749b5f389dc460998b1de451f0bbd17156478e936182ad19f5d60148acf741 last_trade_price 57,684 3,334,837 41-41 30fdc8699a6e3bb32b644c2d04a102c92c110fab0cefde778b5ba72d2ad68066 market_resolved 402 66,519 42-42 e4281d5d4f9b10e1b5dc8a13bf77e7f62bc394d5a1562716002588c5476d8200 new_market 1,016 108,450 43-43 eabf7fd4796fd1865b9e14cbee8d69f5c9f5fb521c1e8ac17f4ee4eecc1edefc price_change 94,666,614 885,114,176 44-405 f482555c5afab92f8c5fcb32226e29e5a90832894b768de9d8615d4cea045744 tick_size_change 2,740 101,195 406-406 e7a5e238c740706e5c41cfbcc3a26a6efe3157b8e141e3070f46e4957902ded4 EVENT MIX count share price_change 94,666,614 90.00% best_bid_ask 9,818,248 9.33% book 632,771 0.60% last_trade_price 57,684 0.05% tick_size_change 2,740 <0.01% new_market 1,016 <0.01% market_resolved 402 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,818,383 9,818,248 135 39,317 FULL book 632,775 632,771 4 187,163 FULL last_trade_price 57,685 57,684 1 3,392 FULL market_resolved 402 402 0 368 FULL new_market 1,016 1,016 0 686 FULL price_change 94,668,798 94,666,614 2,184 26,619 FULL tick_size_change 2,740 2,740 0 596 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 9,815,949 74 56ms 68ms 175ms 3.9s 0 transport_latency_assumed best_bid_ask c 9,817,832 874 4ms 6ms 40ms 3.3s 0 transport_latency_assumed best_bid_ask e 9,816,162 8,743,751 38ms 42ms 110ms 1.9s 0 transport_latency_assumed best_bid_ask f 1,070,263 191,132 47ms 52ms 140ms 2.2s 0 transport_latency_assumed best_bid_ask g 881,219 881,219 82ms 99ms 311ms 8.1s 0 transport_latency_assumed best_bid_ask h 9,816,930 1,198 17ms 20ms 78ms 7.4s 0 transport_latency_assumed book b 129,276 6,368 59ms 284ms 10.3h 98.5d 0 book_staleness book c 120,347 1,141 6ms 11ms 4.4s 79.9d 0 book_staleness book e 122,347 106,443 40ms 88ms 30.5min 79.9d 0 book_staleness book f 398,907 120,482 3.3min 12.9h 33.9d 98.5d 0 book_staleness book g 397,654 397,650 3.3min 13.0h 33.9d 98.5d 0 book_staleness book h 119,317 687 20ms 37ms 362ms 33.9d 0 book_staleness last_trade_price b 57,661 5 63ms 103ms 730ms 5.0s 0 transport_latency_assumed last_trade_price c 57,662 9 9ms 34ms 216ms 5.0s 0 transport_latency_assumed last_trade_price e 57,661 50,561 44ms 77ms 612ms 5.0s 0 transport_latency_assumed last_trade_price f 6,987 736 52ms 86ms 421ms 5.0s 0 transport_latency_assumed last_trade_price g 6,364 6,364 83ms 124ms 557ms 5.1s 0 transport_latency_assumed last_trade_price h 57,643 9 22ms 50ms 319ms 5.6s 0 transport_latency_assumed market_resolved b 402 not meas. 58ms 368ms 695ms 1.4s 0 transport_latency_assumed market_resolved c 402 not meas. 4ms 10ms 58ms 149ms 0 transport_latency_assumed market_resolved e 402 359 40ms 276ms 643ms 776ms 0 transport_latency_assumed market_resolved f 43 9 46ms 51ms 52ms 52ms 0 transport_latency_assumed market_resolved g 34 34 77ms 86ms 98ms 99ms 0 transport_latency_assumed market_resolved h 402 not meas. 18ms 112ms 315ms 733ms 0 transport_latency_assumed new_market b 721 56 193ms 19.1s 53.7s 1.3min 0 transport_latency_assumed new_market c 721 87 53ms 20.8s 53.5s 1.0min 0 transport_latency_assumed new_market e 721 690 128ms 18.9s 39.3s 54.7s 0 transport_latency_assumed new_market f 38 8 60ms 2.5min 2.5min 2.5min 0 transport_latency_assumed new_market g 35 35 85ms 3.1min 3.1min 3.1min 0 transport_latency_assumed new_market h 721 140 103ms 18.0s 45.9s 1.3min 0 transport_latency_assumed price_change b 94,612,657 360 56ms 69ms 209ms 3.9s 0 transport_latency_assumed price_change c 94,661,015 3,906 4ms 7ms 49ms 3.3s 0 transport_latency_assumed price_change e 94,649,723 84,336,088 38ms 43ms 140ms 2.5s 0 transport_latency_assumed price_change f 10,292,332 1,733,452 47ms 56ms 238ms 2.4s 0 transport_latency_assumed price_change g 8,579,898 8,579,898 80ms 102ms 504ms 9.3s 0 transport_latency_assumed price_change h 94,624,153 12,910 17ms 21ms 97ms 7.4s 0 transport_latency_assumed tick_size_change b 2,740 not meas. 56ms 68ms 108ms 157ms 0 transport_latency_assumed tick_size_change c 2,740 not meas. 4ms 6ms 19ms 46ms 0 transport_latency_assumed tick_size_change e 2,740 2,372 38ms 42ms 53ms 125ms 0 transport_latency_assumed tick_size_change f 368 12 47ms 111ms 155ms 161ms 0 transport_latency_assumed tick_size_change g 356 356 77ms 112ms 237ms 245ms 0 transport_latency_assumed tick_size_change h 2,740 not meas. 17ms 20ms 40ms 83ms 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-05/09/2026-09-05T09.parquet sha256sum 2026-09-05T09.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.