Hour audit: 2026-10-05T00
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-05T00 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-05T00:00:00.000276160+00:00 · last event 2026-10-05T00:59:59.999959770+00:00
VOLUME 116,311,690 rows · 1,295,909,168 bytes (1.21 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 116,186,654 · m: 116,137,654 · h: 116,115,442 · n: 116,080,508 · i: 115,070,721 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 58,774,932 (50.53%) · m: 56,064,755 (48.20%) · h: 1,006,337 (0.87%) · n: 75,929 (0.07%) · i: 389,737 (0.34%) (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 116,311,690 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 086699b0293dcb8cea6f300ebcef5796715504a1d098541830726f5ceb79b053
the corpus checksum ledger names this file with the same digest
joined 116,313,029 to merged 116,311,690, minus 1,339 (minus 0.0012%)
boundary drops 1,339 · 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-05T02:02:28Z 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 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 10,386,895 128,899,169 0-39 b8c03d283bdc0731e970e2a581fd7f84ddf89584398c74ac82607648cb629dd2 book 209,868 20,561,274 40-40 b70f7cb6a42074f2ca918d9284f1fde33d358b35f580c91f1066be9f9f115c10 last_trade_price 69,517 3,872,247 41-41 e3483a7a7df3111d261093a94eab85e61bde87ac6509742e9ba268f9dbf44367 market_resolved 2,787 438,083 42-42 5cf62a1783358436daa2cca23eed91df8412db86b8bb224f0fe29ed1fa5ad297 new_market 1,073 98,918 43-43 9a4b88a3116824d51e94c542711b3162263997632bd62ade1ae61eb313c15650 price_change 105,637,066 1,140,549,436 44-446 4893144912e4b5caddec531b4558f75ebf392f6f97ce2a92ff4b020e47b84e78 tick_size_change 4,484 166,113 447-447 dc979a998027548af1b8d1f5e4fcd1e9f06aedbb7d76bf34f3a6ed98fa9a7ec5 EVENT MIX count share price_change 105,637,066 90.82% best_bid_ask 10,386,895 8.93% book 209,868 0.18% last_trade_price 69,517 0.06% tick_size_change 4,484 <0.01% market_resolved 2,787 <0.01% new_market 1,073 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,387,012 10,386,895 117 99 FULL book 209,948 209,868 80 25,546 FULL last_trade_price 69,517 69,517 0 1 FULL market_resolved 2,787 2,787 0 0 FULL new_market 1,073 1,073 0 0 FULL price_change 105,638,208 105,637,066 1,142 1,396 FULL tick_size_change 4,484 4,484 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,385,238 79,005 18ms 29ms 159ms 53.3s 0 transport_latency_assumed best_bid_ask i 10,344,556 32,173 22ms 34ms 203ms 18.7s 0 transport_latency_assumed best_bid_ask m 10,385,782 5,000,225 5ms 15ms 81ms 7.0s 0 transport_latency_assumed best_bid_ask n 10,383,581 3,216 48ms 70ms 223ms 10.2s 0 transport_latency_assumed best_bid_ask o 10,386,219 5,272,276 5ms 14ms 83ms 7.8s 0 transport_latency_assumed book h 145,252 6,644 21ms 96ms 2.6h 109.5d 0 book_staleness book i 148,447 15,862 26ms 1.1s 35.4min 109.6d 0 book_staleness book m 150,009 82,036 7ms 70ms 15.2h 109.6d 0 book_staleness book n 167,825 28,616 61ms 16.7min 15.6d 109.6d 0 book_staleness book o 151,972 76,710 7ms 115ms 21.3h 126.5d 0 book_staleness last_trade_price h 69,361 848 19ms 54ms 410ms 15.7s 0 transport_latency_assumed last_trade_price i 66,082 230 24ms 181ms 3.1s 4.1s 0 transport_latency_assumed last_trade_price m 69,353 35,404 6ms 21ms 154ms 1.5s 0 transport_latency_assumed last_trade_price n 68,860 49 53ms 1.0s 4.4s 10.2s 0 transport_latency_assumed last_trade_price o 69,405 32,986 6ms 25ms 165ms 1.4s 0 transport_latency_assumed market_resolved h 2,715 16 20ms 16.1s 46.9s 51.5s 0 transport_latency_assumed market_resolved i 2,715 310 23ms 14.0s 48.7s 1.1min 0 transport_latency_assumed market_resolved m 2,715 1,215 6ms 14.3s 48.8s 1.1min 0 transport_latency_assumed market_resolved n 2,715 56 50ms 264ms 51.8s 1.0min 0 transport_latency_assumed market_resolved o 2,715 1,190 6ms 21.4s 52.4s 56.8s 0 transport_latency_assumed new_market h 629 146 157ms 32.0s 40.5s 1.6min 0 transport_latency_assumed new_market i 629 158 139ms 27.6s 52.7s 1.7min 0 transport_latency_assumed new_market m 629 307 78ms 32.0s 39.7s 1.6min 0 transport_latency_assumed new_market n 629 58 217ms 29.6s 1.2min 1.8min 0 transport_latency_assumed new_market o 629 404 56ms 31.2s 44.6s 1.5min 0 transport_latency_assumed price_change h 105,507,763 919,670 18ms 33ms 221ms 54.2s 0 transport_latency_assumed price_change i 104,503,808 341,004 22ms 40ms 477ms 19.3s 0 transport_latency_assumed price_change m 105,524,682 50,943,268 5ms 17ms 92ms 7.1s 0 transport_latency_assumed price_change n 105,452,414 43,934 49ms 81ms 761ms 14.4s 0 transport_latency_assumed price_change o 105,571,230 53,389,190 5ms 16ms 93ms 8.9s 0 transport_latency_assumed tick_size_change h 4,484 8 18ms 23ms 48ms 194ms 0 transport_latency_assumed tick_size_change i 4,484 not meas. 22ms 29ms 63ms 1.2s 0 transport_latency_assumed tick_size_change m 4,484 2,300 5ms 11ms 36ms 330ms 0 transport_latency_assumed tick_size_change n 4,484 not meas. 48ms 60ms 120ms 429ms 0 transport_latency_assumed tick_size_change o 4,484 2,176 5ms 11ms 29ms 72ms 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-05/00/2026-10-05T00.parquet sha256sum 2026-10-05T00.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.