Hour audit: 2026-09-01T17
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-01T17 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-01T17:00:00.034574816+00:00 · last event 2026-09-01T17:59:59.999991147+00:00
VOLUME 106,016,569 rows · 1,079,691,021 bytes (1.01 GiB) · 7 products, all holding rows
WITNESSES ceh — 3 machines contributed rows
captured c: 105,724,168 · h: 105,683,801 · e: 105,031,721 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 145,851 (0.14%) · h: 840,234 (0.79%) · e: 105,030,484 (99.07%) (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 106,016,569 rows exactly, so those pairs supplied none
4 expected (bceh), 1 contributed nothing: b
INTEGRITY sha256 19ab9d2297abc55c4e743a71d2a6e0643a77dadb07cd9d4f1d983e04b7c7d5c0
the corpus checksum ledger names this file with the same digest
joined 106,017,806 to merged 106,016,569, minus 1,237 (minus 0.0012%)
boundary drops 1,237 · 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:06:44Z 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,135,340 102,142,490 0-34 b059c37de199db062d55fccc273d8a9ed77d6d2343419b3fe4776b6f73f6f347 book 629,703 57,608,418 35-37 442f7a904065a19edf72c9e81c3793e3e66d6babd937169109409e07ffb83be3 last_trade_price 76,538 4,242,102 38-38 a4c1d4454e097d8a474c294127211b3f390ef1b2e509c3eb7936289dd1075787 market_resolved 920 151,908 39-39 08c80dbb4b37e866de216a99cbcd34a8d4aee2780541e4055f33740897988e44 new_market 1,986 220,678 40-40 3e5e1b2110cd316459f60c55a1c7e037a6023c36cf3f6bd5461dfdd1bebd9d73 price_change 96,168,838 914,003,099 41-407 adb16a539e79aa56a9b4419fee4cb2e99f15ee6b3f91cd7d91c5260c3c1b9ed3 tick_size_change 3,244 118,343 408-408 bbd4e85d21191c7d6bff7c9aea9ee99ab0a93dd356dcb6d848ea9f3344bb9f28 EVENT MIX count share price_change 96,168,838 90.71% best_bid_ask 9,135,340 8.62% book 629,703 0.59% last_trade_price 76,538 0.07% tick_size_change 3,244 <0.01% new_market 1,986 <0.01% market_resolved 920 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,135,434 9,135,340 94 70,219 PARTIAL book 629,709 629,703 6 155,338 PARTIAL last_trade_price 76,539 76,538 1 4,026 PARTIAL market_resolved 920 920 0 920 PARTIAL new_market 1,986 1,986 0 1,479 PARTIAL price_change 96,169,974 96,168,838 1,136 127,030 PARTIAL tick_size_change 3,244 3,244 0 811 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,134,004 888 2ms 7ms 132ms 2.8s 0 transport_latency_assumed best_bid_ask e 9,101,118 9,101,024 42ms 156ms 1.4s 30.9s 0 transport_latency_assumed best_bid_ask h 9,132,022 33,428 19ms 32ms 274ms 15.3s 0 transport_latency_assumed book c 364,837 134,826 12.2s 3.0h 24.2d 94.8d 0 book_staleness book e 337,234 337,228 12.5s 2.9h 30.2d 94.8d 0 book_staleness book h 349,514 157,649 7.5s 3.0h 24.2d 94.8d 0 book_staleness last_trade_price c 76,490 45 8ms 43ms 234ms 4.9s 0 transport_latency_assumed last_trade_price e 72,248 72,247 88ms 3.9s 15.9s 30.9s 0 transport_latency_assumed last_trade_price h 76,318 4,246 27ms 235ms 1.0s 5.3s 0 transport_latency_assumed market_resolved c 920 not meas. 2ms 7ms 237ms 38.8s 0 transport_latency_assumed market_resolved e 920 920 42ms 333ms 1.3s 43.1s 0 transport_latency_assumed market_resolved h 920 not meas. 19ms 109ms 400ms 39.4s 0 transport_latency_assumed new_market c 1,479 128 70ms 13.7s 1.0min 14.9min 0 transport_latency_assumed new_market e 1,479 1,479 245ms 18.5s 1.1min 1.2min 0 transport_latency_assumed new_market h 1,479 379 122ms 11.9s 58.7s 2.1min 0 transport_latency_assumed price_change c 96,143,194 9,964 3ms 7ms 142ms 3.3s 0 transport_latency_assumed price_change e 95,515,478 95,514,342 42ms 185ms 4.8s 31.0s 0 transport_latency_assumed price_change h 96,120,304 644,532 19ms 37ms 324ms 20.4s 0 transport_latency_assumed tick_size_change c 3,244 not meas. 3ms 7ms 165ms 506ms 0 transport_latency_assumed tick_size_change e 3,244 3,244 42ms 217ms 3.8s 11.5s 0 transport_latency_assumed tick_size_change h 3,244 not meas. 19ms 29ms 260ms 947ms 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/17/2026-09-01T17.parquet sha256sum 2026-09-01T17.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.