Hour audit: 2026-10-08T02
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-08T02 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-08T02:00:00.000131560+00:00 · last event 2026-10-08T02:59:59.998085821+00:00
VOLUME 132,696,715 rows · 1,519,319,309 bytes (1.41 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured i: 132,454,825 · o: 132,385,809 · h: 132,278,912 · m: 132,256,702 · n: 132,220,457 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 1,086,117 (0.82%) · o: 64,933,172 (48.93%) · h: 1,609,456 (1.21%) · m: 65,010,732 (48.99%) · n: 57,238 (0.04%) (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 132,696,715 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 1012d8c9cdcca2547f0638fbfa20ec084ad8c02f513f4fec538fd7b502d5874c
the corpus checksum ledger names this file with the same digest
joined 132,698,361 to merged 132,696,715, minus 1,646 (minus 0.0012%)
boundary drops 1,646 · 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-08T04:59:02Z 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 12,336,908 154,179,587 0-47 3b52a91c342921bc54bdffd237676ffd832fc8d1429d4d5fec54c326e38dbc12 book 435,005 46,185,559 48-49 710e86d0b85c4c3629280cf0313acd14ffe8a5cbef98295ed9789b0e0e082d6e last_trade_price 50,133 2,803,465 50-50 4118058357eebd524c8af59018ae4b33ca99062ef735eefa5dbef1661b545824 market_resolved 1,161 171,764 51-51 1448718e2093703a7ea1942c81f017d1a5927c1a0d1d15d0bda21770900e9fcc new_market 838 88,825 52-52 019195352ba8553cb52639d3bdd7ade12c171f6f79c94e38b5a7fc198a65cd26 price_change 119,870,082 1,314,281,041 53-510 090f050564290d4294b0e69c7769bd3482155d0da7b661944a42df924b39eed1 tick_size_change 2,588 96,653 511-511 d353e7a29fadd7f2ef5baffc8719eff61a5380eae7b678eb38dd7bed06d07eb8 EVENT MIX count share price_change 119,870,082 90.33% best_bid_ask 12,336,908 9.30% book 435,005 0.33% last_trade_price 50,133 0.04% tick_size_change 2,588 <0.01% market_resolved 1,161 <0.01% new_market 838 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,337,074 12,336,908 166 78 FULL book 435,015 435,005 10 149,447 FULL last_trade_price 50,135 50,133 2 0 FULL market_resolved 1,161 1,161 0 0 FULL new_market 838 838 0 0 FULL price_change 119,871,550 119,870,082 1,468 101 FULL tick_size_change 2,588 2,588 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 12,336,022 130,728 18ms 33ms 145ms 30.8s 0 transport_latency_assumed best_bid_ask i 12,331,951 76,538 21ms 34ms 118ms 2.4s 0 transport_latency_assumed best_bid_ask m 12,336,262 6,119,862 5ms 18ms 95ms 6.3s 0 transport_latency_assumed best_bid_ask n 12,335,071 3,216 44ms 62ms 192ms 10.1s 0 transport_latency_assumed best_bid_ask o 12,336,072 6,006,564 5ms 18ms 95ms 6.7s 0 transport_latency_assumed book h 127,256 24,728 25ms 1.5h 27.7d 131.2d 0 book_staleness book i 326,403 205,020 3.3min 1.3d 46.5d 131.2d 0 book_staleness book m 152,883 92,720 13ms 7.4h 30.7d 131.2d 0 book_staleness book n 125,985 19,746 56ms 56.6min 25.5d 112.7d 0 book_staleness book o 154,124 92,791 14ms 7.1h 30.7d 131.2d 0 book_staleness last_trade_price h 50,064 1,068 21ms 64ms 317ms 21.3s 0 transport_latency_assumed last_trade_price i 49,623 429 24ms 89ms 524ms 2.2s 0 transport_latency_assumed last_trade_price m 50,077 23,886 6ms 31ms 180ms 1.9s 0 transport_latency_assumed last_trade_price n 49,827 35 50ms 313ms 4.9s 10.1s 0 transport_latency_assumed last_trade_price o 50,005 24,715 6ms 32ms 213ms 1.9s 0 transport_latency_assumed market_resolved h 1,052 66 21ms 221ms 52.8s 56.7s 0 transport_latency_assumed market_resolved i 1,052 182 24ms 32.6s 55.8s 1.0min 0 transport_latency_assumed market_resolved m 1,052 477 7ms 32.2s 54.8s 57.7s 0 transport_latency_assumed market_resolved n 1,052 32 47ms 194ms 54.0s 54.1s 0 transport_latency_assumed market_resolved o 1,052 404 6ms 32.5s 54.5s 57.5s 0 transport_latency_assumed new_market h 552 74 109ms 29.0s 50.5s 1.2min 0 transport_latency_assumed new_market i 552 156 69ms 28.4s 1.1min 1.7min 0 transport_latency_assumed new_market m 552 256 41ms 16.5s 1.3min 1.8min 0 transport_latency_assumed new_market n 552 91 78ms 17.2s 1.1min 1.6min 0 transport_latency_assumed new_market o 552 261 46ms 28.5s 44.3s 1.1min 0 transport_latency_assumed price_change h 119,761,378 1,452,782 18ms 37ms 197ms 31.3s 0 transport_latency_assumed price_change i 119,742,656 803,778 21ms 40ms 197ms 2.9s 0 transport_latency_assumed price_change m 119,713,288 58,772,204 5ms 20ms 107ms 7.2s 0 transport_latency_assumed price_change n 119,705,382 34,118 45ms 76ms 697ms 10.1s 0 transport_latency_assumed price_change o 119,841,416 58,807,200 5ms 20ms 106ms 7.9s 0 transport_latency_assumed tick_size_change h 2,588 10 18ms 27ms 318ms 8.0s 0 transport_latency_assumed tick_size_change i 2,588 14 21ms 29ms 122ms 313ms 0 transport_latency_assumed tick_size_change m 2,588 1,327 4ms 12ms 71ms 167ms 0 transport_latency_assumed tick_size_change n 2,588 not meas. 44ms 53ms 338ms 448ms 0 transport_latency_assumed tick_size_change o 2,588 1,237 4ms 11ms 60ms 319ms 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/02/2026-10-08T02.parquet sha256sum 2026-10-08T02.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.