Hour audit: 2026-09-25T04
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-25T04 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-25T04:00:00.000153106+00:00 · last event 2026-09-25T04:59:59.999973447+00:00
VOLUME 108,907,308 rows · 1,200,622,282 bytes (1.12 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured h: 107,493,213 · i: 102,518,851 · g: 101,933,363 · k: 97,641,935 · c: 97,557,383 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 5,523,012 (5.07%) · i: 5,907,263 (5.42%) · g: 141,905 (0.13%) · k: 12,961,848 (11.90%) · c: 84,373,280 (77.47%) (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 108,907,308 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 3f356004551790583a8f26fc61d205d7e2b9a9d9dce8925145a4fbc067f8461d
the corpus checksum ledger names this file with the same digest
joined 108,909,684 to merged 108,907,308, minus 2,376 (minus 0.0022%)
boundary drops 2,376 · 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-25T06:28:10Z 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,222,552 155,998,330 0-50 72c70947044368de051d73aaf425754e7e232553c7c7075189c2f2344dd0eb74 book 1,490,012 81,197,600 51-56 4ee6e860399dffef31766b439a91c7354bef32d864554fcefcf1372126d2eb81 last_trade_price 42,038 2,442,750 57-57 b7f3ce26cf37f2bbbcb2a8b9378d13be855d67f5e14bc39d991c28dc3870da07 market_resolved 1,963 244,052 58-58 26a8514db580299a3b260a1d1e5e3fd885510a2bfd0898663f845a3804af7840 new_market 12,151 1,151,849 59-59 62a8c4e9875a95d981df555861b8e3d63d0a1ea3abc5346730e337ad22661582 price_change 94,134,328 958,190,423 60-419 1ef468c8541bf3ee4bdabf3502479bd66ec05dd26e5ee8b11d8d8ba399a78e41 tick_size_change 4,264 155,777 420-420 4b1f352cd59f4e4e8f8caded37c6340c60365107b5da1800ca0579b60b1abe10 EVENT MIX count share price_change 94,134,328 86.44% best_bid_ask 13,222,552 12.14% book 1,490,012 1.37% last_trade_price 42,038 0.04% new_market 12,151 0.01% tick_size_change 4,264 <0.01% market_resolved 1,963 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,222,806 13,222,552 254 1,977 FULL book 1,490,206 1,490,012 194 188,279 FULL last_trade_price 42,038 42,038 0 279 FULL market_resolved 1,963 1,963 0 121 FULL new_market 12,151 12,151 0 0 FULL price_change 94,136,256 94,134,328 1,928 751 FULL tick_size_change 4,264 4,264 0 75 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,963,824 10,451,550 5ms 36ms 376ms 12.3s 0 transport_latency_assumed best_bid_ask g 12,554,206 5,231 81ms 228ms 887ms 42.8s 0 transport_latency_assumed best_bid_ask h 13,220,230 619,935 18ms 67ms 1.6s 59.6s 0 transport_latency_assumed best_bid_ask i 12,611,371 665,988 21ms 38ms 210ms 2.9s 0 transport_latency_assumed best_bid_ask k 12,059,896 1,479,848 12ms 33ms 344ms 49.4s 0 transport_latency_assumed book c 958,225 859,794 5.6min 4.5d 40.8d 118.2d 0 book_staleness book g 538,333 92,565 4.7min 3.5d 39.4d 118.2d 0 book_staleness book h 128,360 32,821 48ms 26.7min 17.7d 99.8d 0 book_staleness book i 550,284 164,189 4.8min 3.4d 35.9d 118.2d 0 book_staleness book k 939,351 340,643 5.5min 4.3d 43.1d 118.2d 0 book_staleness last_trade_price c 37,647 30,900 6ms 95ms 638ms 3.8s 0 transport_latency_assumed last_trade_price g 35,775 12 96ms 2.3s 18.2s 42.9s 0 transport_latency_assumed last_trade_price h 41,854 2,777 20ms 182ms 1.7s 50.6s 0 transport_latency_assumed last_trade_price i 39,507 2,725 24ms 125ms 467ms 1.8s 0 transport_latency_assumed last_trade_price k 36,314 5,624 14ms 77ms 445ms 6.6s 0 transport_latency_assumed market_resolved c 1,539 1,312 5ms 7.8min 11.3min 11.4min 0 transport_latency_assumed market_resolved g 1,405 191 86ms 28.4s 48.4s 5.6min 0 transport_latency_assumed market_resolved h 1,501 79 18ms 24.4s 53.9s 54.4s 0 transport_latency_assumed market_resolved i 1,479 88 21ms 26.4s 55.6s 5.8min 0 transport_latency_assumed market_resolved k 1,615 293 13ms 6.6min 12.3min 12.7min 0 transport_latency_assumed new_market c 8,298 2,962 295ms 39.9min 42.2min 43.4min 0 transport_latency_assumed new_market g 7,321 802 372ms 40.1min 42.2min 43.4min 0 transport_latency_assumed new_market h 7,268 1,688 204ms 40.1min 42.2min 43.4min 0 transport_latency_assumed new_market i 7,415 3,167 158ms 40.1min 42.2min 43.4min 0 transport_latency_assumed new_market k 8,531 3,532 287ms 40.0min 42.2min 43.4min 0 transport_latency_assumed price_change c 84,583,654 73,023,038 5ms 46ms 411ms 12.4s 0 transport_latency_assumed price_change g 88,792,103 43,104 82ms 317ms 5.8s 45.6s 0 transport_latency_assumed price_change h 94,089,736 4,865,586 18ms 82ms 1.4s 1.0min 0 transport_latency_assumed price_change i 89,304,603 5,070,970 21ms 48ms 260ms 3.6s 0 transport_latency_assumed price_change k 84,592,180 11,131,630 12ms 41ms 372ms 53.6s 0 transport_latency_assumed tick_size_change c 4,196 3,724 5ms 20ms 323ms 5.7s 0 transport_latency_assumed tick_size_change g 4,220 not meas. 80ms 127ms 592ms 1.4s 0 transport_latency_assumed tick_size_change h 4,264 126 18ms 39ms 1.2s 8.3s 0 transport_latency_assumed tick_size_change i 4,192 136 21ms 28ms 136ms 247ms 0 transport_latency_assumed tick_size_change k 4,048 278 12ms 24ms 239ms 662ms 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-25/04/2026-09-25T04.parquet sha256sum 2026-09-25T04.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.