Hour audit: 2026-10-05T11
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-05T11 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-05T11:00:00.000087064+00:00 · last event 2026-10-05T11:59:59.999974093+00:00
VOLUME 107,076,805 rows · 1,197,531,340 bytes (1.12 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 106,986,758 · m: 106,951,700 · h: 106,937,551 · i: 106,927,129 · n: 106,883,586 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 53,142,800 (49.63%) · m: 52,638,079 (49.16%) · h: 588,881 (0.55%) · i: 658,079 (0.61%) · n: 48,966 (0.05%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 107,076,805 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 984f7381dd656da873ef6301e9b3ca2b82fbcc26d416ad983f387399fba55355
the corpus checksum ledger names this file with the same digest
joined 107,077,853 to merged 107,076,805, minus 1,048 (minus 0.0010%)
boundary drops 1,048 · 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-05T13:04:24Z 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 9,476,844 118,502,601 0-36 9b9b47444966c3dbdff2388e559a39a11c2cfd6e89fd6f2b0f66e225e67586c1 book 124,456 13,758,673 37-37 2b50234bed16af841f7fcf2f1f275e6d88a883b0c2b5d54366599b772c57acfa last_trade_price 52,471 3,020,461 38-38 7cff0c61b743f21cce5d7cae178281c6594a5a442943da747768103510aba7e8 market_resolved 849 140,001 39-39 df38e2315e09d77113386984564dd82afbf814d4167eeab1d0368ce92a87c7d8 new_market 1,961 180,961 40-40 1d9a164605adfc0cd6befdd8d6ec26f72d794beeb98cefdc0812a7437b513827 price_change 97,416,920 1,060,582,458 41-412 7e7a5ff608b4ea2d9c438a10511628a5d50f744264c58ed2d301105a258951cd tick_size_change 3,304 122,701 413-413 764745203ecfb366ad92b73569674849c010ed457df933fcced38346fe41c680 EVENT MIX count share price_change 97,416,920 90.98% best_bid_ask 9,476,844 8.85% book 124,456 0.12% last_trade_price 52,471 0.05% tick_size_change 3,304 <0.01% new_market 1,961 <0.01% market_resolved 849 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,476,920 9,476,844 76 71 FULL book 124,456 124,456 0 6,057 FULL last_trade_price 52,471 52,471 0 0 FULL market_resolved 849 849 0 0 FULL new_market 1,961 1,961 0 0 FULL price_change 97,417,892 97,416,920 972 1,238 FULL tick_size_change 3,304 3,304 0 1 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 9,474,195 44,990 19ms 35ms 368ms 2.0min 0 transport_latency_assumed best_bid_ask i 9,474,654 49,423 21ms 30ms 120ms 6.6s 0 transport_latency_assumed best_bid_ask m 9,474,664 4,733,361 5ms 13ms 86ms 7.2s 0 transport_latency_assumed best_bid_ask n 9,473,454 2,705 43ms 62ms 299ms 21.0s 0 transport_latency_assumed best_bid_ask o 9,476,198 4,646,365 5ms 13ms 88ms 26.5s 0 transport_latency_assumed book h 113,248 7,546 27ms 659ms 15.1h 110.1d 0 book_staleness book i 108,166 3,242 24ms 128ms 16.5s 128.5d 0 book_staleness book m 108,872 52,220 7ms 40ms 1.5h 110.0d 0 book_staleness book n 111,210 5,089 49ms 1.4s 10.4h 110.0d 0 book_staleness book o 109,082 56,359 7ms 35ms 46.9min 110.0d 0 book_staleness last_trade_price h 52,215 301 22ms 149ms 1.7s 37.6s 0 transport_latency_assumed last_trade_price i 52,263 532 23ms 84ms 1.0s 5.7s 0 transport_latency_assumed last_trade_price m 52,131 25,225 6ms 22ms 187ms 1.7s 0 transport_latency_assumed last_trade_price n 51,968 45 48ms 423ms 5.1s 21.3s 0 transport_latency_assumed last_trade_price o 52,298 26,368 6ms 20ms 176ms 2.5s 0 transport_latency_assumed market_resolved h 841 3 22ms 31.0s 46.1s 53.0s 0 transport_latency_assumed market_resolved i 841 124 23ms 21.8s 34.3s 1.1min 0 transport_latency_assumed market_resolved m 841 349 6ms 26.6s 38.6s 53.9s 0 transport_latency_assumed market_resolved n 841 not meas. 46ms 25.0s 40.1s 47.2s 0 transport_latency_assumed market_resolved o 841 373 6ms 22.9s 38.0s 44.8s 0 transport_latency_assumed new_market h 1,151 271 310ms 36.7s 41.0s 1.6min 0 transport_latency_assumed new_market i 1,151 388 122ms 37.3s 42.5s 1.5min 0 transport_latency_assumed new_market m 1,151 546 64ms 37.4s 42.5s 55.8s 0 transport_latency_assumed new_market n 1,151 101 227ms 35.8s 41.4s 1.7min 0 transport_latency_assumed new_market o 1,151 655 97ms 36.0s 41.6s 1.4min 0 transport_latency_assumed price_change h 97,292,597 535,756 20ms 44ms 602ms 2.0min 0 transport_latency_assumed price_change i 97,286,750 604,370 22ms 36ms 318ms 6.9s 0 transport_latency_assumed price_change m 97,310,737 47,824,714 5ms 15ms 106ms 7.9s 0 transport_latency_assumed price_change n 97,241,662 41,026 44ms 81ms 1.5s 21.4s 0 transport_latency_assumed price_change o 97,343,884 48,411,054 5ms 14ms 104ms 27.7s 0 transport_latency_assumed tick_size_change h 3,304 14 20ms 35ms 234ms 3.0s 0 transport_latency_assumed tick_size_change i 3,304 not meas. 22ms 42ms 92ms 329ms 0 transport_latency_assumed tick_size_change m 3,304 1,664 5ms 13ms 35ms 229ms 0 transport_latency_assumed tick_size_change n 3,300 not meas. 43ms 59ms 118ms 1.8s 0 transport_latency_assumed tick_size_change o 3,304 1,626 5ms 11ms 43ms 171ms 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/11/2026-10-05T11.parquet sha256sum 2026-10-05T11.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.