Hour audit: 2026-10-08T17
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-08T17 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-08T17:00:00.000112035+00:00 · last event 2026-10-08T17:59:59.999994214+00:00
VOLUME 132,536,512 rows · 1,584,665,226 bytes (1.48 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 131,918,139 · m: 131,900,281 · h: 131,819,270 · i: 131,738,585 · n: 124,527,446 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 62,880,555 (47.44%) · m: 65,295,315 (49.27%) · h: 1,661,684 (1.25%) · i: 2,034,732 (1.54%) · n: 664,226 (0.50%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 1264e7dbfdb8f1a9ccbd4b1fb79e3eeca82e63726d89d97cbc3324f564340ddf
the corpus checksum ledger names this file with the same digest
joined 132,538,145 to merged 132,536,512, minus 1,633 (minus 0.0012%)
boundary drops 1,633 · 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-08T19:08:14Z 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 13,246,476 169,925,060 0-50 e4b3545358be219408b4c1d8212e0ed541234752d34390989722af433b425799 book 710,859 72,739,318 51-53 2960a87fe280102d748cd28f7344aef70d29d144f9b5f0c407c8e5644931db2d last_trade_price 66,371 3,775,149 54-54 97c45bde3be85bdb006931000f2208843e24ff9bb5c222f6e30313faa99ef44a market_resolved 530 80,682 55-55 25a9aa7b3d2dd23fdd8fcfaa7c66ee12f186dd994834787fe4ab1a9833883a53 new_market 4,588 419,952 56-56 b0987401326a78b5defc50671ca64632040a873a2dd30491f8037a0c426388eb price_change 118,504,748 1,336,107,165 57-509 3de1d7594a41ce4e881d8ba9bcab95804fe01d019e2c7d8de99b742d50bdcca4 tick_size_change 2,940 108,933 510-510 54bd35999d78191e06b3491b126a6264f42139d3a2abaeac4bb89971051cf749 EVENT MIX count share price_change 118,504,748 89.41% best_bid_ask 13,246,476 9.99% book 710,859 0.54% last_trade_price 66,371 0.05% new_market 4,588 <0.01% tick_size_change 2,940 <0.01% market_resolved 530 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,246,630 13,246,476 154 1,141 FULL book 710,881 710,859 22 266,225 FULL last_trade_price 66,372 66,371 1 97 FULL market_resolved 530 530 0 36 FULL new_market 4,588 4,588 0 114 FULL price_change 118,506,204 118,504,748 1,456 670 FULL tick_size_change 2,940 2,940 0 31 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 13,240,091 158,490 22ms 82ms 894ms 1.9min 0 transport_latency_assumed best_bid_ask i 13,241,401 193,569 22ms 46ms 250ms 22.6s 0 transport_latency_assumed best_bid_ask m 13,245,061 6,524,593 6ms 27ms 183ms 8.2s 0 transport_latency_assumed best_bid_ask n 12,567,753 9,329 46ms 88ms 708ms 33.5s 0 transport_latency_assumed best_bid_ask o 13,244,643 6,360,495 6ms 28ms 229ms 12.9s 0 transport_latency_assumed book h 152,856 11,087 42ms 8.1s 13.9h 113.3d 0 book_staleness book i 142,790 8,444 30ms 1.4s 6.0h 113.3d 0 book_staleness book m 142,615 75,613 9ms 104ms 4.9h 113.2d 0 book_staleness book n 676,633 551,180 7.8min 13.2h 47.1d 131.8d 0 book_staleness book o 143,467 64,535 10ms 150ms 9.3h 113.3d 0 book_staleness last_trade_price h 66,109 853 30ms 335ms 4.0s 59.3s 0 transport_latency_assumed last_trade_price i 65,680 956 28ms 359ms 3.9s 14.0s 0 transport_latency_assumed last_trade_price m 66,235 34,341 8ms 42ms 254ms 2.4s 0 transport_latency_assumed last_trade_price n 58,399 103 61ms 3.1s 16.4s 31.5s 0 transport_latency_assumed last_trade_price o 66,178 30,118 9ms 50ms 304ms 6.3s 0 transport_latency_assumed market_resolved h 484 26 34ms 344ms 39.7s 39.7s 0 transport_latency_assumed market_resolved i 484 41 30ms 19.5s 53.7s 57.1s 0 transport_latency_assumed market_resolved m 484 220 8ms 22.0s 55.0s 55.1s 0 transport_latency_assumed market_resolved n 449 28 52ms 415ms 4.1min 6.5min 0 transport_latency_assumed market_resolved o 484 215 9ms 19.8s 53.6s 57.1s 0 transport_latency_assumed new_market h 2,664 700 239ms 37.5s 49.7s 1.3min 0 transport_latency_assumed new_market i 2,664 1,001 151ms 41.7s 51.1s 1.6min 0 transport_latency_assumed new_market m 2,672 1,074 105ms 40.6s 48.3s 1.4min 0 transport_latency_assumed new_market n 2,568 757 170ms 43.2s 5.7min 33.9min 0 transport_latency_assumed new_market o 2,669 1,056 168ms 40.9s 49.8s 1.4min 0 transport_latency_assumed price_change h 118,354,150 1,490,504 23ms 117ms 2.2s 2.0min 0 transport_latency_assumed price_change i 118,282,626 1,830,696 23ms 67ms 1.2s 22.6s 0 transport_latency_assumed price_change m 118,440,274 58,657,918 7ms 31ms 206ms 9.5s 0 transport_latency_assumed price_change n 111,218,804 102,826 47ms 172ms 8.0s 33.5s 0 transport_latency_assumed price_change o 118,457,758 56,422,804 7ms 33ms 252ms 16.9s 0 transport_latency_assumed tick_size_change h 2,916 24 22ms 78ms 399ms 6.2s 0 transport_latency_assumed tick_size_change i 2,940 25 23ms 50ms 148ms 303ms 0 transport_latency_assumed tick_size_change m 2,940 1,556 6ms 25ms 106ms 332ms 0 transport_latency_assumed tick_size_change n 2,840 3 46ms 77ms 350ms 511ms 0 transport_latency_assumed tick_size_change o 2,940 1,332 7ms 30ms 183ms 15.4s 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-08/17/2026-10-08T17.parquet sha256sum 2026-10-08T17.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.