Hour audit: 2026-09-04T01
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.
No findings
Every check that could be evaluated for this hour passed. That is not the same as the hour being perfect: it means the records this archive keeps about it agree with each other and with the corpus ledger.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-04T01 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-04T01:00:00.002923709+00:00 · last event 2026-09-04T01:59:59.999965335+00:00
VOLUME 104,087,325 rows · 998,129,463 bytes (951.89 MiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured c: 104,047,436 · h: 77,064,125 · e: 64,805,094 · b: 61,676,078 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 20,237,086 (19.44%) · h: 19,037,217 (18.29%) · e: 64,804,311 (62.26%) · b: 8,711 (0.01%) (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 104,087,325 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 2a14c33079a02541a090e966b82181b7d6f71456ac695118034e341489724cc5
the corpus checksum ledger names this file with the same digest
joined 104,088,516 to merged 104,087,325, minus 1,191 (minus 0.0011%)
boundary drops 1,191 · 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-04T02:50:31Z as bceh
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 8/8 pass
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
PASS every expected machine contributed
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,323,716 105,527,386 0-35 d0cd370de8b275e253fe226b8a66f14dfddfac5322ba015d84d8e98d195c5661 book 154,477 15,331,710 36-36 dbe78565c526eb7d5ebf658cad859ac397ca75658af0f7ef3eac7086acd4eec9 last_trade_price 61,333 3,403,478 37-37 f65f8a9a04cc2596c4e41bf410d7e96c91b01cc0f197dc1ca464ce7b3adf5ba1 market_resolved 1,411 220,632 38-38 67460ca8746cfb175072528f9afc90a67b047a29c0e9878a93c5924ef9b25dd4 new_market 1,266 144,069 39-39 aaec3bc709d11d2a7857d716ceb4fd9b19fa73dc5399cebb890cf08b1b2ce374 price_change 94,542,400 872,215,574 40-400 82d6804eeb38439f25a9fe6a0821116b06870127b0a0b4e69c62782da6c92373 tick_size_change 2,722 100,276 401-401 bd5a38e93b2a3d1c3cec038c7f9566e795e9733c9e26a6f0d36a792d62754677 EVENT MIX count share price_change 94,542,400 90.83% best_bid_ask 9,323,716 8.96% book 154,477 0.15% last_trade_price 61,333 0.06% tick_size_change 2,722 <0.01% market_resolved 1,411 <0.01% new_market 1,266 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,323,844 9,323,716 128 236 FULL book 154,481 154,477 4 10,095 FULL last_trade_price 61,334 61,333 1 0 FULL market_resolved 1,411 1,411 0 1 FULL new_market 1,266 1,266 0 0 FULL price_change 94,543,458 94,542,400 1,058 113,340 FULL tick_size_change 2,722 2,722 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 9,314,775 72 53ms 85ms 597ms 30.9s 0 transport_latency_assumed best_bid_ask c 9,323,348 1,259 5ms 10ms 93ms 2.0s 0 transport_latency_assumed best_bid_ask e 9,309,407 9,309,303 42ms 90ms 1.6s 19.9s 0 transport_latency_assumed best_bid_ask h 9,321,761 13,082 18ms 26ms 162ms 19.2s 0 transport_latency_assumed book b 131,816 7,998 143ms 7.7s 5.7h 78.6d 0 book_staleness book c 134,235 7,091 8ms 66ms 3.4h 78.6d 0 book_staleness book e 131,302 131,300 80ms 7.5s 1.3h 7.0d 0 book_staleness book h 133,206 8,088 26ms 376ms 2.9h 97.1d 0 book_staleness last_trade_price b 59,525 7 113ms 4.4s 14.6s 30.8s 0 transport_latency_assumed last_trade_price c 61,287 6 11ms 48ms 281ms 5.0s 0 transport_latency_assumed last_trade_price e 60,484 60,483 75ms 5.6s 15.7s 19.8s 0 transport_latency_assumed last_trade_price h 61,204 837 28ms 256ms 977ms 5.0s 0 transport_latency_assumed market_resolved b 1,363 not meas. 55ms 412ms 57.9s 1.0min 0 transport_latency_assumed market_resolved c 1,363 47 6ms 15ms 460ms 1.0min 0 transport_latency_assumed market_resolved e 1,362 1,362 43ms 361ms 57.1s 1.0min 0 transport_latency_assumed market_resolved h 1,363 2 20ms 140ms 56.6s 1.0min 0 transport_latency_assumed new_market b 949 58 261ms 14.2s 24.7s 1.1min 0 transport_latency_assumed new_market c 949 81 62ms 12.8s 26.8s 1.2min 0 transport_latency_assumed new_market e 949 949 120ms 630ms 28.0s 1.2min 0 transport_latency_assumed new_market h 949 178 122ms 12.1s 26.8s 1.1min 0 transport_latency_assumed price_change b 52,164,928 576 54ms 184ms 7.2s 30.9s 0 transport_latency_assumed price_change c 94,523,532 20,228,602 6ms 10ms 109ms 3.2s 0 transport_latency_assumed price_change e 55,298,868 55,298,192 43ms 191ms 9.5s 20.0s 0 transport_latency_assumed price_change h 67,542,920 19,015,030 19ms 33ms 322ms 20.3s 0 transport_latency_assumed tick_size_change b 2,722 not meas. 52ms 64ms 321ms 902ms 0 transport_latency_assumed tick_size_change c 2,722 not meas. 5ms 8ms 24ms 395ms 0 transport_latency_assumed tick_size_change e 2,722 2,722 42ms 55ms 320ms 3.4s 0 transport_latency_assumed tick_size_change h 2,722 not meas. 18ms 22ms 70ms 720ms 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-04/01/2026-09-04T01.parquet sha256sum 2026-09-04T01.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.