Hour audit: 2026-10-01T02
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-10-01T02 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-01T02:00:00.000008378+00:00 · last event 2026-10-01T02:59:59.999962390+00:00
VOLUME 100,596,364 rows · 1,041,752,081 bytes (993.49 MiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured h: 92,223,426 · m: 91,175,425 · i: 89,697,248 · g: 87,137,316 · k: 86,429,721 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 5,827,148 (5.79%) · m: 71,913,872 (71.49%) · i: 1,831,788 (1.82%) · g: 96,235 (0.10%) · k: 20,927,321 (20.80%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 100,596,364 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 68f3a1a9f784b9a0924163f2489cfec4784ab47b6c3828906d839edd62f56928
the corpus checksum ledger names this file with the same digest
joined 100,598,493 to merged 100,596,364, minus 2,129 (minus 0.0021%)
boundary drops 2,129 · 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-10-01T05:04:52Z as ghikm
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 status feed unobserved for this hour. Our incident register was last checked against the venue's feed at 2026-09-23T20:35Z, before this hour ended, so nothing has looked yet. This is a could-not-look and never an all-clear.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,710,502 112,573,562 0-37 a23629287cfc72aac3adaa77502afe366d6d0590a45270f2bde352369d91eb7f book 149,216 16,605,869 38-38 5e194f64f54bf2ccf33ea3c9cbbde1ed2e7bea8789b2440b340b97dee4aacd89 last_trade_price 43,944 2,517,516 39-39 2caa696dc792de8a535f8a625bc82b63b2f64f3afd768ede06a2a090111cda79 market_resolved 421 68,904 40-40 caec7a29d3d0e20a9a86499c339e37cd424c3fc6b05f356fc5a4a1dde803a34c new_market 1,391 163,741 41-41 cf661dee2dba12c941e1576c2ef377999f1d1e5fd7c4555d09a02b6b85db7306 price_change 90,688,254 908,577,303 42-387 c8da1c3a84de48e57ba4c729f81b457d9790aadd298704eb243d52efa3dcacbd tick_size_change 2,636 96,910 388-388 d6d39fca300533a52764b70459a9f67ab32e464fb8373273f59c676e4702c5c5 EVENT MIX count share price_change 90,688,254 90.15% best_bid_ask 9,710,502 9.65% book 149,216 0.15% last_trade_price 43,944 0.04% tick_size_change 2,636 <0.01% new_market 1,391 <0.01% market_resolved 421 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,710,650 9,710,502 148 88 FULL book 149,218 149,216 2 28,012 FULL last_trade_price 43,945 43,944 1 0 FULL market_resolved 421 421 0 0 FULL new_market 1,391 1,391 0 0 FULL price_change 90,690,232 90,688,254 1,978 63,686 FULL tick_size_change 2,636 2,636 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,708,958 2,663 79ms 98ms 350ms 23.8s 0 transport_latency_assumed best_bid_ask h 9,708,840 214,479 17ms 26ms 283ms 1.5min 0 transport_latency_assumed best_bid_ask i 9,709,862 58,693 21ms 53ms 148ms 10.0s 0 transport_latency_assumed best_bid_ask k 9,709,730 1,473,384 12ms 22ms 170ms 1.0min 0 transport_latency_assumed best_bid_ask m 9,710,214 7,961,283 5ms 20ms 92ms 2.5s 0 transport_latency_assumed book g 93,596 4,378 84ms 227ms 15.3h 105.5d 0 book_staleness book h 109,499 23,664 22ms 1.4h 17.0d 124.2d 0 book_staleness book i 91,314 3,082 22ms 89ms 2.8min 105.5d 0 book_staleness book k 104,166 35,418 16ms 4.2min 9.1d 105.7d 0 book_staleness book m 111,518 82,674 13ms 2.4h 11.5d 105.7d 0 book_staleness last_trade_price g 43,825 34 83ms 150ms 1.7s 23.9s 0 transport_latency_assumed last_trade_price h 43,900 2,234 19ms 43ms 641ms 53.5s 0 transport_latency_assumed last_trade_price i 43,927 624 22ms 66ms 486ms 2.5s 0 transport_latency_assumed last_trade_price k 43,932 11,654 14ms 35ms 267ms 8.3s 0 transport_latency_assumed last_trade_price m 43,930 29,398 10ms 37ms 146ms 1.3s 0 transport_latency_assumed market_resolved g 421 not meas. 87ms 41.4s 52.6s 54.7s 0 transport_latency_assumed market_resolved h 421 4 20ms 31.8s 40.8s 42.7s 0 transport_latency_assumed market_resolved i 421 2 41ms 23.7s 33.3s 34.6s 0 transport_latency_assumed market_resolved k 421 43 15ms 28.1s 39.1s 40.7s 0 transport_latency_assumed market_resolved m 421 372 6ms 22.2s 32.1s 33.1s 0 transport_latency_assumed new_market g 1,092 320 16.4s 26.0s 1.0min 1.6min 0 transport_latency_assumed new_market h 1,092 321 15.5s 26.4s 1.0min 1.7min 0 transport_latency_assumed new_market i 1,092 161 16.5s 24.6s 58.5s 1.7min 0 transport_latency_assumed new_market k 1,092 164 16.3s 26.4s 59.7s 1.3min 0 transport_latency_assumed new_market m 1,092 425 15.8s 26.0s 57.8s 1.7min 0 transport_latency_assumed price_change g 77,286,788 88,840 80ms 104ms 464ms 24.1s 0 transport_latency_assumed price_change h 82,357,038 5,586,342 18ms 29ms 343ms 1.5min 0 transport_latency_assumed price_change i 79,847,996 1,769,208 22ms 56ms 205ms 10.1s 0 transport_latency_assumed price_change k 76,567,744 19,406,180 13ms 25ms 188ms 1.1min 0 transport_latency_assumed price_change m 81,305,614 63,837,684 6ms 25ms 110ms 9.3s 0 transport_latency_assumed tick_size_change g 2,636 not meas. 79ms 97ms 165ms 299ms 0 transport_latency_assumed tick_size_change h 2,636 104 18ms 27ms 72ms 112ms 0 transport_latency_assumed tick_size_change i 2,636 18 21ms 54ms 112ms 130ms 0 transport_latency_assumed tick_size_change k 2,636 478 12ms 20ms 89ms 196ms 0 transport_latency_assumed tick_size_change m 2,636 2,036 6ms 24ms 111ms 133ms 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-10-01/02/2026-10-01T02.parquet sha256sum 2026-10-01T02.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.