Hour audit: 2026-09-23T22
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-23T22 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-23T22:00:00.000010096+00:00 · last event 2026-09-23T22:59:59.999968543+00:00
VOLUME 111,575,054 rows · 1,191,589,019 bytes (1.11 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured i: 110,329,684 · k: 110,316,888 · h: 110,272,889 · g: 110,137,917 · c: 96,551,950 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 1,375,221 (1.23%) · k: 20,115,769 (18.03%) · h: 2,020,100 (1.81%) · g: 17,092 (0.02%) · c: 88,046,872 (78.91%) (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 111,575,054 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 5950b97d41e235f9a9ba2ad69012d6ad5a55ae799028a27c3c56b1c2e2bf0c8e
the corpus checksum ledger names this file with the same digest
joined 111,577,405 to merged 111,575,054, minus 2,351 (minus 0.0021%)
boundary drops 2,351 · 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-24T06:03:36Z as cghik
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 10,712,866 125,884,497 0-40 94540adc17469b085b234e4de0e35589db8f3136cb6c82aa10a972b3900c6aa2 book 1,317,284 71,000,841 41-46 fd1f0fdc626ae7dfdbe789fe96952610be80561890df3c280791f0ac14aec350 last_trade_price 47,388 2,736,475 47-47 4e71bd73b51fb00fcd997bc0996f68cd0036757f9512932f97e918fb13d7e50b market_resolved 1,445 218,407 48-48 4141162f8dd43f88122fb3b5568a732e64bbad336921e7b3e13731bc79a570a0 new_market 1,907 193,502 49-49 da6319f0ab2161e8b90a95743f02be8f2e6b47dd6051b9d0f1372939cfba2fa3 price_change 99,491,020 990,167,294 50-429 033d6fa8e865515006da20f60abd2f37daa85913904ec1f080eb4e991dcac1eb tick_size_change 3,144 115,488 430-430 7462b7f5fa2c16717abb1f0ff5307ae2bec02dbd84ae788749900a58a27e4235 EVENT MIX count share price_change 99,491,020 89.17% best_bid_ask 10,712,866 9.60% book 1,317,284 1.18% last_trade_price 47,388 0.04% tick_size_change 3,144 <0.01% new_market 1,907 <0.01% market_resolved 1,445 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,713,122 10,712,866 256 1,359 FULL book 1,317,332 1,317,284 48 196,593 FULL last_trade_price 47,389 47,388 1 210 FULL market_resolved 1,445 1,445 0 9 FULL new_market 1,907 1,907 0 0 FULL price_change 99,493,066 99,491,020 2,046 711 FULL tick_size_change 3,144 3,144 0 58 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,276,880 8,491,692 5ms 14ms 150ms 6.1s 0 transport_latency_assumed best_bid_ask g 10,707,344 861 81ms 115ms 503ms 16.8s 0 transport_latency_assumed best_bid_ask h 10,710,042 188,126 18ms 35ms 212ms 31.3s 0 transport_latency_assumed best_bid_ask i 10,710,615 131,969 21ms 30ms 136ms 2.1s 0 transport_latency_assumed best_bid_ask k 10,711,275 1,900,218 12ms 19ms 109ms 10.8s 0 transport_latency_assumed book c 1,285,104 1,262,000 9.2min 4.3d 42.3d 117.0d 0 book_staleness book g 101,679 4,119 93ms 4.0s 2.1d 109.3d 0 book_staleness book h 110,097 10,205 25ms 36.4s 5.3d 98.5d 0 book_staleness book i 131,960 19,463 43ms 25.5min 17.7d 98.5d 0 book_staleness book k 102,828 21,497 15ms 153ms 2.1d 98.5d 0 book_staleness last_trade_price c 41,530 37,125 6ms 27ms 213ms 5.6s 0 transport_latency_assumed last_trade_price g 46,510 70 93ms 880ms 9.3s 16.9s 0 transport_latency_assumed last_trade_price h 47,036 705 20ms 135ms 625ms 8.9s 0 transport_latency_assumed last_trade_price i 47,095 450 25ms 209ms 967ms 2.0s 0 transport_latency_assumed last_trade_price k 47,131 9,038 13ms 38ms 229ms 3.0s 0 transport_latency_assumed market_resolved c 1,359 1,194 5ms 41.1s 5.7min 6.0min 0 transport_latency_assumed market_resolved g 1,353 not meas. 84ms 19.4s 57.5s 58.1s 0 transport_latency_assumed market_resolved h 1,353 11 18ms 12.6s 50.3s 55.7s 0 transport_latency_assumed market_resolved i 1,353 144 23ms 12.6s 49.8s 55.3s 0 transport_latency_assumed market_resolved k 1,353 96 13ms 16.8s 59.4s 1.0min 0 transport_latency_assumed new_market c 1,262 500 100ms 43.4s 4.5min 6.3min 0 transport_latency_assumed new_market g 1,251 124 257ms 15.1s 2.4min 3.4min 0 transport_latency_assumed new_market h 1,251 463 111ms 12.9s 2.9min 3.4min 0 transport_latency_assumed new_market i 1,251 467 94ms 13.0s 2.7min 3.6min 0 transport_latency_assumed new_market k 1,251 353 104ms 14.1s 2.5min 3.6min 0 transport_latency_assumed price_change c 85,942,903 78,251,647 5ms 16ms 159ms 6.1s 0 transport_latency_assumed price_change g 99,276,636 11,918 82ms 159ms 2.6s 16.9s 0 transport_latency_assumed price_change h 99,399,966 1,820,534 18ms 42ms 282ms 31.7s 0 transport_latency_assumed price_change i 99,434,266 1,222,692 22ms 40ms 255ms 4.0s 0 transport_latency_assumed price_change k 99,449,906 18,184,229 12ms 22ms 126ms 11.3s 0 transport_latency_assumed tick_size_change c 2,912 2,714 4ms 12ms 52ms 226ms 0 transport_latency_assumed tick_size_change g 3,144 not meas. 81ms 99ms 248ms 618ms 0 transport_latency_assumed tick_size_change h 3,144 56 18ms 34ms 118ms 3.6s 0 transport_latency_assumed tick_size_change i 3,144 36 21ms 29ms 83ms 276ms 0 transport_latency_assumed tick_size_change k 3,144 338 12ms 20ms 92ms 166ms 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-23/22/2026-09-23T22.parquet sha256sum 2026-09-23T22.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.