Hour audit: 2026-10-09T16
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-09T16 · corpus v3 · verdict AUDIT PENDING
COVERAGE not measured (this hour is not in the corpus attestation, so we have not looked at it)
VOLUME 124,856,446 rows · 1,525,376,928 bytes (1.42 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 123,692,537 · h: 123,578,669 · i: 123,462,597 · n: 118,630,862 · m: 118,366,749 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 61,146,385 (48.97%) · h: 1,757,885 (1.41%) · i: 2,513,416 (2.01%) · n: 1,266,026 (1.01%) · m: 58,172,734 (46.59%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 100fd08d0d40f3c35ec92269b7b82f93405e12a7c31c41b808b5e2101cdd4e18
no line in the corpus checksum ledger names this file
joined 124,872,075 to merged 124,856,446, minus 15,629 (minus 0.0125%)
boundary drops 15,629 · 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-10T05:23:05Z 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,291,527 160,862,200 0-46 0abd79a25f15bc916bc7e791def405086c709060b7d480dc79ca0d67b8ae9c02 book 1,411,479 104,486,420 47-52 4aaa44a0394752d58a02e6678033df30a9683ca3188b6bc42cef141081ca9186 last_trade_price 61,572 3,666,417 53-53 58a77a7adbc9ff011550664f7d96d9fddc0345340c476f7f4ce893fcaa2b95bc market_resolved 1,620 235,821 54-54 fe0f5821b29b80f86d40a8c2e7522f372d2f43d86fe502e8df64b0e76b480024 new_market 10,238 951,054 55-55 5881f8efbba4626adabeb62133c52fb73a8ce141c1eeaf2edb5f0897737d0268 price_change 111,073,498 1,253,511,325 56-479 72ef0f519a74a7533e33f30ed9deabbcf3b9e107ed590f0843d11edcac2eb389 tick_size_change 6,512 242,879 480-480 953a28b4dd07cf8c833e31f37d233b6a067ef03e5a6b90f3a116ef03b395673f EVENT MIX count share price_change 111,073,498 88.96% best_bid_ask 12,291,527 9.84% book 1,411,479 1.13% last_trade_price 61,572 0.05% new_market 10,238 <0.01% tick_size_change 6,512 <0.01% market_resolved 1,620 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,292,142 12,291,527 615 1,453 FULL book 1,416,229 1,411,479 4,750 266,308 FULL last_trade_price 61,574 61,572 2 252 FULL market_resolved 1,634 1,620 14 30 FULL new_market 10,238 10,238 0 0 FULL price_change 111,083,746 111,073,498 10,248 3,093 FULL tick_size_change 6,512 6,512 0 127 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 12,283,327 166,081 19ms 119ms 3.5s 2.1min 0 transport_latency_assumed best_bid_ask i 12,286,872 246,285 21ms 52ms 324ms 10.4s 0 transport_latency_assumed best_bid_ask m 11,708,662 5,720,499 6ms 26ms 337ms 24.8s 0 transport_latency_assumed best_bid_ask n 11,752,996 54,975 45ms 131ms 648ms 17.5s 0 transport_latency_assumed best_bid_ask o 12,288,637 6,103,687 6ms 33ms 411ms 28.5s 0 transport_latency_assumed book h 362,275 117,317 1.2min 21.3h 48.0d 132.8d 0 book_staleness book i 261,793 63,840 3.5s 11.1h 37.9d 132.8d 0 book_staleness book m 855,269 479,263 8.3min 1.5d 48.1d 132.8d 0 book_staleness book n 800,024 594,472 5.7min 1.5d 48.1d 132.7d 0 book_staleness book o 327,608 156,587 45.0s 18.4h 44.9d 132.8d 0 book_staleness last_trade_price h 61,337 577 23ms 383ms 4.4s 1.1min 0 transport_latency_assumed last_trade_price i 61,283 820 36ms 673ms 5.6s 10.4s 0 transport_latency_assumed last_trade_price m 59,200 29,797 7ms 34ms 376ms 9.5s 0 transport_latency_assumed last_trade_price n 58,354 520 58ms 1.0s 8.7s 17.5s 0 transport_latency_assumed last_trade_price o 61,489 29,858 7ms 42ms 466ms 10.0s 0 transport_latency_assumed market_resolved h 1,480 12 35ms 29.5s 50.4s 1.4min 0 transport_latency_assumed market_resolved i 1,466 270 46ms 21.4s 50.0s 52.5s 0 transport_latency_assumed market_resolved m 1,462 662 7ms 26.1s 4.6min 7.1min 0 transport_latency_assumed market_resolved n 1,507 55 72ms 32.8s 7.2min 7.2min 0 transport_latency_assumed market_resolved o 1,480 621 7ms 29.9s 48.8s 49.1s 0 transport_latency_assumed new_market h 6,085 1,352 223ms 43.9s 38.1min 42.6min 0 transport_latency_assumed new_market i 6,085 2,036 160ms 43.8s 34.1min 42.2min 0 transport_latency_assumed new_market m 6,225 3,415 97ms 45.5s 34.5min 42.7min 0 transport_latency_assumed new_market n 6,170 858 277ms 46.5s 38.1min 42.6min 0 transport_latency_assumed new_market o 6,085 2,577 136ms 41.1s 31.0min 42.2min 0 transport_latency_assumed price_change h 110,857,653 1,472,521 20ms 173ms 3.8s 2.1min 0 transport_latency_assumed price_change i 110,838,586 2,200,102 22ms 87ms 1.2s 10.4s 0 transport_latency_assumed price_change m 105,729,571 51,935,947 6ms 29ms 345ms 24.8s 0 transport_latency_assumed price_change n 106,005,655 615,126 46ms 210ms 3.1s 17.6s 0 transport_latency_assumed price_change o 111,000,726 54,849,802 6ms 37ms 419ms 29.3s 0 transport_latency_assumed tick_size_change h 6,512 25 19ms 47ms 1.8s 30.6s 0 transport_latency_assumed tick_size_change i 6,512 63 21ms 50ms 254ms 539ms 0 transport_latency_assumed tick_size_change m 6,360 3,151 5ms 12ms 263ms 1.6s 0 transport_latency_assumed tick_size_change n 6,156 20 45ms 127ms 614ms 1.0s 0 transport_latency_assumed tick_size_change o 6,512 3,253 5ms 14ms 330ms 5.3s 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/16/2026-10-09T16.parquet sha256sum 2026-10-09T16.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.