Hour audit: 2026-10-09T20
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.
1 check could not be evaluated for this hour, listed with the reason in the block below. A check we could not run is recorded as exactly that, and never counted as a pass.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-10-09T20 · corpus v3 · verdict AUDIT PENDING
COVERAGE not measured (this hour is not in the corpus attestation, so we have not looked at it)
VOLUME 128,075,922 rows · 1,492,266,706 bytes (1.39 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured i: 127,702,435 · o: 127,091,657 · m: 126,979,505 · h: 126,926,311 · n: 126,853,101 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 1,498,247 (1.17%) · o: 59,136,912 (46.17%) · m: 66,391,933 (51.84%) · h: 855,821 (0.67%) · n: 193,009 (0.15%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 d4514ceaae181b254bd00007b6ded623e22f3907f66f1c67df4c91a022a97a6c
no line in the corpus checksum ledger names this file
joined 128,101,118 to merged 128,075,922, minus 25,196 (minus 0.0197%)
boundary drops 25,196 · 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-10T07:43:09Z 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 6/8 pass, 1 finding, 1 not evaluated
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
SKIPPED the hour's minutes have not been measured
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 12,538,581 157,018,632 0-47 80465cb66b1aaefdbed6547332c2c448f0c9379610e60c7f9ad8d002cdb7ba28 book 910,375 79,767,969 48-51 9b9518b976d7dc8fab59759ce3143d7efa36b5e1e2e6c30675052c4ab801c70d last_trade_price 60,767 3,537,154 52-52 8cc950a043c8ea34e54272463a1781a237316f2415138d9ce607e306a5051e4a market_resolved 3,265 488,735 53-53 785334f349ef211ce2e5353ef22e475eb0ce2398a350a7032c70f77a60e5b620 new_market 1,776 173,597 54-54 f22a6b7c8f726629ff35ffd6aff38505fc518846cec4343fac1e6f44ad2988c9 price_change 114,554,458 1,249,577,980 55-491 1a587c6d4f6e6aea281771f405e4bb6faacd9778a9e99c204a8240535f55b193 tick_size_change 6,700 246,219 492-492 5cfd72cc3c7b78053b253fb4feab1f3d3375daeeb976098ac82563982d04e072 EVENT MIX count share price_change 114,554,458 89.44% best_bid_ask 12,538,581 9.79% book 910,375 0.71% last_trade_price 60,767 0.05% tick_size_change 6,700 <0.01% market_resolved 3,265 <0.01% new_market 1,776 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,540,957 12,538,581 2,376 130 FULL book 911,167 910,375 792 244,682 FULL last_trade_price 60,832 60,767 65 30 FULL market_resolved 3,270 3,265 5 5 FULL new_market 1,778 1,776 2 5 FULL price_change 114,576,414 114,554,458 21,956 1,722 FULL tick_size_change 6,700 6,700 0 1 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 12,538,219 65,661 18ms 29ms 457ms 1.0min 0 transport_latency_assumed best_bid_ask i 12,534,723 66,745 21ms 39ms 137ms 4.2s 0 transport_latency_assumed best_bid_ask m 12,537,607 6,636,886 5ms 13ms 125ms 14.6s 0 transport_latency_assumed best_bid_ask n 12,536,061 9,747 44ms 59ms 301ms 26.4s 0 transport_latency_assumed best_bid_ask o 12,537,786 5,759,542 5ms 13ms 143ms 8.5s 0 transport_latency_assumed book h 221,540 68,277 88ms 8.8h 34.3d 132.9d 0 book_staleness book i 672,021 491,396 8.0min 1.7d 48.3d 132.9d 0 book_staleness book m 241,151 142,029 198ms 9.7h 37.1d 132.9d 0 book_staleness book n 216,918 62,289 224ms 8.4h 34.3d 132.9d 0 book_staleness book o 257,275 146,384 4.6s 10.9h 34.3d 132.9d 0 book_staleness last_trade_price h 60,713 522 20ms 74ms 910ms 1.0min 0 transport_latency_assumed last_trade_price i 60,549 337 24ms 129ms 1.2s 3.6s 0 transport_latency_assumed last_trade_price m 60,640 31,953 6ms 19ms 254ms 3.1s 0 transport_latency_assumed last_trade_price n 60,100 155 46ms 237ms 3.9s 26.0s 0 transport_latency_assumed last_trade_price o 60,720 27,800 6ms 21ms 259ms 3.5s 0 transport_latency_assumed market_resolved h 3,060 18 20ms 104ms 53.4s 55.5s 0 transport_latency_assumed market_resolved i 3,057 388 24ms 18.8s 51.4s 52.6s 0 transport_latency_assumed market_resolved m 3,056 1,425 6ms 12.6s 52.9s 56.7s 0 transport_latency_assumed market_resolved n 3,059 4 47ms 270ms 52.9s 55.5s 0 transport_latency_assumed market_resolved o 3,056 1,430 6ms 27ms 47.6s 57.9s 0 transport_latency_assumed new_market h 1,072 159 199ms 10.2s 28.0s 1.7min 0 transport_latency_assumed new_market i 1,072 477 45ms 9.8s 17.6s 1.7min 0 transport_latency_assumed new_market m 1,075 694 46ms 11.1s 30.7s 1.6min 0 transport_latency_assumed new_market n 1,077 158 252ms 11.7s 30.1s 1.5min 0 transport_latency_assumed new_market o 1,072 288 120ms 12.3s 29.1s 1.6min 0 transport_latency_assumed price_change h 114,095,007 721,140 18ms 34ms 611ms 1.0min 0 transport_latency_assumed price_change i 114,424,317 938,880 21ms 41ms 384ms 4.6s 0 transport_latency_assumed price_change m 114,129,276 59,575,458 5ms 14ms 165ms 14.6s 0 transport_latency_assumed price_change n 114,029,186 120,648 44ms 72ms 750ms 27.9s 0 transport_latency_assumed price_change o 114,225,048 53,198,332 5ms 15ms 186ms 9.4s 0 transport_latency_assumed tick_size_change h 6,700 44 18ms 28ms 196ms 7.3s 0 transport_latency_assumed tick_size_change i 6,696 24 21ms 39ms 91ms 277ms 0 transport_latency_assumed tick_size_change m 6,700 3,488 5ms 13ms 54ms 2.6s 0 transport_latency_assumed tick_size_change n 6,700 8 44ms 59ms 121ms 551ms 0 transport_latency_assumed tick_size_change o 6,700 3,136 6ms 14ms 67ms 638ms 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/20/2026-10-09T20.parquet sha256sum 2026-10-09T20.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.