Hour audit: 2026-09-05T23
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-05T23 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-05T23:00:00.086406361+00:00 · last event 2026-09-05T23:59:59.999998214+00:00
VOLUME 126,412,621 rows · 1,322,050,012 bytes (1.23 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 124,265,141 · e: 124,246,466 · h: 124,233,582 · g: 123,300,185 · c: 99,549,322 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 990,940 (0.78%) · e: 14,955 (0.01%) · h: 22,137 (0.02%) · g: 123,299,951 (97.54%) · c: 2,084,638 (1.65%) (rows of the merged file that came from it; these partition it)
5 product-machine pairs publish no supplied count; the figures above still sum to the file's 126,412,621 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 41461a517ea8bac5e5b4a0152aebbd87e0bb2e0206c828a455539b23bf463f25
the corpus checksum ledger names this file with the same digest
joined 126,416,015 to merged 126,412,621, minus 3,394 (minus 0.0027%)
boundary drops 3,394 · 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-06T03:23:19Z 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 12,412,622 136,446,681 0-47 aae4dbd6affee0c825ce302fe5b16ac821c6cacb56d7560c364be096a7eeaa71 book 2,198,845 85,173,481 48-56 1404e0064ac0a375d2d84be305c5ce358360b1979e0d5845ca33ffc418c3b025 last_trade_price 55,292 3,169,044 57-57 6df6f14e9979c53fa8adf02509ebe12cc851758af4eecc13bd1986e9c35ce563 market_resolved 5,693 597,315 58-58 37b3734d6a03f2ab5e62c3fb5b8e2741cd9cbb9ea1c23f2d9e8ea5660b5ceb14 new_market 4,427 388,766 59-59 eb2eb0447c3d7a1578b4706b05bc1bd1c931e9190ff2ce2f85ed926a1bfcdcf3 price_change 111,729,750 1,094,618,485 60-486 97034db14f2fa4ee4b2d59e79b296242a590f59cbe75304e069980929eb02a87 tick_size_change 5,992 217,771 487-487 fb3b91479499255ae82c19084e957f07fb72c62a1fcde756396159a03fa25315 EVENT MIX count share price_change 111,729,750 88.38% best_bid_ask 12,412,622 9.82% book 2,198,845 1.74% last_trade_price 55,292 0.04% tick_size_change 5,992 <0.01% market_resolved 5,693 <0.01% new_market 4,427 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,412,640 12,412,622 18 3,692 FULL book 2,202,115 2,198,845 3,270 182,947 FULL last_trade_price 55,292 55,292 0 485 FULL market_resolved 5,693 5,693 0 281 FULL new_market 4,427 4,427 0 5 FULL price_change 111,729,856 111,729,750 106 2,548 FULL tick_size_change 5,992 5,992 0 409 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,774,587 498 4ms 9ms 89ms 3.2s 0 transport_latency_assumed best_bid_ask e 12,410,807 701 40ms 51ms 302ms 18.4s 0 transport_latency_assumed best_bid_ask f 12,410,330 44,004 49ms 65ms 342ms 11.7s 0 transport_latency_assumed best_bid_ask g 12,366,530 12,366,512 84ms 163ms 1.6s 37.2s 0 transport_latency_assumed best_bid_ask h 12,411,026 907 18ms 40ms 618ms 1.9min 0 transport_latency_assumed book c 2,163,156 2,059,545 12.5min 12.1h 34.5d 99.1d 0 book_staleness book e 117,894 667 42ms 202ms 8.5s 14.5d 0 book_staleness book f 118,238 8,634 51ms 236ms 7.6s 33.2d 0 book_staleness book g 125,811 125,701 88ms 15.7s 8.8h 38.3d 0 book_staleness book h 121,463 4,298 22ms 221ms 2.2h 80.5d 0 book_staleness last_trade_price c 42,367 5 9ms 37ms 211ms 5.0s 0 transport_latency_assumed last_trade_price e 55,250 86 46ms 131ms 4.3s 18.4s 0 transport_latency_assumed last_trade_price f 55,186 3,558 55ms 150ms 4.3s 11.7s 0 transport_latency_assumed last_trade_price g 51,637 51,637 91ms 242ms 9.3s 34.9s 0 transport_latency_assumed last_trade_price h 55,179 6 23ms 80ms 1.2s 54.0s 0 transport_latency_assumed market_resolved c 4,838 2,286 11ms 10.6min 15.6min 16.1min 0 transport_latency_assumed market_resolved e 3,398 not meas. 42ms 144ms 500ms 42.6s 0 transport_latency_assumed market_resolved f 3,398 12 51ms 153ms 569ms 1.0min 0 transport_latency_assumed market_resolved g 3,395 3,395 91ms 289ms 2.1s 46.7s 0 transport_latency_assumed market_resolved h 3,398 not meas. 22ms 80ms 770ms 44.6s 0 transport_latency_assumed new_market c 3,238 938 124ms 9.9min 53.6min 3.0h 0 transport_latency_assumed new_market e 2,383 263 194ms 35.0s 2.9min 3.4min 0 transport_latency_assumed new_market f 2,383 761 229ms 38.0s 2.9min 1.8h 0 transport_latency_assumed new_market g 2,383 2,383 311ms 26.2s 2.8min 1.8h 0 transport_latency_assumed new_market h 2,383 82 183ms 33.1s 2.9min 3.2min 0 transport_latency_assumed price_change c 87,556,760 21,366 4ms 9ms 94ms 3.2s 0 transport_latency_assumed price_change e 111,650,742 13,238 40ms 57ms 352ms 18.5s 0 transport_latency_assumed price_change f 111,669,614 933,935 49ms 70ms 389ms 11.7s 0 transport_latency_assumed price_change g 110,744,473 110,744,367 84ms 190ms 3.1s 37.4s 0 transport_latency_assumed price_change h 111,634,141 16,844 18ms 42ms 603ms 1.9min 0 transport_latency_assumed tick_size_change c 4,376 not meas. 4ms 7ms 67ms 194ms 0 transport_latency_assumed tick_size_change e 5,992 not meas. 40ms 51ms 166ms 399ms 0 transport_latency_assumed tick_size_change f 5,992 36 49ms 69ms 247ms 529ms 0 transport_latency_assumed tick_size_change g 5,956 5,956 83ms 177ms 437ms 17.6s 0 transport_latency_assumed tick_size_change h 5,992 not meas. 18ms 32ms 261ms 14.7s 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/23/2026-09-05T23.parquet sha256sum 2026-09-05T23.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.