Hour audit: 2026-10-09T01
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-09T01 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-10-09T01:00:00.000000641+00:00 · last event 2026-10-09T01:59:59.999983710+00:00
VOLUME 140,362,454 rows · 1,642,253,250 bytes (1.53 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured i: 140,232,597 · o: 140,211,494 · m: 140,173,162 · h: 140,158,363 · n: 140,106,319 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 1,224,859 (0.87%) · o: 68,755,011 (48.98%) · m: 68,596,201 (48.87%) · h: 1,691,757 (1.21%) · n: 94,626 (0.07%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 140,362,454 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 30d9d7320598004ef58ecabeb91cdd0d6232790ab8587482ab4536aa30fe1d7d
no line in the corpus checksum ledger names this file
joined 140,370,700 to merged 140,362,454, minus 8,246 (minus 0.0059%)
boundary drops 8,246 · 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-09T21:17:40Z 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 14,032,927 176,203,972 0-53 b49762e865e349e7ae3232806621a7573d2b89866b42cf45c32a85863548aa3c book 248,235 24,765,762 54-54 eb76658cb06908187cd6ec9ad05c580c0ce82092257d9d4f07285e9938fb3c65 last_trade_price 71,206 3,900,447 55-55 b95d7cc2e413db3c0f64935b52eb55995039cc722da4176792876c42873e4ea1 market_resolved 638 94,159 56-56 ed2a487850c65c9fcf062890e374e25f915ebbbdf6abb3a6868d2bec1fd378a8 new_market 1,192 119,076 57-57 52f626d610aab716b68d7056a1ef2751513aa0da4893259f1b85d79718c5bb93 price_change 126,005,060 1,435,457,057 58-538 26182a33710cf3fdf7f4d90decb479a1ea8da9e515e606f74d5cd2e6f0c232ea tick_size_change 3,196 117,862 539-539 212506a0fbca83a3d4ec9ac191e3744e30d2b56aa3173c5132abef665a358b08 EVENT MIX count share price_change 126,005,060 89.77% best_bid_ask 14,032,927 10.00% book 248,235 0.18% last_trade_price 71,206 0.05% tick_size_change 3,196 <0.01% new_market 1,192 <0.01% market_resolved 638 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 14,033,904 14,032,927 977 93 FULL book 248,265 248,235 30 46,117 FULL last_trade_price 71,213 71,206 7 0 FULL market_resolved 638 638 0 0 FULL new_market 1,192 1,192 0 0 FULL price_change 126,012,292 126,005,060 7,232 173 FULL tick_size_change 3,196 3,196 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 14,029,519 152,254 18ms 36ms 293ms 1.1min 0 transport_latency_assumed best_bid_ask i 14,030,933 99,746 21ms 36ms 157ms 4.4s 0 transport_latency_assumed best_bid_ask m 14,031,546 6,928,196 5ms 19ms 128ms 5.0s 0 transport_latency_assumed best_bid_ask n 14,030,154 6,153 45ms 67ms 284ms 16.4s 0 transport_latency_assumed best_bid_ask o 14,031,485 6,846,578 5ms 19ms 129ms 6.9s 0 transport_latency_assumed book h 149,775 8,814 23ms 230ms 9.2h 113.6d 0 book_staleness book i 224,620 81,758 52ms 8.0h 31.6d 132.1d 0 book_staleness book m 148,369 69,568 7ms 54ms 4.2h 113.6d 0 book_staleness book n 150,585 7,534 53ms 2.1s 16.2h 113.6d 0 book_staleness book o 148,842 80,561 7ms 61ms 6.6h 113.6d 0 book_staleness last_trade_price h 70,768 1,113 20ms 105ms 862ms 1.0min 0 transport_latency_assumed last_trade_price i 71,039 576 24ms 155ms 1.4s 4.4s 0 transport_latency_assumed last_trade_price m 70,986 32,103 7ms 32ms 211ms 2.1s 0 transport_latency_assumed last_trade_price n 70,745 52 52ms 803ms 4.8s 16.4s 0 transport_latency_assumed last_trade_price o 70,868 37,362 6ms 31ms 224ms 4.2s 0 transport_latency_assumed market_resolved h 568 72 20ms 32.8s 44.6s 44.6s 0 transport_latency_assumed market_resolved i 568 129 31ms 39.8s 54.8s 54.8s 0 transport_latency_assumed market_resolved m 568 233 7ms 40.2s 54.8s 54.8s 0 transport_latency_assumed market_resolved n 568 1 49ms 33.0s 43.0s 56.0s 0 transport_latency_assumed market_resolved o 568 203 6ms 42.7s 57.4s 1.4min 0 transport_latency_assumed new_market h 759 138 159ms 21.8s 41.3s 1.2min 0 transport_latency_assumed new_market i 759 213 109ms 24.3s 42.4s 1.6min 0 transport_latency_assumed new_market m 759 358 75ms 34.6s 40.3s 1.4min 0 transport_latency_assumed new_market n 759 70 181ms 12.6s 40.9s 1.5min 0 transport_latency_assumed new_market o 759 413 81ms 24.5s 41.2s 1.4min 0 transport_latency_assumed price_change h 125,903,778 1,529,346 19ms 43ms 481ms 1.1min 0 transport_latency_assumed price_change i 125,901,482 1,042,432 22ms 43ms 346ms 4.5s 0 transport_latency_assumed price_change m 125,917,738 61,564,220 5ms 22ms 170ms 5.2s 0 transport_latency_assumed price_change n 125,850,312 80,816 45ms 81ms 758ms 16.5s 0 transport_latency_assumed price_change o 125,955,776 61,788,246 5ms 22ms 175ms 6.9s 0 transport_latency_assumed tick_size_change h 3,196 20 18ms 28ms 63ms 21.0s 0 transport_latency_assumed tick_size_change i 3,196 5 21ms 27ms 53ms 226ms 0 transport_latency_assumed tick_size_change m 3,196 1,523 5ms 11ms 45ms 193ms 0 transport_latency_assumed tick_size_change n 3,196 not meas. 44ms 55ms 82ms 121ms 0 transport_latency_assumed tick_size_change o 3,196 1,648 5ms 12ms 54ms 145ms 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/01/2026-10-09T01.parquet sha256sum 2026-10-09T01.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.