Hour audit: 2026-09-21T05
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-21T05 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-21T05:00:00.000036116+00:00 · last event 2026-09-21T05:59:59.999701364+00:00
VOLUME 96,334,197 rows · 948,309,195 bytes (904.38 MiB) · 7 products, all holding rows
WITNESSES cefh — 4 machines contributed rows
captured c: 96,215,607 · h: 96,206,393 · f: 96,203,354 · e: 96,152,903 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 92,743,286 (96.27%) · h: 3,268,608 (3.39%) · f: 139,903 (0.15%) · e: 182,400 (0.19%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 96,334,197 rows exactly, so those pairs supplied none
5 expected (cefgh), 1 contributed nothing: g
INTEGRITY sha256 c39d3e5cee0bc0f32eaeee02ae2ff8f5d5db2675066c7a09fe846caeb2b2c0a1
the corpus checksum ledger names this file with the same digest
joined 96,335,187 to merged 96,334,197, minus 990 (minus 0.0010%)
boundary drops 990 · 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:03:12Z 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,926,094 98,419,117 0-34 65e70a91dc9ee0c6eddd731e132f41e08a0cc0d0eed64d379313b0c67b373411 book 133,072 14,271,264 35-35 78277765314762a8e2e79cf6ed3217df91a5f1cc6c77cb032596ffd938a49f2e last_trade_price 42,816 2,432,026 36-36 7805f4cb5821dabcc1abcaf0a2fde1bff79ee8dafe69a37d9945a72fdd61dcc6 market_resolved 1,238 199,263 37-37 6f5a5fd998f058c0c5226baf3ff46a177dacd12d6242fd9c9d323040d0d99c8b new_market 217 28,693 38-38 042899d1e80654ea0ab23e0a5bcd45849eadf5df81b6c264abd6c08e8439220b price_change 87,227,564 831,747,576 39-371 246cf2e7e349e92bc888fd24606a55c73776f7a81435189e0eb4f7e24b9b9d09 tick_size_change 3,196 112,023 372-372 2b8b25b9be365bb6f3fd2f6533a260762022791617704e886f8a4e15a0b00cd2 EVENT MIX count share price_change 87,227,564 90.55% best_bid_ask 8,926,094 9.27% book 133,072 0.14% last_trade_price 42,816 0.04% tick_size_change 3,196 <0.01% market_resolved 1,238 <0.01% new_market 217 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,926,232 8,926,094 138 65,752 PARTIAL book 133,088 133,072 16 23,481 PARTIAL last_trade_price 42,816 42,816 0 2,841 PARTIAL market_resolved 1,238 1,238 0 1,238 PARTIAL new_market 217 217 0 191 PARTIAL price_change 87,228,400 87,227,564 836 115,185 PARTIAL tick_size_change 3,196 3,196 0 799 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,925,621 8,656,059 4ms 8ms 56ms 1.1s 0 transport_latency_assumed best_bid_ask e 8,925,082 11,726 42ms 46ms 107ms 5.6s 0 transport_latency_assumed best_bid_ask f 8,925,210 5,595 46ms 51ms 115ms 4.5s 0 transport_latency_assumed best_bid_ask h 8,925,480 252,714 17ms 22ms 74ms 5.5s 0 transport_latency_assumed book c 101,810 96,353 6ms 3.4min 13.8d 95.8d 0 book_staleness book e 93,998 8,174 44ms 489ms 2.6d 112.7d 0 book_staleness book f 92,685 6,380 48ms 219ms 2.6d 114.3d 0 book_staleness book h 104,892 22,165 21ms 6.3min 13.8d 114.3d 0 book_staleness last_trade_price c 42,699 40,379 5ms 15ms 142ms 746ms 0 transport_latency_assumed last_trade_price e 42,532 181 44ms 95ms 433ms 1.6s 0 transport_latency_assumed last_trade_price f 42,538 160 48ms 96ms 330ms 3.1s 0 transport_latency_assumed last_trade_price h 42,660 2,096 18ms 35ms 182ms 2.1s 0 transport_latency_assumed market_resolved c 1,238 1,033 4ms 23.8s 50.2s 58.5s 0 transport_latency_assumed market_resolved e 1,238 169 43ms 23.0s 49.6s 57.8s 0 transport_latency_assumed market_resolved f 1,238 5 48ms 23.4s 49.7s 57.8s 0 transport_latency_assumed market_resolved h 1,238 31 18ms 24.5s 51.4s 59.1s 0 transport_latency_assumed new_market c 191 55 7.3s 13.9s 23.2s 26.6s 0 transport_latency_assumed new_market e 191 22 5.5s 15.2s 18.4s 18.5s 0 transport_latency_assumed new_market f 191 61 5.8s 13.3s 16.1s 21.0s 0 transport_latency_assumed new_market h 191 79 6.1s 14.2s 23.5s 24.5s 0 transport_latency_assumed price_change c 87,140,852 83,946,240 4ms 10ms 70ms 1.4s 0 transport_latency_assumed price_change e 87,086,666 162,124 42ms 49ms 163ms 6.3s 0 transport_latency_assumed price_change f 87,138,296 127,702 46ms 55ms 161ms 4.8s 0 transport_latency_assumed price_change h 87,128,736 2,991,498 17ms 25ms 98ms 6.2s 0 transport_latency_assumed tick_size_change c 3,196 3,167 4ms 6ms 22ms 51ms 0 transport_latency_assumed tick_size_change e 3,196 4 42ms 45ms 67ms 108ms 0 transport_latency_assumed tick_size_change f 3,196 not meas. 46ms 49ms 66ms 110ms 0 transport_latency_assumed tick_size_change h 3,196 25 17ms 20ms 63ms 100ms 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/05/2026-09-21T05.parquet sha256sum 2026-09-21T05.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.