Hour audit: 2026-08-30T16
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 5 machines expected to be capturing this hour, 1 contributed no rows: b. The hour is still whole on minutes; it simply rests on 4 machines rather than 5.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-08-30T16 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-30T16:00:00.032546366+00:00 · last event 2026-08-30T16:59:59.999999+00:00
VOLUME 112,493,488 rows · 1,204,328,486 bytes (1.12 GiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured c: 112,110,408 · h: 112,058,186 · e: 110,925,125 · a: 107,453,630 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 45,367 (0.04%) · h: 1,170,853 (1.04%) · e: 110,924,219 (98.61%) · a: 353,049 (0.31%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 112,493,488 rows exactly, so those pairs supplied none
5 expected (abceh), 1 contributed nothing: b
INTEGRITY sha256 578cf6391f7d196daf0bc8d27873da7d9b62654d81079cec5d553fe92bd55769
the corpus checksum ledger names this file with the same digest
joined 112,494,418 to merged 112,493,488, minus 930 (minus 0.0008%)
boundary drops 930 · 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-08-30T18:56:15Z as aceh
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,180,297 106,789,107 0-35 b338d3f86ffdd01aa09a5b64dd71af15193b363fdd06186e8f8fc28f23facdc9 book 553,900 57,761,286 36-38 3610aa7d69b1b90bb567364c5572497df9f33481a9c5e3e0458c4e9dde5ee54d last_trade_price 91,994 5,203,566 39-39 d389e094ede464ff54ba8599313af06735e5bb4ce234aad3e2f31557281d7e60 market_resolved 2,287 358,374 40-40 2613d7078cb33ddbfefe29f51c65d92f02d73b20fd77e13e86d4684142354e91 new_market 2,036 199,625 41-41 a9dbca2027f1f745fd9fccf95768c4d529e04ad7c8dd59ee756ea79dcbd883db price_change 102,652,546 1,032,353,247 42-433 70cd68ee32c8fba22213c00ce3ba1d191cbb85774ad2704811d463c37d3b6ee2 tick_size_change 10,428 380,429 434-434 386b61e221a385d288034193e37108edf51609675b6ffe34dd61ad74b402399b EVENT MIX count share price_change 102,652,546 91.25% best_bid_ask 9,180,297 8.16% book 553,900 0.49% last_trade_price 91,994 0.08% tick_size_change 10,428 <0.01% market_resolved 2,287 <0.01% new_market 2,036 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,180,365 9,180,297 68 82,001 PARTIAL book 553,926 553,900 26 173,531 PARTIAL last_trade_price 91,994 91,994 0 5,489 PARTIAL market_resolved 2,287 2,287 0 2,221 PARTIAL new_market 2,036 2,036 0 1,306 PARTIAL price_change 102,653,382 102,652,546 836 133,911 PARTIAL tick_size_change 10,428 10,428 0 2,607 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 8,790,063 120 35ms 55ms 459ms 21.8s 0 transport_latency_assumed best_bid_ask c 9,178,770 804 5ms 10ms 135ms 9.4s 0 transport_latency_assumed best_bid_ask e 9,154,696 9,154,628 45ms 127ms 1.5s 26.0s 0 transport_latency_assumed best_bid_ask h 9,179,097 24,745 13ms 23ms 197ms 43.9s 0 transport_latency_assumed book a 526,086 346,633 37.3s 2.3h 25.0d 92.7d 0 book_staleness book c 193,785 3,650 8ms 31ms 1.1min 74.2d 0 book_staleness book e 192,862 192,860 95ms 5.7s 48.2min 14.0d 0 book_staleness book h 190,961 10,757 20ms 102ms 864ms 10.2s 0 book_staleness last_trade_price a 85,151 3 52ms 1.8s 9.9s 21.9s 0 transport_latency_assumed last_trade_price c 91,914 4 10ms 41ms 240ms 5.0s 0 transport_latency_assumed last_trade_price e 87,363 87,363 73ms 3.3s 12.5s 25.7s 0 transport_latency_assumed last_trade_price h 91,965 4,624 19ms 101ms 542ms 10.7s 0 transport_latency_assumed market_resolved a 2,114 61 37ms 200ms 52.1s 2.4min 0 transport_latency_assumed market_resolved c 2,221 not meas. 5ms 11ms 54.2s 1.0min 0 transport_latency_assumed market_resolved e 2,220 2,220 45ms 350ms 54.2s 1.0min 0 transport_latency_assumed market_resolved h 2,221 6 13ms 50ms 53.1s 59.8s 0 transport_latency_assumed new_market a 1,306 74 240ms 20.9s 29.9s 2.6min 0 transport_latency_assumed new_market c 1,306 223 93ms 18.7s 28.2s 3.7min 0 transport_latency_assumed new_market e 1,306 1,306 240ms 21.3s 29.1s 3.9min 0 transport_latency_assumed new_market h 1,306 433 96ms 15.2s 26.2s 54.2s 0 transport_latency_assumed price_change a 98,038,806 6,158 36ms 94ms 2.0s 21.9s 0 transport_latency_assumed price_change c 102,631,984 40,686 5ms 11ms 168ms 11.8s 0 transport_latency_assumed price_change e 101,476,254 101,475,418 45ms 237ms 5.6s 26.0s 0 transport_latency_assumed price_change h 102,582,208 1,130,284 13ms 27ms 244ms 45.4s 0 transport_latency_assumed tick_size_change a 10,104 not meas. 35ms 46ms 170ms 609ms 0 transport_latency_assumed tick_size_change c 10,428 not meas. 5ms 11ms 74ms 296ms 0 transport_latency_assumed tick_size_change e 10,424 10,424 45ms 126ms 341ms 5.6s 0 transport_latency_assumed tick_size_change h 10,428 4 13ms 27ms 114ms 472ms 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-08-30/16/2026-08-30T16.parquet sha256sum 2026-08-30T16.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.