Hour audit: 2026-10-01T06
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-01T06 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-01T06:00:00.000011399+00:00 · last event 2026-10-01T06:59:59.999958813+00:00
VOLUME 106,212,754 rows · 1,138,923,554 bytes (1.06 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured k: 105,743,717 · i: 102,024,819 · h: 99,528,066 · m: 96,850,857 · g: 92,928,129 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 19,443,532 (18.31%) · i: 1,229,260 (1.16%) · h: 5,925,799 (5.58%) · m: 79,589,977 (74.93%) · g: 24,186 (0.02%) (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 106,212,754 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 cbb807cf1d184b694a06bdcf0a88b2b88af459ec33532c66712ef38ae8e3eed2
the corpus checksum ledger names this file with the same digest
joined 106,219,022 to merged 106,212,754, minus 6,268 (minus 0.0059%)
boundary drops 6,268 · 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-01T09:05:47Z 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 11,179,474 130,331,362 0-42 09bc69919cb9ed82123bc318fb9e8a490265f53a7a7b7059251742db87fc17cb book 552,576 56,250,192 43-45 1ec693c0d0079161664dd712d2856847a7698434d865a8f7aead519ad7e9ec26 last_trade_price 50,622 2,928,970 46-46 a3e8e7270f6e844320b8e076638d0d5e0f1d6eabf477ecef0a3a009209dcd311 market_resolved 993 156,946 47-47 6b6454403f5e37967be969ee8c0638b607c69ca36a2ec252239c5bae3a25e408 new_market 537 55,329 48-48 c1487217c21d0fc0798fac12f02a31e6cc0de1be5fa90a265a138a2399b29a37 price_change 94,426,604 947,916,183 49-409 0af1181707354afcf580c92ee148bb780f9f4520a09540c92bd9412de97d5e87 tick_size_change 1,948 70,931 410-410 6d9f56b3016ab07aa54db32d29688ff8d07c60e7c944875415d9de8c135fbbdc EVENT MIX count share price_change 94,426,604 88.90% best_bid_ask 11,179,474 10.53% book 552,576 0.52% last_trade_price 50,622 0.05% tick_size_change 1,948 <0.01% market_resolved 993 <0.01% new_market 537 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,179,688 11,179,474 214 80 FULL book 557,054 552,576 4,478 206,204 FULL last_trade_price 50,622 50,622 0 1 FULL market_resolved 993 993 0 0 FULL new_market 537 537 0 0 FULL price_change 94,428,180 94,426,604 1,576 45,660 FULL tick_size_change 1,948 1,948 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 11,177,756 759 78ms 100ms 249ms 15.6s 0 transport_latency_assumed best_bid_ask h 11,178,932 435,690 18ms 29ms 134ms 43.8s 0 transport_latency_assumed best_bid_ask i 11,152,874 49,064 30ms 60ms 138ms 8.4s 0 transport_latency_assumed best_bid_ask k 11,178,557 1,455,847 15ms 32ms 134ms 9.5s 0 transport_latency_assumed best_bid_ask m 11,179,034 9,238,114 5ms 24ms 106ms 1.0s 0 transport_latency_assumed book g 114,378 9,080 84ms 29.7s 4.1d 105.8d 0 book_staleness book h 106,801 7,104 21ms 71ms 18.9h 105.9d 0 book_staleness book i 541,642 429,673 16.5min 3.2d 39.7d 124.4d 0 book_staleness book k 106,586 13,113 17ms 52ms 20.3h 105.8d 0 book_staleness book m 112,548 93,606 6ms 314ms 4.1d 124.3d 0 book_staleness last_trade_price g 50,389 8 82ms 207ms 4.2s 15.6s 0 transport_latency_assumed last_trade_price h 50,599 2,225 19ms 37ms 355ms 5.2s 0 transport_latency_assumed last_trade_price i 50,519 172 34ms 82ms 343ms 3.4s 0 transport_latency_assumed last_trade_price k 50,598 5,526 16ms 35ms 154ms 1.7s 0 transport_latency_assumed last_trade_price m 50,601 42,691 6ms 27ms 202ms 922ms 0 transport_latency_assumed market_resolved g 972 54 84ms 12.8s 45.0s 57.3s 0 transport_latency_assumed market_resolved h 972 17 20ms 21.6s 52.7s 53.8s 0 transport_latency_assumed market_resolved i 972 8 38ms 12.1s 43.2s 43.7s 0 transport_latency_assumed market_resolved k 972 90 16ms 130ms 54.3s 58.0s 0 transport_latency_assumed market_resolved m 972 824 5ms 12.2s 43.1s 43.6s 0 transport_latency_assumed new_market g 356 41 130ms 10.5s 44.3s 1.5min 0 transport_latency_assumed new_market h 356 131 157ms 13.8s 17.9s 1.4min 0 transport_latency_assumed new_market i 356 55 90ms 432ms 40.1s 1.7min 0 transport_latency_assumed new_market k 356 90 64ms 361ms 16.0s 1.6min 0 transport_latency_assumed new_market m 356 220 45ms 10.2s 16.0s 1.4min 0 transport_latency_assumed price_change g 81,582,330 14,244 79ms 113ms 651ms 15.6s 0 transport_latency_assumed price_change h 88,188,458 5,480,534 18ms 32ms 195ms 47.4s 0 transport_latency_assumed price_change i 90,276,508 750,288 31ms 65ms 199ms 10.4s 0 transport_latency_assumed price_change k 94,404,700 17,968,624 15ms 34ms 144ms 9.7s 0 transport_latency_assumed price_change m 85,505,398 70,212,914 5ms 25ms 129ms 1.4s 0 transport_latency_assumed tick_size_change g 1,948 not meas. 79ms 101ms 171ms 389ms 0 transport_latency_assumed tick_size_change h 1,948 98 18ms 29ms 53ms 133ms 0 transport_latency_assumed tick_size_change i 1,948 not meas. 32ms 67ms 106ms 157ms 0 transport_latency_assumed tick_size_change k 1,948 242 15ms 30ms 68ms 116ms 0 transport_latency_assumed tick_size_change m 1,948 1,608 4ms 23ms 56ms 122ms 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/06/2026-10-01T06.parquet sha256sum 2026-10-01T06.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.