Hour audit: 2026-10-09T14
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-09T14 · corpus v3 · verdict AUDIT PENDING
COVERAGE not measured (this hour is not in the corpus attestation, so we have not looked at it)
VOLUME 134,197,507 rows · 1,641,715,931 bytes (1.53 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured h: 133,039,857 · m: 133,011,341 · o: 132,902,107 · i: 132,576,104 · n: 132,273,302 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 2,091,186 (1.56%) · m: 67,614,115 (50.38%) · o: 62,899,566 (46.87%) · i: 1,197,602 (0.89%) · n: 395,038 (0.29%) (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 134,197,507 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 5199d320d7342451c09e91ee0214dbd229fd0aafab1a2362d1496954dadba0b3
no line in the corpus checksum ledger names this file
joined 134,208,636 to merged 134,197,507, minus 11,129 (minus 0.0083%)
boundary drops 11,129 · 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-10T04:16:58Z 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,608,372 163,446,247 0-48 4d24be2fee832970eba1d2bc3e9af2b899cf792c96be7aae185808bae0001713 book 2,014,309 121,663,133 49-56 5f0e2536f3352ed6f9903205ad4af51539a82b2a288f16138aea7843545c95aa last_trade_price 63,268 3,744,194 57-57 c13deb2405c3cb43c1fb6778549a21fd05712de400d65d5aecb7f482496f68ef market_resolved 613 101,231 58-58 f9fa5662397aaae2bfed3a59ea89518256cac1a097bd9a14a686da0593f38ea3 new_market 1,193 128,316 59-59 f955fcc7678186e84f3d2ab55f30771fac0966e1a5e88617463ab1f82b976dda price_change 119,504,848 1,350,923,104 60-515 1e96e00a25939d4698410417d46d2185317594a78a7a4fa02ddbc4c793aee067 tick_size_change 4,904 182,732 516-516 f051d50e1f3574724a2a71c9a5bc626e110fc8b4de62d3fd9f804e9daccd10cb EVENT MIX count share price_change 119,504,848 89.05% best_bid_ask 12,608,372 9.40% book 2,014,309 1.50% last_trade_price 63,268 0.05% tick_size_change 4,904 <0.01% new_market 1,193 <0.01% market_resolved 613 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,608,534 12,608,372 162 60 FULL book 2,022,726 2,014,309 8,417 170,847 FULL last_trade_price 63,268 63,268 0 1 FULL market_resolved 613 613 0 11 FULL new_market 1,193 1,193 0 0 FULL price_change 119,507,398 119,504,848 2,550 232 FULL tick_size_change 4,904 4,904 0 3 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 12,601,883 143,815 19ms 41ms 296ms 57.7s 0 transport_latency_assumed best_bid_ask i 12,604,017 94,346 22ms 41ms 201ms 4.4s 0 transport_latency_assumed best_bid_ask m 12,604,283 6,389,586 6ms 22ms 157ms 7.4s 0 transport_latency_assumed best_bid_ask n 12,598,049 4,249 46ms 74ms 366ms 27.1s 0 transport_latency_assumed best_bid_ask o 12,604,047 5,976,376 6ms 22ms 168ms 25.5s 0 transport_latency_assumed book h 1,012,264 544,437 12.0min 1.4d 48.0d 132.7d 0 book_staleness book i 548,815 199,111 5.4min 1.4d 48.0d 132.7d 0 book_staleness book m 931,556 521,615 10.8min 1.4d 48.0d 132.7d 0 book_staleness book n 738,455 335,246 8.4min 1.4d 48.0d 132.7d 0 book_staleness book o 843,486 413,900 10.1min 1.4d 48.0d 132.7d 0 book_staleness last_trade_price h 62,975 596 21ms 153ms 917ms 12.9s 0 transport_latency_assumed last_trade_price i 63,053 349 27ms 281ms 1.7s 4.4s 0 transport_latency_assumed last_trade_price m 63,143 33,263 7ms 26ms 176ms 7.4s 0 transport_latency_assumed last_trade_price n 61,644 44 59ms 1.7s 11.6s 26.8s 0 transport_latency_assumed last_trade_price o 63,143 29,016 7ms 31ms 218ms 2.8s 0 transport_latency_assumed market_resolved h 599 2 23ms 101ms 45.3s 52.5s 0 transport_latency_assumed market_resolved i 599 34 28ms 134ms 33.2s 56.5s 0 transport_latency_assumed market_resolved m 599 293 6ms 34ms 35.8s 44.0s 0 transport_latency_assumed market_resolved n 588 10 49ms 209ms 479ms 56.3s 0 transport_latency_assumed market_resolved o 599 274 6ms 39ms 46.1s 52.5s 0 transport_latency_assumed new_market h 826 100 147ms 13.0s 1.7min 2.2min 0 transport_latency_assumed new_market i 826 201 98ms 12.8s 1.6min 2.2min 0 transport_latency_assumed new_market m 826 413 57ms 15.1s 1.7min 2.2min 0 transport_latency_assumed new_market n 826 51 203ms 40.5s 2.0min 2.3min 0 transport_latency_assumed new_market o 826 428 71ms 30.9s 1.9min 2.2min 0 transport_latency_assumed price_change h 119,356,406 1,402,132 19ms 53ms 540ms 60.0s 0 transport_latency_assumed price_change i 119,353,894 903,500 22ms 60ms 652ms 4.5s 0 transport_latency_assumed price_change m 119,406,030 60,666,456 6ms 25ms 192ms 7.8s 0 transport_latency_assumed price_change n 118,868,836 55,438 46ms 129ms 4.8s 27.1s 0 transport_latency_assumed price_change o 119,385,110 56,477,322 6ms 26ms 202ms 25.5s 0 transport_latency_assumed tick_size_change h 4,904 104 19ms 44ms 267ms 7.3s 0 transport_latency_assumed tick_size_change i 4,900 61 22ms 48ms 188ms 601ms 0 transport_latency_assumed tick_size_change m 4,904 2,489 6ms 24ms 153ms 468ms 0 transport_latency_assumed tick_size_change n 4,904 not meas. 46ms 78ms 371ms 1.9s 0 transport_latency_assumed tick_size_change o 4,896 2,250 6ms 29ms 176ms 501ms 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-09/14/2026-10-09T14.parquet sha256sum 2026-10-09T14.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.