Hour audit: 2026-09-24T16
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-24T16 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-24T16:00:00.000006749+00:00 · last event 2026-09-24T16:59:59.999948311+00:00
VOLUME 124,505,789 rows · 1,380,188,162 bytes (1.29 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured i: 123,317,817 · h: 123,175,433 · g: 122,606,204 · k: 118,261,398 · c: 113,904,258 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 1,165,860 (0.94%) · h: 2,352,071 (1.89%) · g: 157,855 (0.13%) · k: 18,573,557 (14.92%) · c: 102,256,446 (82.13%) (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 124,505,789 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 da613b6fe0d540a830d691dd2a5e11ae592162a11ed25da03af630f44149f284
the corpus checksum ledger names this file with the same digest
joined 124,513,699 to merged 124,505,789, minus 7,910 (minus 0.0064%)
boundary drops 7,910 · 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-24T18:55:30Z 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 12,627,103 150,223,939 0-48 32871d08ca312b36c4bd14c1ecc8227392ade10d6ac2e35dc4fb8230e241feae book 1,737,816 93,732,416 49-55 2c2d7f79a1c3815fe48328232699d01ba882ad350b624ec97c4de4db0252b32d last_trade_price 62,966 3,674,605 56-56 3e3e7107cddc5e6770a67da0df6f3aa6e039a3a80c92ddd736c9bae8d5994ba1 market_resolved 1,222 179,518 57-57 02745072de2a29122eb5eba4d8b2fd2ec735f41de488f31e55a81401cb9c915a new_market 1,354 142,355 58-58 a9b821cc343d1bb89b3f51071a539f106a3b9619299b0628ea4f671499b7a795 price_change 110,072,740 1,130,722,999 59-478 16a43c7091434ec74aa7a257f51873508808b00e09af6f8b06d7b2a701207de2 tick_size_change 2,588 95,901 479-479 17389c497f022da22b351bb7b5f5cd6fb45beb1e27dfe40a92ba30745ceea9c8 EVENT MIX count share price_change 110,072,740 88.41% best_bid_ask 12,627,103 10.14% book 1,737,816 1.40% last_trade_price 62,966 0.05% tick_size_change 2,588 <0.01% new_market 1,354 <0.01% market_resolved 1,222 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,627,313 12,627,103 210 1,912 FULL book 1,743,658 1,737,816 5,842 102,020 FULL last_trade_price 62,966 62,966 0 348 FULL market_resolved 1,222 1,222 0 31 FULL new_market 1,354 1,354 0 0 FULL price_change 110,074,598 110,072,740 1,858 1,230 FULL tick_size_change 2,588 2,588 0 50 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,562,116 10,458,929 6ms 16ms 116ms 3.0s 0 transport_latency_assumed best_bid_ask g 12,613,144 356 82ms 109ms 464ms 31.7s 0 transport_latency_assumed best_bid_ask h 12,622,815 211,292 19ms 30ms 133ms 13.0s 0 transport_latency_assumed best_bid_ask i 12,621,977 90,690 21ms 31ms 122ms 7.8s 0 transport_latency_assumed best_bid_ask k 12,108,976 1,865,836 13ms 20ms 82ms 3.0s 0 transport_latency_assumed book c 1,104,590 811,713 7.4min 4.8d 42.9d 117.8d 0 book_staleness book g 421,942 154,453 1.8min 2.8d 33.1d 117.8d 0 book_staleness book h 449,238 169,889 2.0min 2.8d 33.1d 117.7d 0 book_staleness book i 623,331 249,262 3.6min 3.0d 35.8d 117.8d 0 book_staleness book k 750,032 352,499 5.7min 3.5d 40.1d 117.8d 0 book_staleness last_trade_price c 57,919 51,309 7ms 23ms 195ms 1.5s 0 transport_latency_assumed last_trade_price g 60,559 3 95ms 1.4s 16.5s 31.8s 0 transport_latency_assumed last_trade_price h 62,940 1,373 20ms 49ms 251ms 4.2s 0 transport_latency_assumed last_trade_price i 62,711 389 24ms 95ms 1.0s 6.9s 0 transport_latency_assumed last_trade_price k 60,349 9,892 14ms 30ms 167ms 1.5s 0 transport_latency_assumed market_resolved c 1,077 955 6ms 257ms 5.0min 5.1min 0 transport_latency_assumed market_resolved g 1,107 not meas. 90ms 368ms 28.3s 33.6s 0 transport_latency_assumed market_resolved h 1,107 59 20ms 92ms 23.2s 57.9s 0 transport_latency_assumed market_resolved i 1,107 4 24ms 129ms 44.2s 48.7s 0 transport_latency_assumed market_resolved k 1,106 204 15ms 67ms 4.9min 5.0min 0 transport_latency_assumed new_market c 930 423 66ms 11.6s 1.6min 4.3min 0 transport_latency_assumed new_market g 930 99 257ms 10.6s 1.6min 1.9min 0 transport_latency_assumed new_market h 930 246 84ms 12.3s 1.6min 2.3min 0 transport_latency_assumed new_market i 930 202 90ms 10.7s 1.6min 1.9min 0 transport_latency_assumed new_market k 930 384 56ms 197ms 33.1s 1.6min 0 transport_latency_assumed price_change c 101,175,182 90,930,992 6ms 18ms 126ms 3.6s 0 transport_latency_assumed price_change g 109,505,934 2,944 83ms 147ms 3.6s 31.9s 0 transport_latency_assumed price_change h 110,035,815 1,969,162 19ms 34ms 154ms 13.1s 0 transport_latency_assumed price_change i 110,005,173 825,272 22ms 37ms 197ms 8.0s 0 transport_latency_assumed price_change k 105,337,473 16,344,370 13ms 22ms 93ms 3.6s 0 transport_latency_assumed tick_size_change c 2,444 2,125 6ms 21ms 121ms 279ms 0 transport_latency_assumed tick_size_change g 2,588 not meas. 81ms 105ms 445ms 891ms 0 transport_latency_assumed tick_size_change h 2,588 50 19ms 34ms 105ms 2.1s 0 transport_latency_assumed tick_size_change i 2,588 41 21ms 36ms 149ms 773ms 0 transport_latency_assumed tick_size_change k 2,532 372 13ms 20ms 90ms 206ms 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/16/2026-09-24T16.parquet sha256sum 2026-09-24T16.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.