Hour audit: 2026-09-21T11
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-21T11 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-21T11:00:00.000126104+00:00 · last event 2026-09-21T11:59:59.999985854+00:00
VOLUME 114,524,404 rows · 1,198,731,730 bytes (1.12 GiB) · 7 products, all holding rows
WITNESSES cefh — 4 machines contributed rows
captured h: 113,547,837 · f: 113,513,234 · e: 113,498,567 · c: 105,352,567 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 13,446,961 (11.74%) · f: 414,328 (0.36%) · e: 1,087,162 (0.95%) · c: 99,575,953 (86.95%) (rows of the merged file that came from it; these partition it)
5 expected (cefgh), 1 contributed nothing: g
INTEGRITY sha256 396a993d57bb89b40397374dbb90aa1f9e9ab5d0e3dca1244602c9735b567118
the corpus checksum ledger names this file with the same digest
joined 114,525,632 to merged 114,524,404, minus 1,228 (minus 0.0011%)
boundary drops 1,228 · 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-21T12:56:29Z 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,985,822 122,038,846 0-41 2799d92a9f5efab62f1615e82e73a62aa7ac20f980532f5a38e94d3ff447528a book 865,385 58,662,729 42-45 ad9e769099737533184c866453a543d9a9a8f0ea4fe3e14337ecdf68467840b7 last_trade_price 57,991 3,263,462 46-46 f0a41fcd966dffa6187f73eb42c82e2c5b47c0722c294508141bebccda0bcf14 market_resolved 806 121,928 47-47 a2b012fa587c58c7e211938742e5348ab7dfc047035f3c7d8155ae68b563ca50 new_market 1,110 114,879 48-48 5343141ec72ec98c15ebdef65c36c75dc1301e131b9fa457f713c7a5979fc1fe price_change 102,610,070 1,013,109,736 49-440 ffaa9b4b4e4efe44795f8b703c2aa03f2deadba186cd5faaf458222c3cf0ae6a tick_size_change 3,220 117,391 441-441 f774cb1b8ddd9eec137680235b487d5427f1f1d82c1bb634a1435344bdcdc19f EVENT MIX count share price_change 102,610,070 89.60% best_bid_ask 10,985,822 9.59% book 865,385 0.76% last_trade_price 57,991 0.05% tick_size_change 3,220 <0.01% new_market 1,110 <0.01% market_resolved 806 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,985,962 10,985,822 140 64,901 PARTIAL book 865,449 865,385 64 150,741 PARTIAL last_trade_price 57,991 57,991 0 3,208 PARTIAL market_resolved 806 806 0 750 PARTIAL new_market 1,110 1,110 0 739 PARTIAL price_change 102,611,094 102,610,070 1,024 116,211 PARTIAL tick_size_change 3,220 3,220 0 805 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,196,006 9,684,981 6ms 14ms 103ms 3.3s 0 transport_latency_assumed best_bid_ask e 10,982,229 85,499 41ms 52ms 209ms 13.9s 0 transport_latency_assumed best_bid_ask f 10,982,226 22,445 49ms 62ms 226ms 17.3s 0 transport_latency_assumed best_bid_ask h 10,984,315 1,192,897 18ms 31ms 135ms 49.4s 0 transport_latency_assumed book c 732,285 720,813 5.8min 2.8d 43.9d 114.5d 0 book_staleness book e 208,758 66,334 560ms 44.3min 29.9d 114.6d 0 book_staleness book f 201,554 59,689 316ms 36.9min 29.9d 114.6d 0 book_staleness book h 122,085 18,549 22ms 148ms 36.0min 96.0d 0 book_staleness last_trade_price c 52,774 49,516 7ms 25ms 213ms 2.9s 0 transport_latency_assumed last_trade_price e 57,160 683 45ms 535ms 7.6s 13.9s 0 transport_latency_assumed last_trade_price f 57,128 371 52ms 471ms 5.7s 17.3s 0 transport_latency_assumed last_trade_price h 57,555 7,421 20ms 70ms 410ms 40.9s 0 transport_latency_assumed market_resolved c 724 578 7ms 42.2s 3.2min 4.2min 0 transport_latency_assumed market_resolved e 750 142 44ms 32.8s 1.0min 1.0min 0 transport_latency_assumed market_resolved f 750 28 50ms 31.0s 55.8s 58.1s 0 transport_latency_assumed market_resolved h 750 58 19ms 34.9s 52.1s 59.7s 0 transport_latency_assumed new_market c 745 470 193ms 31.9s 2.4min 4.1min 0 transport_latency_assumed new_market e 739 112 355ms 31.3s 48.7s 1.3min 0 transport_latency_assumed new_market f 739 180 330ms 25.8s 42.5s 44.4s 0 transport_latency_assumed new_market h 739 348 209ms 29.7s 48.7s 1.3min 0 transport_latency_assumed price_change c 94,367,053 89,116,769 6ms 17ms 133ms 4.1s 0 transport_latency_assumed price_change e 102,245,711 934,374 42ms 72ms 1.4s 13.9s 0 transport_latency_assumed price_change f 102,267,617 331,614 49ms 80ms 1.3s 17.4s 0 transport_latency_assumed price_change h 102,379,173 12,227,313 18ms 38ms 241ms 49.6s 0 transport_latency_assumed tick_size_change c 2,980 2,826 6ms 12ms 153ms 226ms 0 transport_latency_assumed tick_size_change e 3,220 18 41ms 49ms 106ms 199ms 0 transport_latency_assumed tick_size_change f 3,220 1 49ms 58ms 117ms 182ms 0 transport_latency_assumed tick_size_change h 3,220 375 18ms 26ms 66ms 239ms 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/11/2026-09-21T11.parquet sha256sum 2026-09-21T11.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.