Hour audit: 2026-09-21T04
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-21T04 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-21T04:00:00.000006546+00:00 · last event 2026-09-21T04:59:59.999922996+00:00
VOLUME 99,578,414 rows · 990,101,576 bytes (944.23 MiB) · 7 products, all holding rows
WITNESSES cefh — 4 machines contributed rows
captured h: 99,406,610 · e: 99,393,836 · c: 99,384,637 · f: 99,310,701 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 4,358,134 (4.38%) · e: 499,796 (0.50%) · c: 94,497,543 (94.90%) · f: 222,941 (0.22%) (rows of the merged file that came from it; these partition it)
5 expected (cefgh), 1 contributed nothing: g
INTEGRITY sha256 b25a5dfe3775ff0ab699fc4b11f2213ee511e8a403634ae007123e8ca16fab88
the corpus checksum ledger names this file with the same digest
joined 99,579,561 to merged 99,578,414, minus 1,147 (minus 0.0012%)
boundary drops 1,147 · 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-21T06:43:05Z 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 9,081,878 101,776,306 0-34 a72651706813406fb199f09a0ada39cbc92875a7a44abe780f026d3259196aa1 book 185,601 19,128,204 35-35 d195820fb9161d2a6ebed881681d8f77f776aebcb6080db2c1cf28d82596b369 last_trade_price 50,489 2,835,860 36-36 b464ca9efa88e24cbe6b6fdbb595c68c93b8eccb0d77add04db963daf894f96d market_resolved 1,173 191,396 37-37 c88b11aff882e0a234f382b74fbdf99b5ad8f3f64a75682185a91d0a36a68d63 new_market 1,593 164,835 38-38 556991866c14e94de8590e5916524cfec6a7cbeca255b54823810b83ee78022c price_change 90,254,768 864,763,004 39-383 aff86fbbc4364d9e689f16bf4de52744610e855cf9e62a2fbf92c67cbc02911b tick_size_change 2,912 107,009 384-384 e996727d53ac2423303969dce2e28c087f41c01e20f0525ae2a9941a20d512c6 EVENT MIX count share price_change 90,254,768 90.64% best_bid_ask 9,081,878 9.12% book 185,601 0.19% last_trade_price 50,489 0.05% tick_size_change 2,912 <0.01% new_market 1,593 <0.01% market_resolved 1,173 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,082,009 9,081,878 131 67,666 PARTIAL book 185,647 185,601 46 38,672 PARTIAL last_trade_price 50,489 50,489 0 2,615 PARTIAL market_resolved 1,173 1,173 0 1,173 PARTIAL new_market 1,593 1,593 0 1,107 PARTIAL price_change 90,255,738 90,254,768 970 115,237 PARTIAL tick_size_change 2,912 2,912 0 728 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,080,495 8,694,119 4ms 10ms 128ms 5.5s 0 transport_latency_assumed best_bid_ask e 9,080,914 35,600 39ms 47ms 219ms 7.8s 0 transport_latency_assumed best_bid_ask f 9,079,499 14,940 46ms 57ms 242ms 7.9s 0 transport_latency_assumed best_bid_ask h 9,080,935 337,219 18ms 32ms 214ms 18.5s 0 transport_latency_assumed book c 122,176 112,339 6ms 3.7min 13.8d 114.3d 0 book_staleness book e 115,728 12,543 42ms 13.1s 11.8d 114.3d 0 book_staleness book f 123,396 20,723 49ms 6.6min 13.8d 114.3d 0 book_staleness book h 136,775 39,996 23ms 15.6min 16.3d 114.3d 0 book_staleness last_trade_price c 50,172 46,637 5ms 22ms 251ms 4.1s 0 transport_latency_assumed last_trade_price e 50,249 339 41ms 107ms 1.4s 6.3s 0 transport_latency_assumed last_trade_price f 49,888 147 48ms 136ms 1.5s 4.6s 0 transport_latency_assumed last_trade_price h 50,393 3,366 19ms 50ms 361ms 11.2s 0 transport_latency_assumed market_resolved c 1,173 1,145 4ms 38ms 43.4s 1.0min 0 transport_latency_assumed market_resolved e 1,173 6 40ms 271ms 44.2s 1.0min 0 transport_latency_assumed market_resolved f 1,173 1 47ms 297ms 44.3s 1.0min 0 transport_latency_assumed market_resolved h 1,173 21 18ms 156ms 43.5s 1.0min 0 transport_latency_assumed new_market c 1,107 601 179ms 16.1s 21.4s 26.7s 0 transport_latency_assumed new_market e 1,107 210 283ms 18.1s 24.1s 28.8s 0 transport_latency_assumed new_market f 1,107 350 217ms 18.9s 22.4s 25.2s 0 transport_latency_assumed new_market h 1,107 432 201ms 18.9s 22.5s 28.4s 0 transport_latency_assumed price_change c 90,126,602 85,640,002 4ms 13ms 157ms 6.1s 0 transport_latency_assumed price_change e 90,141,753 451,078 40ms 55ms 394ms 8.4s 0 transport_latency_assumed price_change f 90,052,726 186,772 47ms 65ms 395ms 8.5s 0 transport_latency_assumed price_change h 90,133,315 3,976,916 18ms 37ms 273ms 18.8s 0 transport_latency_assumed tick_size_change c 2,912 2,700 4ms 19ms 247ms 2.4s 0 transport_latency_assumed tick_size_change e 2,912 20 40ms 56ms 495ms 724ms 0 transport_latency_assumed tick_size_change f 2,912 8 46ms 77ms 507ms 659ms 0 transport_latency_assumed tick_size_change h 2,912 184 18ms 42ms 333ms 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-21/04/2026-09-21T04.parquet sha256sum 2026-09-21T04.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.