Hour audit: 2026-09-24T14
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-24T14 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-24T14:00:00.000006629+00:00 · last event 2026-09-24T14:59:59.999936215+00:00
VOLUME 132,106,982 rows · 1,477,281,124 bytes (1.38 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured i: 125,623,702 · h: 125,270,870 · g: 123,788,936 · k: 120,853,554 · c: 114,542,959 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 5,008,977 (3.79%) · h: 4,367,242 (3.31%) · g: 122,277 (0.09%) · k: 21,167,526 (16.02%) · c: 101,440,960 (76.79%) (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 132,106,982 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 dc6ea96a333510b693aa1c7e6f364f45a9792dd8afe088a7e0b8c2c0dcbfff21
the corpus checksum ledger names this file with the same digest
joined 132,109,857 to merged 132,106,982, minus 2,875 (minus 0.0022%)
boundary drops 2,875 · 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-24T16:49:09Z 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 13,005,726 155,393,357 0-49 6386bb4d120c4ff66e30980a3519be95e5dc0ec06e38cf1e6847d948be08452b book 1,748,867 91,182,631 50-56 1aa9f1caccdf3696521a9b128258cbfdd2c702f98091c400d0a0e5f0236e5466 last_trade_price 63,236 3,643,282 57-57 0454ceb593808f3664a6c9efc5e2d01e468cf842f017d4ecd128e6e35e18e8d5 market_resolved 1,353 161,726 58-58 728272d80dcf212824d8af05e992beb065b031861a684309f09e50cb8b7177e4 new_market 1,872 187,884 59-59 602351996bde561e49c1539e33d0027071e5ceabc8b69a622705a4325869c244 price_change 117,283,264 1,225,112,738 60-507 4f1a58dde8d766409fc5d66b388848ab8329c9cc9ee78bbc1064e9a33db90095 tick_size_change 2,664 98,227 508-508 d3138278c1b512fc5595d97ca21405f33602933330bdb2836146b1c30e03decb EVENT MIX count share price_change 117,283,264 88.78% best_bid_ask 13,005,726 9.84% book 1,748,867 1.32% last_trade_price 63,236 0.05% tick_size_change 2,664 <0.01% new_market 1,872 <0.01% market_resolved 1,353 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,006,024 13,005,726 298 3,009 FULL book 1,748,877 1,748,867 10 2,240 FULL last_trade_price 63,237 63,236 1 643 FULL market_resolved 1,353 1,353 0 206 FULL new_market 1,872 1,872 0 0 FULL price_change 117,285,830 117,283,264 2,566 1,137 FULL tick_size_change 2,664 2,664 0 178 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,320,455 10,115,811 6ms 17ms 154ms 4.5s 0 transport_latency_assumed best_bid_ask g 12,452,828 1,378 81ms 115ms 683ms 40.4s 0 transport_latency_assumed best_bid_ask h 12,500,231 415,491 19ms 48ms 201ms 18.8s 0 transport_latency_assumed best_bid_ask i 12,501,226 465,290 21ms 30ms 127ms 4.1s 0 transport_latency_assumed best_bid_ask k 11,990,751 2,007,756 13ms 22ms 103ms 5.8s 0 transport_latency_assumed book c 1,291,942 955,920 7.9min 5.0d 43.0d 117.7d 0 book_staleness book g 520,966 108,600 5.3min 2.9d 35.3d 117.7d 0 book_staleness book h 514,888 124,482 4.4min 2.8d 33.0d 117.7d 0 book_staleness book i 514,862 143,606 3.6min 2.8d 33.0d 117.7d 0 book_staleness book k 900,030 416,259 5.8min 3.9d 42.8d 117.7d 0 book_staleness last_trade_price c 54,763 48,036 7ms 25ms 232ms 2.3s 0 transport_latency_assumed last_trade_price g 55,730 13 91ms 1.9s 17.5s 39.9s 0 transport_latency_assumed last_trade_price h 59,689 1,825 21ms 77ms 452ms 6.1s 0 transport_latency_assumed last_trade_price i 60,586 2,451 23ms 100ms 763ms 4.0s 0 transport_latency_assumed last_trade_price k 57,866 10,911 14ms 38ms 208ms 1.3s 0 transport_latency_assumed market_resolved c 889 773 6ms 192ms 5.7min 6.2min 0 transport_latency_assumed market_resolved g 994 127 88ms 4.8min 5.7min 6.2min 0 transport_latency_assumed market_resolved h 1,058 49 22ms 7.2min 8.5min 9.0min 0 transport_latency_assumed market_resolved i 947 147 21ms 168ms 4.4min 5.4min 0 transport_latency_assumed market_resolved k 946 257 14ms 8.1min 9.5min 9.5min 0 transport_latency_assumed new_market c 1,243 642 87ms 20.7s 1.5min 5.3min 0 transport_latency_assumed new_market g 1,245 115 288ms 24.6s 3.9min 3.9min 0 transport_latency_assumed new_market h 1,271 244 164ms 23.6s 6.7min 6.7min 0 transport_latency_assumed new_market i 1,241 294 116ms 20.8s 1.1min 1.7min 0 transport_latency_assumed new_market k 1,258 577 88ms 26.4s 5.8min 9.2min 0 transport_latency_assumed price_change c 101,871,343 90,317,704 6ms 20ms 172ms 4.9s 0 transport_latency_assumed price_change g 110,754,741 12,044 82ms 179ms 8.2s 40.4s 0 transport_latency_assumed price_change h 112,191,125 3,825,041 19ms 54ms 262ms 19.6s 0 transport_latency_assumed price_change i 112,542,336 4,397,062 21ms 38ms 218ms 4.2s 0 transport_latency_assumed price_change k 107,900,319 18,731,413 13ms 25ms 121ms 7.6s 0 transport_latency_assumed tick_size_change c 2,324 2,074 6ms 16ms 105ms 215ms 0 transport_latency_assumed tick_size_change g 2,432 not meas. 79ms 98ms 264ms 617ms 0 transport_latency_assumed tick_size_change h 2,608 110 19ms 45ms 123ms 342ms 0 transport_latency_assumed tick_size_change i 2,504 127 21ms 29ms 91ms 219ms 0 transport_latency_assumed tick_size_change k 2,384 353 13ms 22ms 90ms 286ms 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-24/14/2026-09-24T14.parquet sha256sum 2026-09-24T14.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.