Hour audit: 2026-09-22T19
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-09-22T19 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-22T19:00:00.000013163+00:00 · last event 2026-09-22T19:59:59.999985286+00:00
VOLUME 119,728,978 rows · 1,350,604,403 bytes (1.26 GiB) · 7 products, all holding rows
WITNESSES cefhik — 6 machines contributed rows
captured h: 118,226,709 · e: 114,137,824 · f: 113,347,530 · c: 112,302,953 · i: 111,185,519 · k: 109,555,997 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 5,392,795 (4.50%) · e: 511,515 (0.43%) · f: 344,308 (0.29%) · c: 98,833,185 (82.55%) · i: 3,429,195 (2.86%) · k: 11,217,980 (9.37%) (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 119,728,978 rows exactly, so those pairs supplied none
6 expected, all 6 contributed
INTEGRITY sha256 eb4caca95f0ec2d08b5545b208050d92a158b7bd0feb64bbc602e5e4e9051710
the corpus checksum ledger names this file with the same digest
joined 119,730,224 to merged 119,728,978, minus 1,246 (minus 0.0010%)
boundary drops 1,246 · 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-09-22T22:04:18Z as cefhik
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 our incident register was checked against the venue's own status feed at 2026-09-23T20:35Z and names no event in this hour. That is a statement about what they published, not a check that every message they sent reached us.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,361,711 150,050,884 0-47 a46882966a2787e7641e94c0ba267c047fd2883bf0f6354f60ae75ce9b40ad8b book 1,636,134 89,086,826 48-54 3b47fb971c03ced41301432f3243473bf83daa286d7fb63448e81f935d6190fe last_trade_price 59,916 3,420,499 55-55 afe7cd871a7cdb8551afcd2fde1f502edee2cec955573663022ef9dea5e68fb0 market_resolved 1,055 148,189 56-56 7f2802c81fecbe77ef623640e387186cbf71dea14c520116128dcd9173f32e09 new_market 8,200 728,748 57-57 34ca22377b943937e245df18d4f8724e4b11728097b1951080be560cacf64347 price_change 105,657,030 1,105,620,267 58-461 888bb569b777ba2c89251dcbe8817d45c4f53516f2c7af4c87a6114b9c002edc tick_size_change 4,932 182,501 462-462 6a918b07961bb580f17e547ab65c3401b5de8c638f2878eb448d7b782e4c9c5c EVENT MIX count share price_change 105,657,030 88.25% best_bid_ask 12,361,711 10.32% book 1,636,134 1.37% last_trade_price 59,916 0.05% new_market 8,200 <0.01% tick_size_change 4,932 <0.01% market_resolved 1,055 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,361,863 12,361,711 152 2,970 FULL book 1,636,196 1,636,134 62 51,382 FULL last_trade_price 59,916 59,916 0 261 FULL market_resolved 1,055 1,055 0 21 FULL new_market 8,200 8,200 0 0 FULL price_change 105,658,062 105,657,030 1,032 1,228 FULL tick_size_change 4,932 4,932 0 154 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,716,905 10,398,329 6ms 22ms 244ms 6.8s 0 transport_latency_assumed best_bid_ask e 12,110,232 32,501 45ms 91ms 564ms 25.8s 0 transport_latency_assumed best_bid_ask f 11,827,478 14,732 49ms 84ms 454ms 21.0s 0 transport_latency_assumed best_bid_ask h 12,341,731 494,275 19ms 49ms 603ms 50.2s 0 transport_latency_assumed best_bid_ask i 11,622,671 357,056 21ms 43ms 295ms 13.2s 0 transport_latency_assumed best_bid_ask k 11,381,037 1,064,818 13ms 27ms 226ms 31.3s 0 transport_latency_assumed book c 672,399 493,132 3.8min 3.1d 41.0d 115.9d 0 book_staleness book e 492,795 182,130 2.7min 2.1d 38.2d 115.9d 0 book_staleness book f 654,317 188,161 3.9min 2.7d 41.0d 115.9d 0 book_staleness book h 533,258 206,480 2.8min 2.1d 38.3d 115.9d 0 book_staleness book i 498,855 141,051 3.0min 1.9d 38.0d 115.9d 0 book_staleness book k 978,987 425,180 5.4min 3.2d 42.0d 115.9d 0 book_staleness last_trade_price c 56,113 48,663 7ms 41ms 349ms 3.4s 0 transport_latency_assumed last_trade_price e 53,447 207 53ms 1.1s 12.4s 25.6s 0 transport_latency_assumed last_trade_price f 56,026 140 55ms 570ms 8.8s 21.1s 0 transport_latency_assumed last_trade_price h 58,858 3,045 20ms 150ms 1.2s 11.7s 0 transport_latency_assumed last_trade_price i 55,146 1,516 23ms 293ms 5.1s 13.0s 0 transport_latency_assumed last_trade_price k 54,359 6,345 14ms 64ms 458ms 10.1s 0 transport_latency_assumed market_resolved c 907 729 6ms 39.8s 4.4min 5.6min 0 transport_latency_assumed market_resolved e 905 60 46ms 499ms 1.0min 2.3min 0 transport_latency_assumed market_resolved f 924 20 50ms 815ms 5.4min 5.5min 0 transport_latency_assumed market_resolved h 908 31 19ms 165ms 1.0min 1.0min 0 transport_latency_assumed market_resolved i 902 75 22ms 35.5s 3.7min 4.6min 0 transport_latency_assumed market_resolved k 943 140 14ms 3.8min 8.9min 9.0min 0 transport_latency_assumed new_market c 4,501 2,075 102ms 47.3s 16.7min 31.5min 0 transport_latency_assumed new_market e 4,428 649 210ms 28.8s 16.6min 31.4min 0 transport_latency_assumed new_market f 4,474 491 229ms 1.1min 16.4min 31.4min 0 transport_latency_assumed new_market h 4,428 1,243 164ms 27.3s 16.1min 31.4min 0 transport_latency_assumed new_market i 4,517 1,307 161ms 1.7min 16.5min 31.5min 0 transport_latency_assumed new_market k 5,945 2,435 192ms 5.0min 6.4min 31.4min 0 transport_latency_assumed price_change c 99,847,368 87,885,974 6ms 27ms 262ms 6.8s 0 transport_latency_assumed price_change e 101,471,157 295,956 46ms 144ms 4.0s 26.1s 0 transport_latency_assumed price_change f 100,799,503 140,764 50ms 122ms 1.7s 21.1s 0 transport_latency_assumed price_change h 105,282,598 4,687,624 19ms 60ms 724ms 1.1min 0 transport_latency_assumed price_change i 98,998,824 2,928,098 21ms 61ms 1.7s 13.2s 0 transport_latency_assumed price_change k 97,129,950 9,718,614 13ms 32ms 251ms 33.9s 0 transport_latency_assumed tick_size_change c 4,760 4,283 6ms 15ms 194ms 537ms 0 transport_latency_assumed tick_size_change e 4,860 12 45ms 73ms 381ms 7.1s 0 transport_latency_assumed tick_size_change f 4,808 not meas. 49ms 77ms 231ms 727ms 0 transport_latency_assumed tick_size_change h 4,928 97 18ms 39ms 327ms 3.5s 0 transport_latency_assumed tick_size_change i 4,604 92 21ms 42ms 197ms 7.5s 0 transport_latency_assumed tick_size_change k 4,776 448 13ms 26ms 1.4s 2.3s 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-09-22/19/2026-09-22T19.parquet sha256sum 2026-09-22T19.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.