Hour audit: 2026-10-08T15
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-08T15 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-08T15:00:00.000058731+00:00 · last event 2026-10-08T15:59:59.999975363+00:00
VOLUME 128,631,417 rows · 1,504,581,769 bytes (1.40 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured m: 128,506,630 · o: 128,481,054 · h: 128,318,047 · i: 128,223,497 · n: 127,120,529 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 65,433,704 (50.87%) · o: 59,885,416 (46.56%) · h: 1,771,858 (1.38%) · i: 1,443,434 (1.12%) · n: 97,005 (0.08%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 128,631,417 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 58ea824577534fe05bd1e380ecfa82a7cbdf5eb3c0026ba0640ee2305c596169
the corpus checksum ledger names this file with the same digest
joined 128,637,083 to merged 128,631,417, minus 5,666 (minus 0.0044%)
boundary drops 5,666 · 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-08T17:24:03Z 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,512,324 160,827,187 0-47 7e6625604f76cfcbdd25296a053919064960ca938c87b48515c2edfdafc1916a book 256,569 27,932,535 48-48 677055f0e46df2ba60dd6a583ab20482b520966bc1d70325e9df2edca7ea388c last_trade_price 73,411 4,207,360 49-49 dba9704b5420cca4877d5ab4a31772af33e32d9b28d59edf9d0d2d19b9567f49 market_resolved 884 144,718 50-50 4292be553799606dbefc66b755605bcb8a63f37f0defabbd1ce26665d133a3d3 new_market 3,181 292,154 51-51 fc74dc44a4634be221e09ff6947629e781338302c1ea718d24b62e47510bf78e price_change 115,781,944 1,309,601,885 52-493 060e2cc7eac2e4dfaea29b1f0982fcee8ee0072a09bf0fd13e0e85fb4a546767 tick_size_change 3,104 114,210 494-494 3e07bb0b8dbb8006bba1bb4e1fdf45861760f287f2886a7932c45d5a6dfe2c71 EVENT MIX count share price_change 115,781,944 90.01% best_bid_ask 12,512,324 9.73% book 256,569 0.20% last_trade_price 73,411 0.06% new_market 3,181 <0.01% tick_size_change 3,104 <0.01% market_resolved 884 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,512,432 12,512,324 108 243 FULL book 256,570 256,569 1 45,215 FULL last_trade_price 73,412 73,411 1 0 FULL market_resolved 884 884 0 0 FULL new_market 3,181 3,181 0 2 FULL price_change 115,787,500 115,781,944 5,556 84 FULL tick_size_change 3,104 3,104 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 12,507,036 157,538 19ms 45ms 585ms 1.2min 0 transport_latency_assumed best_bid_ask i 12,503,860 129,368 22ms 43ms 199ms 11.7s 0 transport_latency_assumed best_bid_ask m 12,510,532 6,244,962 6ms 23ms 137ms 7.1s 0 transport_latency_assumed best_bid_ask n 12,488,535 7,060 46ms 80ms 480ms 22.2s 0 transport_latency_assumed best_bid_ask o 12,510,212 5,973,396 6ms 24ms 165ms 12.7s 0 transport_latency_assumed book h 163,297 15,944 29ms 2.0s 11.9h 113.2d 0 book_staleness book i 189,671 42,765 44ms 1.1h 29.8d 113.2d 0 book_staleness book m 167,854 94,036 9ms 5.7s 11.9h 113.2d 0 book_staleness book n 160,902 20,941 65ms 2.0min 5.1d 113.2d 0 book_staleness book o 166,001 82,883 10ms 2.7s 11.9h 113.2d 0 book_staleness last_trade_price h 72,778 1,027 23ms 184ms 1.7s 1.1min 0 transport_latency_assumed last_trade_price i 71,844 732 28ms 512ms 6.5s 11.7s 0 transport_latency_assumed last_trade_price m 73,288 37,520 8ms 31ms 200ms 3.8s 0 transport_latency_assumed last_trade_price n 68,102 41 57ms 1.7s 11.6s 22.2s 0 transport_latency_assumed last_trade_price o 73,235 34,091 8ms 37ms 267ms 3.3s 0 transport_latency_assumed market_resolved h 858 3 21ms 77ms 46.8s 48.6s 0 transport_latency_assumed market_resolved i 858 73 24ms 135ms 56.8s 56.8s 0 transport_latency_assumed market_resolved m 858 421 7ms 31ms 39.8s 40.9s 0 transport_latency_assumed market_resolved n 858 not meas. 48ms 186ms 55.0s 56.2s 0 transport_latency_assumed market_resolved o 858 387 7ms 29ms 38.4s 39.3s 0 transport_latency_assumed new_market h 1,862 488 190ms 40.6s 54.9s 64.2d 0 transport_latency_assumed new_market i 1,860 588 95ms 24.1s 51.1s 1.4min 0 transport_latency_assumed new_market m 1,860 996 57ms 32.2s 50.3s 1.6min 0 transport_latency_assumed new_market n 1,860 559 100ms 37.9s 52.5s 1.2min 0 transport_latency_assumed new_market o 1,860 550 108ms 31.2s 49.9s 1.6min 0 transport_latency_assumed price_change h 115,569,112 1,596,808 20ms 59ms 915ms 1.2min 0 transport_latency_assumed price_change i 115,452,300 1,269,848 22ms 60ms 1.5s 11.7s 0 transport_latency_assumed price_change m 115,749,134 59,054,252 6ms 26ms 151ms 7.7s 0 transport_latency_assumed price_change n 114,397,168 68,404 47ms 132ms 6.3s 22.2s 0 transport_latency_assumed price_change o 115,725,784 53,792,632 7ms 28ms 186ms 17.4s 0 transport_latency_assumed tick_size_change h 3,104 50 20ms 41ms 258ms 3.2s 0 transport_latency_assumed tick_size_change i 3,104 60 22ms 42ms 99ms 276ms 0 transport_latency_assumed tick_size_change m 3,104 1,517 6ms 27ms 99ms 154ms 0 transport_latency_assumed tick_size_change n 3,104 not meas. 46ms 67ms 140ms 347ms 0 transport_latency_assumed tick_size_change o 3,104 1,477 6ms 24ms 70ms 264ms 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/15/2026-10-08T15.parquet sha256sum 2026-10-08T15.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.