Hour audit: 2026-09-02T00
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, 2 contributed no rows: b, c. The hour is still whole on minutes; it simply rests on 2 machines rather than 4.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-02T00 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-02T00:00:00.009470251+00:00 · last event 2026-09-02T00:59:59.999992835+00:00
VOLUME 79,077,228 rows · 796,302,052 bytes (759.41 MiB) · 7 products, all holding rows
WITNESSES eh — 2 machines contributed rows
captured h: 79,044,385 · e: 76,440,699 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 2,637,183 (3.33%) · e: 76,440,045 (96.67%) (rows of the merged file that came from it; these partition it)
4 expected (bceh), 2 contributed nothing: b, c
INTEGRITY sha256 9fdbd3c8136277883b14381830e9ada2a1f97ab9441e853b5b96271d0612df49
the corpus checksum ledger names this file with the same digest
joined 79,077,886 to merged 79,077,228, minus 658 (minus 0.0008%)
boundary drops 658 · 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-02T05:25:43Z as eh
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,042,102 90,153,167 0-30 8755d2b2c1e7e08f441e6df1ec6c2c805085d59b0d15d48aa37bdc29c3c2fc3b book 443,393 43,692,006 31-32 580a4051a75c47560bc6cef0d3b05fec03f92925567892d9e2070dd058fc44c9 last_trade_price 60,143 3,329,625 33-33 158c1d15631f1857e61634701e54b3103f0f8168910d681266dae818e9902528 market_resolved 704 114,696 34-34 d13285764926cf734119c2beefab7ffb0e63a05ae9bca2f33a8e908fa8c07b25 new_market 1,218 138,320 35-35 93a2b9e179fd2b777f507fede292766d452c25c418092ae64c2844e19e1bb847 price_change 70,527,620 657,896,446 36-305 d4ff1abf894d72b7459c262cb7414ec3c25281f08c4135be3bac9847c3c19bee tick_size_change 2,048 75,410 306-306 b3440783fbfe6f306aa4e864bbbe07e69b6fb0aaff5a20879494c24188de358a EVENT MIX count share price_change 70,527,620 89.19% best_bid_ask 8,042,102 10.17% book 443,393 0.56% last_trade_price 60,143 0.08% tick_size_change 2,048 <0.01% new_market 1,218 <0.01% market_resolved 704 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,042,154 8,042,102 52 83,317 PARTIAL book 443,399 443,393 6 140,906 PARTIAL last_trade_price 60,143 60,143 0 3,267 PARTIAL market_resolved 704 704 0 687 PARTIAL new_market 1,218 1,218 0 924 PARTIAL price_change 70,528,220 70,527,620 600 135,164 PARTIAL tick_size_change 2,048 2,048 0 512 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask e 7,818,472 7,818,420 42ms 100ms 1.4s 22.6s 0 transport_latency_assumed best_bid_ask h 8,039,793 223,682 17ms 25ms 196ms 7.5s 0 transport_latency_assumed book e 128,037 128,035 124ms 9.6s 1.0h 12.3d 0 book_staleness book h 434,776 315,358 1.5min 56.3min 27.0d 95.1d 0 book_staleness last_trade_price e 56,894 56,894 87ms 5.2s 14.8s 22.6s 0 transport_latency_assumed last_trade_price h 60,039 3,249 29ms 427ms 1.5s 5.0s 0 transport_latency_assumed market_resolved e 682 682 42ms 761ms 1.1min 2.5min 0 transport_latency_assumed market_resolved h 687 22 17ms 190ms 58.9s 1.0min 0 transport_latency_assumed new_market e 924 924 196ms 33.7s 1.1min 1.3min 0 transport_latency_assumed new_market h 924 294 102ms 17.7s 1.2min 1.2min 0 transport_latency_assumed price_change e 68,433,686 68,433,086 42ms 163ms 6.4s 23.0s 0 transport_latency_assumed price_change h 70,506,118 2,094,534 17ms 34ms 409ms 7.7s 0 transport_latency_assumed tick_size_change e 2,004 2,004 42ms 117ms 1.5s 9.4s 0 transport_latency_assumed tick_size_change h 2,048 44 17ms 23ms 233ms 1.0s 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-02/00/2026-09-02T00.parquet sha256sum 2026-09-02T00.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.