Hour audit: 2026-10-10T04
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-10T04 · 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,647,628 rows · 1,388,796,883 bytes (1.29 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured h: 124,504,599 · m: 124,497,756 · o: 124,495,808 · i: 124,475,654 · n: 124,463,570 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 584,385 (0.47%) · m: 61,990,904 (49.73%) · o: 61,050,576 (48.98%) · i: 824,652 (0.66%) · n: 197,111 (0.16%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 33e4a12a375abed485f02726c5d41fba14a3076bedb10f68aff619e6a38e9db4
no line in the corpus checksum ledger names this file
joined 124,649,944 to merged 124,647,628, minus 2,316 (minus 0.0019%)
boundary drops 2,316 · 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-10T11:54:38Z 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,205,798 150,736,850 0-46 cc08259fe9373e44080435257979d84a3f58f95010fce8d39d06e2e6b52607af book 236,931 25,792,971 47-47 6ac49a2907af9936d1317fa443c30e4c326305df8dd9442939e3edd93f221672 last_trade_price 42,374 2,525,855 48-48 cbed30aae49950e790bfcbe0b6d0c5a82e80180868b6df972ee749158748555a market_resolved 1,166 187,390 49-49 6d74d6c3f86c6e564795fdc30be666daccbeb08ef9e365774498f9304eab985e new_market 2,495 241,952 50-50 04b947770ccb254e25d96c3db09589ce78b764e28c5aa39c77b5d133d2f6cd5d price_change 112,153,720 1,207,704,893 51-478 a0067fb1f0065f3968b7a2682cca355d01955384882038383d5eeec0e97eb05f tick_size_change 5,144 188,866 479-479 e549911691d95476d4e0ac60f985cce7ebfff8e27f60a50ef61ab138728dcaab EVENT MIX count share price_change 112,153,720 89.98% best_bid_ask 12,205,798 9.79% book 236,931 0.19% last_trade_price 42,374 0.03% tick_size_change 5,144 <0.01% new_market 2,495 <0.01% market_resolved 1,166 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,206,126 12,205,798 328 125 FULL book 237,021 236,931 90 67,818 FULL last_trade_price 42,374 42,374 0 0 FULL market_resolved 1,166 1,166 0 2 FULL new_market 2,495 2,495 0 0 FULL price_change 112,155,618 112,153,720 1,898 113 FULL tick_size_change 5,144 5,144 0 3 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 12,199,854 42,790 17ms 25ms 1.5s 2.2min 0 transport_latency_assumed best_bid_ask i 12,204,558 73,883 21ms 39ms 136ms 8.5s 0 transport_latency_assumed best_bid_ask m 12,204,544 6,070,041 4ms 10ms 161ms 14.1s 0 transport_latency_assumed best_bid_ask n 12,204,501 15,923 44ms 54ms 312ms 15.2s 0 transport_latency_assumed best_bid_ask o 12,204,135 6,003,161 4ms 10ms 177ms 28.2s 0 transport_latency_assumed book h 160,025 69,584 122ms 12.8h 40.5d 114.8d 0 book_staleness book i 96,748 10,554 24ms 3.9s 2.0d 114.7d 0 book_staleness book m 120,703 74,251 7ms 3.1h 32.7d 133.2d 0 book_staleness book n 96,541 9,467 46ms 4.1s 2.0d 114.7d 0 book_staleness book o 119,035 73,075 7ms 2.5h 32.7d 114.7d 0 book_staleness last_trade_price h 42,330 258 19ms 45ms 3.0s 51.4s 0 transport_latency_assumed last_trade_price i 42,320 399 23ms 42ms 316ms 3.5s 0 transport_latency_assumed last_trade_price m 42,345 20,524 5ms 14ms 258ms 11.4s 0 transport_latency_assumed last_trade_price n 42,306 79 45ms 104ms 1.2s 15.2s 0 transport_latency_assumed last_trade_price o 42,232 21,114 5ms 14ms 275ms 10.5s 0 transport_latency_assumed market_resolved h 1,108 2 21ms 21.1s 52.9s 54.7s 0 transport_latency_assumed market_resolved i 1,110 167 25ms 22.0s 52.3s 53.1s 0 transport_latency_assumed market_resolved m 1,110 454 5ms 22.3s 52.7s 53.4s 0 transport_latency_assumed market_resolved n 1,110 2 46ms 531ms 55.6s 55.7s 0 transport_latency_assumed market_resolved o 1,110 541 5ms 927ms 55.9s 56.0s 0 transport_latency_assumed new_market h 1,574 277 449ms 34.2s 1.1min 2.2min 0 transport_latency_assumed new_market i 1,574 413 203ms 35.0s 59.4s 1.5min 0 transport_latency_assumed new_market m 1,574 874 199ms 38.9s 1.2min 2.0min 0 transport_latency_assumed new_market n 1,574 298 376ms 34.0s 53.6s 2.2min 0 transport_latency_assumed new_market o 1,574 633 192ms 34.1s 41.4s 1.9min 0 transport_latency_assumed price_change h 112,094,576 471,454 18ms 28ms 1.5s 2.3min 0 transport_latency_assumed price_change i 112,124,200 739,192 21ms 40ms 185ms 8.5s 0 transport_latency_assumed price_change m 112,122,336 55,822,338 4ms 11ms 184ms 14.9s 0 transport_latency_assumed price_change n 112,112,394 171,338 44ms 59ms 438ms 15.3s 0 transport_latency_assumed price_change o 112,122,578 54,949,398 4ms 11ms 198ms 28.2s 0 transport_latency_assumed tick_size_change h 5,132 20 17ms 24ms 3.8s 1.3min 0 transport_latency_assumed tick_size_change i 5,144 44 21ms 39ms 194ms 351ms 0 transport_latency_assumed tick_size_change m 5,144 2,422 4ms 11ms 156ms 389ms 0 transport_latency_assumed tick_size_change n 5,144 4 43ms 50ms 1.0s 1.4s 0 transport_latency_assumed tick_size_change o 5,144 2,654 4ms 9ms 265ms 1.8s 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-10/04/2026-10-10T04.parquet sha256sum 2026-10-10T04.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.