Hour audit: 2026-09-01T01
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-01T01 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-01T01:00:00.005504327+00:00 · last event 2026-09-01T01:59:59.999992273+00:00
VOLUME 77,127,738 rows · 756,081,870 bytes (721.06 MiB) · 7 products, all holding rows
WITNESSES ceh — 3 machines contributed rows
captured c: 77,111,630 · h: 77,046,455 · e: 76,936,098 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 25,813 (0.03%) · h: 165,841 (0.22%) · e: 76,936,084 (99.75%) (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 77,127,738 rows exactly, so those pairs supplied none
4 expected (bceh), 1 contributed nothing: b
the listing string reads "bche"; the letters above are the machines whose rows are in the file
INTEGRITY sha256 2771fa8ac87d973751a83731e45fe4f8a63cf23edf1a207e19bfa1252c74d4da
the corpus checksum ledger names this file with the same digest
joined 77,127,752 to merged 77,127,738, minus 14 (minus 0.0000%)
boundary drops 14 · 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-02T04:40:07Z 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 8,415,321 95,762,427 0-32 4b605bfc65cb5105b5c5734f9c5e28c9de845d65f7066583e07f7ec29f8ee367 book 131,640 11,473,595 33-33 1922d76f8b6d28ba7b846d3498649a6febfeba9a8d7c433ad23c1173c3cb069e last_trade_price 59,743 3,369,211 34-34 9a2ac606cc86394bb8f13b3fef24ca1dde947481b8303c56d5173c8449442e8f market_resolved 532 87,817 35-35 98a8d5c4846b84dcb1f55cd3faced20bac242c23ebf95c9cb04bd32d5a8d0838 new_market 1,598 159,320 36-36 5703551c13889ee800947596d3120adaf99f3baffa31ac22cc219c10906e13ea price_change 68,513,844 644,162,040 37-298 3daa200e0e672716f7ba85508d2893fb71a718593ec43d55b57326a030873ca7 tick_size_change 5,060 184,563 299-299 e619c2f0dd9b63dc5ffdcdec958de2e034c74efb69f0d1121d1bce14b394f7f1 EVENT MIX count share price_change 68,513,844 88.83% best_bid_ask 8,415,321 10.91% book 131,640 0.17% last_trade_price 59,743 0.08% tick_size_change 5,060 <0.01% new_market 1,598 <0.01% market_resolved 532 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,415,323 8,415,321 2 100,400 PARTIAL book 131,640 131,640 0 7,787 PARTIAL last_trade_price 59,743 59,743 0 4,046 PARTIAL market_resolved 532 532 0 532 PARTIAL new_market 1,598 1,598 0 1,039 PARTIAL price_change 68,513,856 68,513,844 12 149,954 PARTIAL tick_size_change 5,060 5,060 0 1,265 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,415,218 352 4ms 6ms 68ms 2.7s 0 transport_latency_assumed best_bid_ask e 8,409,152 8,409,150 42ms 78ms 784ms 22.6s 0 transport_latency_assumed best_bid_ask h 8,414,813 5,819 12ms 16ms 124ms 46.9s 0 transport_latency_assumed book c 125,402 1,495 6ms 24ms 6.9s 75.6d 0 book_staleness book e 123,590 123,590 70ms 5.7s 8.5min 2.4d 0 book_staleness book h 127,287 6,555 16ms 162ms 7.5min 75.6d 0 book_staleness last_trade_price c 59,717 4 9ms 37ms 164ms 5.0s 0 transport_latency_assumed last_trade_price e 58,306 58,306 70ms 4.5s 12.4s 22.7s 0 transport_latency_assumed last_trade_price h 59,699 1,433 17ms 104ms 628ms 32.5s 0 transport_latency_assumed market_resolved c 532 not meas. 4ms 6ms 25ms 41ms 0 transport_latency_assumed market_resolved e 532 532 43ms 173ms 516ms 8.5s 0 transport_latency_assumed market_resolved h 532 not meas. 12ms 30ms 92ms 125ms 0 transport_latency_assumed new_market c 1,039 177 81ms 41.9s 45.7s 1.1min 0 transport_latency_assumed new_market e 1,039 1,039 234ms 38.6s 47.9s 1.3min 0 transport_latency_assumed new_market h 1,039 382 151ms 39.4s 51.2s 1.0min 0 transport_latency_assumed price_change c 68,504,662 23,785 4ms 7ms 95ms 3.3s 0 transport_latency_assumed price_change e 68,338,419 68,338,407 43ms 116ms 4.2s 22.7s 0 transport_latency_assumed price_change h 68,438,025 151,652 12ms 18ms 193ms 48.0s 0 transport_latency_assumed tick_size_change c 5,060 not meas. 4ms 6ms 21ms 223ms 0 transport_latency_assumed tick_size_change e 5,060 5,060 43ms 110ms 342ms 889ms 0 transport_latency_assumed tick_size_change h 5,060 not meas. 12ms 15ms 98ms 263ms 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/01/2026-09-01T01.parquet sha256sum 2026-09-01T01.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.