Hour audit: 2026-09-21T06
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-21T06 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-21T06:00:00.000207439+00:00 · last event 2026-09-21T06:59:59.999831661+00:00
VOLUME 97,330,215 rows · 976,891,326 bytes (931.64 MiB) · 7 products, all holding rows
WITNESSES cefh — 4 machines contributed rows
captured f: 97,093,011 · c: 97,080,326 · h: 97,056,640 · e: 97,045,732 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 241,977 (0.25%) · c: 93,463,929 (96.03%) · h: 3,262,818 (3.35%) · e: 361,491 (0.37%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 97,330,215 rows exactly, so those pairs supplied none
5 expected (cefgh), 1 contributed nothing: g
INTEGRITY sha256 45a95122358afa2edb86e42d51f7672435ad28b69f16b268d5f9b6764ed88484
the corpus checksum ledger names this file with the same digest
joined 97,331,289 to merged 97,330,215, minus 1,074 (minus 0.0011%)
boundary drops 1,074 · 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-21T07:53:16Z 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 8,967,748 99,354,663 0-34 a09afa6d4540fbdc18341e9f73af1dd2aa548a81f9dad35c6f15182dee2167c8 book 285,597 29,134,424 35-36 4f258bad765edaa39f16d95bf3d59ea68db791071f592a2bfd3940f4ec701b3a last_trade_price 48,115 2,737,935 37-37 484c6f1fef33b7eb3b347b6b4dec67673cbb8aff9170780b105b107d4d18fd12 market_resolved 1,150 188,274 38-38 246c679536148f7392168a794046c6149a669ad4f1236927cc8e10dba5de7e34 new_market 2,261 226,252 39-39 00ba46bc353d24a70d1f0114df06a6ba356ceb4ddccac2d2eac244a4ce880bf6 price_change 88,023,060 844,055,266 40-375 77d4e428aecb8553b5dd7a3802b5e8e79e7e4e53fe065b906b71467470fbb641 tick_size_change 2,284 83,370 376-376 f29083f6f7af171d2f5b74514ea5c3a6f4959c45306313dc0b52adea72c3d1a3 EVENT MIX count share price_change 88,023,060 90.44% best_bid_ask 8,967,748 9.21% book 285,597 0.29% last_trade_price 48,115 0.05% tick_size_change 2,284 <0.01% new_market 2,261 <0.01% market_resolved 1,150 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,967,840 8,967,748 92 64,867 PARTIAL book 285,601 285,597 4 84,965 PARTIAL last_trade_price 48,115 48,115 0 3,281 PARTIAL market_resolved 1,150 1,150 0 1,150 PARTIAL new_market 2,261 2,261 0 1,520 PARTIAL price_change 88,024,038 88,023,060 978 116,232 PARTIAL tick_size_change 2,284 2,284 0 571 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,965,745 8,679,233 4ms 8ms 97ms 3.6s 0 transport_latency_assumed best_bid_ask e 8,964,570 21,768 42ms 48ms 218ms 9.5s 0 transport_latency_assumed best_bid_ask f 8,963,876 10,728 46ms 55ms 259ms 11.3s 0 transport_latency_assumed best_bid_ask h 8,964,950 256,019 18ms 26ms 199ms 45.2s 0 transport_latency_assumed book c 115,120 107,479 6ms 1.3min 13.4d 114.4d 0 book_staleness book e 182,443 72,346 277ms 2.5h 29.7d 114.4d 0 book_staleness book f 188,270 76,275 480ms 3.9h 29.7d 114.3d 0 book_staleness book h 125,273 29,497 23ms 10.3min 15.7d 114.4d 0 book_staleness last_trade_price c 48,035 45,853 5ms 14ms 173ms 1.5s 0 transport_latency_assumed last_trade_price e 48,038 202 44ms 141ms 3.4s 9.6s 0 transport_latency_assumed last_trade_price f 47,816 69 48ms 137ms 1.6s 11.3s 0 transport_latency_assumed last_trade_price h 47,924 1,991 19ms 51ms 342ms 8.3s 0 transport_latency_assumed market_resolved c 1,150 985 4ms 296ms 53.9s 55.6s 0 transport_latency_assumed market_resolved e 1,150 98 43ms 693ms 53.6s 55.4s 0 transport_latency_assumed market_resolved f 1,150 15 48ms 715ms 53.6s 55.7s 0 transport_latency_assumed market_resolved h 1,150 52 18ms 716ms 55.2s 57.3s 0 transport_latency_assumed new_market c 1,520 1,010 111ms 22.9s 58.2s 1.6min 0 transport_latency_assumed new_market e 1,520 231 234ms 25.5s 1.3min 1.6min 0 transport_latency_assumed new_market f 1,520 464 208ms 24.6s 1.3min 1.6min 0 transport_latency_assumed new_market h 1,520 556 186ms 23.7s 1.0min 1.6min 0 transport_latency_assumed price_change c 87,946,472 84,627,133 4ms 10ms 121ms 4.2s 0 transport_latency_assumed price_change e 87,845,727 266,846 42ms 55ms 329ms 9.8s 0 transport_latency_assumed price_change f 87,888,095 154,426 47ms 63ms 358ms 11.3s 0 transport_latency_assumed price_change h 87,913,539 2,974,655 18ms 32ms 250ms 45.7s 0 transport_latency_assumed tick_size_change c 2,284 2,236 4ms 6ms 83ms 211ms 0 transport_latency_assumed tick_size_change e 2,284 not meas. 42ms 48ms 190ms 615ms 0 transport_latency_assumed tick_size_change f 2,284 not meas. 46ms 51ms 267ms 509ms 0 transport_latency_assumed tick_size_change h 2,284 48 18ms 22ms 127ms 312ms 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/06/2026-09-21T06.parquet sha256sum 2026-09-21T06.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.