Hour audit: 2026-09-21T16
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.
1 finding
- a machine expected this hour contributed nothing. Of the 5 machines expected to be capturing this hour, 1 contributed no rows: g. The hour is still whole on minutes; it simply rests on 4 machines rather than 5.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-21T16 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-21T16:00:00.000032012+00:00 · last event 2026-09-21T16:59:59.999834394+00:00
VOLUME 106,882,608 rows · 1,153,924,086 bytes (1.07 GiB) · 7 products, all holding rows
WITNESSES cefh — 4 machines contributed rows
captured h: 105,645,643 · f: 105,162,464 · e: 105,073,877 · c: 93,351,313 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 17,511,615 (16.38%) · f: 461,948 (0.43%) · e: 906,544 (0.85%) · c: 88,002,501 (82.34%) (rows of the merged file that came from it; these partition it)
5 expected (cefgh), 1 contributed nothing: g
INTEGRITY sha256 5c49db9ce33f562fb316eaf630c38d915dda27223a2963dace98a525884f74e4
the corpus checksum ledger names this file with the same digest
joined 106,884,036 to merged 106,882,608, minus 1,428 (minus 0.0013%)
boundary drops 1,428 · 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-21T17:53:48Z as cefh
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 7/8 pass, 1 finding
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
FINDING a machine expected this hour contributed nothing
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,117,470 118,096,305 0-38 d04f56d19fb09cd9efe0780dcc1f04fb6399bf4cd6bcea2b3fc450d42180dade book 1,304,721 70,516,630 39-43 d5dd0463a4edb375f4d3791a593a479d0116eff859cf68ad3b7854fb0cc6728e last_trade_price 70,168 3,958,999 44-44 06ffeca50ef8e50e516d782bb1ea4125aafed3eab7e2b9eb74c2ff99fa2bdf34 market_resolved 1,710 210,598 45-45 012d659d3b15becd0836c7211e67b604b7ba48c3799cda56c2ec233b0a4de4a4 new_market 2,209 220,637 46-46 f669a195ae54fc5d7549e561b775290695b134fea25dd4b91cb2d4f3901d079f price_change 95,381,406 959,526,940 47-410 b15c32560deea26236ce87baac6b3bc306f7c78a4e93d6b2d05096ef6b0a35b9 tick_size_change 4,924 179,579 411-411 cf18ceda0d16b04ef807ceed9919ea8f339b4d163a0fc627bacfab1b4ae6c46a EVENT MIX count share price_change 95,381,406 89.24% best_bid_ask 10,117,470 9.47% book 1,304,721 1.22% last_trade_price 70,168 0.07% tick_size_change 4,924 <0.01% new_market 2,209 <0.01% market_resolved 1,710 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,117,580 10,117,470 110 75,581 PARTIAL book 1,305,021 1,304,721 300 156,762 PARTIAL last_trade_price 70,168 70,168 0 3,575 PARTIAL market_resolved 1,710 1,710 0 1,272 PARTIAL new_market 2,209 2,209 0 1,414 PARTIAL price_change 95,382,424 95,381,406 1,018 122,672 PARTIAL tick_size_change 4,924 4,924 0 1,231 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,902,673 8,424,073 6ms 16ms 137ms 3.5s 0 transport_latency_assumed best_bid_ask e 10,109,926 72,651 42ms 58ms 342ms 21.8s 0 transport_latency_assumed best_bid_ask f 10,110,017 28,250 48ms 66ms 346ms 25.9s 0 transport_latency_assumed best_bid_ask h 10,115,136 1,592,496 19ms 32ms 212ms 51.1s 0 transport_latency_assumed book c 1,123,637 1,106,195 4.9min 3.0d 44.1d 114.8d 0 book_staleness book e 201,949 43,149 122ms 16.6min 25.9d 114.8d 0 book_staleness book f 256,538 79,571 1.8s 41.8min 30.1d 114.8d 0 book_staleness book h 221,029 75,806 42ms 19.5min 30.1d 114.8d 0 book_staleness last_trade_price c 61,440 57,913 7ms 23ms 201ms 3.2s 0 transport_latency_assumed last_trade_price e 68,166 543 48ms 1.2s 10.0s 22.0s 0 transport_latency_assumed last_trade_price f 68,227 276 55ms 1.5s 9.9s 26.0s 0 transport_latency_assumed last_trade_price h 69,984 11,436 20ms 77ms 461ms 9.6s 0 transport_latency_assumed market_resolved c 1,440 1,328 8ms 9.0min 15.3min 15.6min 0 transport_latency_assumed market_resolved e 1,272 20 44ms 278ms 57.3s 1.0min 0 transport_latency_assumed market_resolved f 1,272 17 50ms 278ms 48.0s 58.1s 0 transport_latency_assumed market_resolved h 1,272 345 20ms 126ms 58.2s 1.0min 0 transport_latency_assumed new_market c 1,634 1,071 184ms 4.2min 11.7min 12.0min 0 transport_latency_assumed new_market e 1,414 339 285ms 25.9s 1.3min 1.5min 0 transport_latency_assumed new_market f 1,414 340 283ms 26.8s 1.2min 1.4min 0 transport_latency_assumed new_market h 1,414 459 184ms 24.7s 1.3min 1.5min 0 transport_latency_assumed price_change c 83,255,893 78,407,561 6ms 19ms 171ms 3.9s 0 transport_latency_assumed price_change e 94,686,226 789,818 43ms 100ms 3.7s 22.1s 0 transport_latency_assumed price_change f 94,720,072 353,482 48ms 108ms 3.8s 26.0s 0 transport_latency_assumed price_change h 95,231,884 15,830,545 19ms 41ms 354ms 52.9s 0 transport_latency_assumed tick_size_change c 4,596 4,360 6ms 13ms 79ms 482ms 0 transport_latency_assumed tick_size_change e 4,924 24 42ms 57ms 192ms 417ms 0 transport_latency_assumed tick_size_change f 4,924 12 48ms 61ms 208ms 484ms 0 transport_latency_assumed tick_size_change h 4,924 528 19ms 29ms 143ms 427ms 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-21/16/2026-09-21T16.parquet sha256sum 2026-09-21T16.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.