Hour audit: 2026-10-09T05
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
- the checksum ledger does not name this file. No line in the corpus checksum ledger names this file, so the documented verification step passes over it in silence rather than checking it. The manifest below still carries the digest.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-10-09T05 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-10-09T05:00:00.000056424+00:00 · last event 2026-10-09T05:59:59.999992669+00:00
VOLUME 109,565,411 rows · 1,266,988,042 bytes (1.18 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured i: 109,368,827 · o: 108,901,326 · m: 108,890,369 · n: 108,875,925 · h: 108,722,836 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 1,182,283 (1.08%) · o: 54,521,627 (49.76%) · m: 52,862,144 (48.25%) · n: 72,080 (0.07%) · h: 927,277 (0.85%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 cce44a8624ccf2111ad42df159d9b0333abdae53f7114300e2b3e03b416625af
no line in the corpus checksum ledger names this file
joined 109,582,470 to merged 109,565,411, minus 17,059 (minus 0.0156%)
boundary drops 17,059 · 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-09T23:24:42Z as himno
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
PASS every expected machine contributed
FINDING the checksum ledger does not name 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 11,815,628 146,207,569 0-45 3657dfee29d00658540ddb82d586f3131373ebd826174415333594eeb9242d72 book 722,078 67,482,730 46-48 ab6dcff3f8a4103ee3533afe5bc2765ac6d88815886782a13eab1dd3fa25e962 last_trade_price 42,548 2,498,393 49-49 cf3b74c4e7c7ef0792a36bdc6809a109d4d424cdaae7498904ed00607d83884d market_resolved 921 151,141 50-50 672d021363e0a5ee44823a92d0d3d9df1e1028ee2e1edf33948a3cb547c8525e new_market 940 134,214 51-51 de33400e6d67313ce9e74677c6a6848ab41232484a93ce12c986a14babcb241a price_change 96,980,524 1,049,162,928 52-421 3da47bc207d64b6617bf7d12d6a75fa716071612014a13065d5e17b7c2ca9345 tick_size_change 2,772 101,483 422-422 dbfdf7fe29eb840ded9ad2961bde7257f5963fce49e1481be30bd68b5e244616 EVENT MIX count share price_change 96,980,524 88.51% best_bid_ask 11,815,628 10.78% book 722,078 0.66% last_trade_price 42,548 0.04% tick_size_change 2,772 <0.01% new_market 940 <0.01% market_resolved 921 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,817,622 11,815,628 1,994 163 FULL book 722,370 722,078 292 236,607 FULL last_trade_price 42,559 42,548 11 2 FULL market_resolved 921 921 0 0 FULL new_market 946 940 6 6 FULL price_change 96,995,280 96,980,524 14,756 247 FULL tick_size_change 2,772 2,772 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 11,811,638 84,487 18ms 30ms 169ms 1.1min 0 transport_latency_assumed best_bid_ask i 11,811,815 63,369 21ms 30ms 108ms 4.1s 0 transport_latency_assumed best_bid_ask m 11,814,783 5,778,082 4ms 13ms 84ms 8.9s 0 transport_latency_assumed best_bid_ask n 11,813,691 3,807 44ms 61ms 203ms 19.2s 0 transport_latency_assumed best_bid_ask o 11,814,153 5,885,883 4ms 13ms 84ms 3.6s 0 transport_latency_assumed book h 112,085 24,234 26ms 1.9h 19.9d 124.5d 0 book_staleness book i 641,808 506,517 13.7min 1.1d 47.7d 132.3d 0 book_staleness book m 131,578 78,555 10ms 7.6h 31.8d 132.3d 0 book_staleness book n 122,435 27,094 72ms 4.8h 31.8d 132.3d 0 book_staleness book o 139,110 85,678 13ms 10.0h 31.8d 113.8d 0 book_staleness last_trade_price h 41,970 480 20ms 68ms 370ms 23.5s 0 transport_latency_assumed last_trade_price i 42,303 307 24ms 104ms 491ms 3.8s 0 transport_latency_assumed last_trade_price m 42,446 20,112 6ms 24ms 199ms 3.4s 0 transport_latency_assumed last_trade_price n 42,318 52 49ms 237ms 1.6s 8.0s 0 transport_latency_assumed last_trade_price o 42,328 21,597 6ms 25ms 193ms 3.7s 0 transport_latency_assumed market_resolved h 908 11 32ms 119ms 1.5min 2.4min 0 transport_latency_assumed market_resolved i 908 23 45ms 145ms 1.5min 2.1min 0 transport_latency_assumed market_resolved m 908 433 5ms 20ms 1.4min 2.1min 0 transport_latency_assumed market_resolved n 908 3 100ms 290ms 1.3min 2.1min 0 transport_latency_assumed market_resolved o 908 451 5ms 22ms 1.3min 2.2min 0 transport_latency_assumed new_market h 915 66 53ms 208ms 2.2min 14.1min 0 transport_latency_assumed new_market i 909 181 40ms 99ms 2.1min 19.1min 0 transport_latency_assumed new_market m 912 363 34ms 130ms 2.1min 19.1min 0 transport_latency_assumed new_market n 915 16 91ms 240ms 1.8min 2.5min 0 transport_latency_assumed new_market o 913 314 38ms 115ms 1.9min 19.2min 0 transport_latency_assumed price_change h 96,752,548 817,984 18ms 35ms 228ms 1.1min 0 transport_latency_assumed price_change i 96,868,312 611,860 21ms 37ms 188ms 4.1s 0 transport_latency_assumed price_change m 96,896,970 46,983,192 5ms 15ms 101ms 8.9s 0 transport_latency_assumed price_change n 96,892,886 41,104 44ms 73ms 436ms 20.5s 0 transport_latency_assumed price_change o 96,901,142 48,526,384 5ms 15ms 101ms 3.9s 0 transport_latency_assumed tick_size_change h 2,772 15 18ms 38ms 124ms 895ms 0 transport_latency_assumed tick_size_change i 2,772 26 21ms 47ms 84ms 332ms 0 transport_latency_assumed tick_size_change m 2,772 1,407 5ms 15ms 63ms 137ms 0 transport_latency_assumed tick_size_change n 2,772 4 45ms 96ms 157ms 219ms 0 transport_latency_assumed tick_size_change o 2,772 1,320 5ms 22ms 88ms 216ms 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-09/05/2026-10-09T05.parquet sha256sum 2026-10-09T05.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.