Hour audit: 2026-09-01T18
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 4 machines expected to be capturing this hour, 1 contributed no rows: b. The hour is still whole on minutes; it simply rests on 3 machines rather than 4.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-01T18 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-01T18:00:00.025051186+00:00 · last event 2026-09-01T18:59:59.999974181+00:00
VOLUME 109,144,949 rows · 1,125,180,153 bytes (1.05 GiB) · 7 products, all holding rows
WITNESSES ceh — 3 machines contributed rows
captured h: 108,771,609 · c: 108,764,559 · e: 107,962,628 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 1,031,755 (0.95%) · c: 152,620 (0.14%) · e: 107,960,574 (98.91%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 109,144,949 rows exactly, so those pairs supplied none
4 expected (bceh), 1 contributed nothing: b
INTEGRITY sha256 e8caa2218c6267b69dcee2910e509b7b24b27035bf15bf067499a1673804f920
the corpus checksum ledger names this file with the same digest
joined 109,148,611 to merged 109,144,949, minus 3,662 (minus 0.0034%)
boundary drops 3,662 · 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-01T22:24:17Z as ceh
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,626,718 110,910,835 0-36 a56cd573c4326915fc9e7106f436893ed035c7a98422eacc714cce8c58560c75 book 731,284 63,995,141 37-39 20cada6f300c63eabc3cb1b26bd5197de957dc146302b5e6f8b108e367a43d14 last_trade_price 81,212 4,516,445 40-40 6bca7c2bfb15f68355cac29754f5ad56686752abf68f1cef8148a7d21fccb148 market_resolved 1,154 187,816 41-41 35a0a4844196ed38d0033a7b130d18a22ca9b9a1ed9d14bbcf6ec5fa153e9969 new_market 1,271 143,242 42-42 306a45d84f41e892b397d5cc21e2ea4a6ddff560d9a40d6b1ae088ba313e0880 price_change 98,698,482 944,011,182 43-419 cdceaf88021bba87e68e8c5984e4d26daf59768b58d8651a6ee52eb8364a30ac tick_size_change 4,828 176,576 420-420 367093c0fded51ef37f79368eb0c1a525b97b6ab1f079bbe9223c4d051941379 EVENT MIX count share price_change 98,698,482 90.43% best_bid_ask 9,626,718 8.82% book 731,284 0.67% last_trade_price 81,212 0.07% tick_size_change 4,828 <0.01% new_market 1,271 <0.01% market_resolved 1,154 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,626,784 9,626,718 66 92,670 PARTIAL book 734,212 731,284 2,928 163,204 PARTIAL last_trade_price 81,212 81,212 0 4,114 PARTIAL market_resolved 1,154 1,154 0 1,154 PARTIAL new_market 1,271 1,271 0 938 PARTIAL price_change 98,699,150 98,698,482 668 139,629 PARTIAL tick_size_change 4,828 4,828 0 1,207 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,625,074 831 5ms 9ms 82ms 2.0s 0 transport_latency_assumed best_bid_ask e 9,605,876 9,605,810 42ms 97ms 903ms 27.4s 0 transport_latency_assumed best_bid_ask h 9,624,357 20,077 19ms 29ms 144ms 14.9s 0 transport_latency_assumed book c 378,014 144,792 9.3s 3.3h 24.2d 94.9d 0 book_staleness book e 398,847 397,527 23.0s 3.6h 27.8d 94.9d 0 book_staleness book h 394,159 188,965 13.9s 3.4h 24.2d 94.9d 0 book_staleness last_trade_price c 81,141 12 10ms 42ms 196ms 5.0s 0 transport_latency_assumed last_trade_price e 76,259 76,259 83ms 3.8s 13.6s 27.1s 0 transport_latency_assumed last_trade_price h 81,171 4,941 28ms 233ms 1.4s 5.6s 0 transport_latency_assumed market_resolved c 1,154 not meas. 5ms 15ms 54.6s 59.7s 0 transport_latency_assumed market_resolved e 1,154 1,154 42ms 326ms 54.4s 59.8s 0 transport_latency_assumed market_resolved h 1,154 not meas. 19ms 115ms 53.8s 59.8s 0 transport_latency_assumed new_market c 938 95 54ms 14.1s 33.5s 1.3min 0 transport_latency_assumed new_market e 938 938 189ms 12.9s 27.5s 1.3min 0 transport_latency_assumed new_market h 938 238 106ms 14.6s 28.8s 1.2min 0 transport_latency_assumed price_change c 98,673,410 6,890 5ms 10ms 110ms 2.8s 0 transport_latency_assumed price_change e 97,874,726 97,874,058 42ms 155ms 5.0s 27.7s 0 transport_latency_assumed price_change h 98,665,002 817,534 19ms 35ms 265ms 15.1s 0 transport_latency_assumed tick_size_change c 4,828 not meas. 5ms 9ms 71ms 303ms 0 transport_latency_assumed tick_size_change e 4,828 4,828 42ms 104ms 235ms 4.3s 0 transport_latency_assumed tick_size_change h 4,828 not meas. 19ms 27ms 297ms 3.5s 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-01/18/2026-09-01T18.parquet sha256sum 2026-09-01T18.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.