Hour audit: 2026-09-25T07
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-25T07 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-25T07:00:00.000181921+00:00 · last event 2026-09-25T07:59:59.999934490+00:00
VOLUME 118,255,055 rows · 1,262,709,639 bytes (1.18 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured i: 117,037,647 · g: 117,017,185 · c: 112,545,053 · h: 112,398,007 · k: 107,844,929 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 1,253,268 (1.06%) · g: 10,220 (0.01%) · c: 105,355,651 (89.09%) · h: 1,774,700 (1.50%) · k: 9,861,216 (8.34%) (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 118,255,055 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 5a4d416740e78c784eedb67c9a3caa39178a596c0741a93b21e78d226120e19f
the corpus checksum ledger names this file with the same digest
joined 118,257,309 to merged 118,255,055, minus 2,254 (minus 0.0019%)
boundary drops 2,254 · 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-25T09:40:13Z 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,598,902 154,540,267 0-51 1d92c12ffd901b5de3b9da901ff38ef340a0e59fd9d3a0c4a760172c79bc411d book 1,279,242 76,859,637 52-56 f9b1da66d101309cc6fe78e1a76f980bd2103d19066d539629f746e2b051d554 last_trade_price 47,614 2,707,657 57-57 05b03a21eed60337da95f0d64f8338db70bc5119b9644e563809618940e631f8 market_resolved 704 83,421 58-58 f0696391f9ea628ec9a4ffeaa8c4c54020075cf5fee7775911f87439ba0748ab new_market 1,233 118,715 59-59 5dc96aaec543700b254ba06982bed7242664945027c1fb67e4a56b87a96beea5 price_change 103,325,432 1,026,982,695 60-454 ec0efa1928805339fd3e717dfc844ae9c99f1b674f721a7a4d3f90a1edaa3a3c tick_size_change 1,928 71,940 455-455 844e01789f4c0f28e47caa15974b5134e5f43a60ea4a23c04f559ed2daa47810 EVENT MIX count share price_change 103,325,432 87.38% best_bid_ask 13,598,902 11.50% book 1,279,242 1.08% last_trade_price 47,614 0.04% tick_size_change 1,928 <0.01% new_market 1,233 <0.01% market_resolved 704 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,599,138 13,598,902 236 1,169 FULL book 1,279,266 1,279,242 24 207,035 FULL last_trade_price 47,614 47,614 0 200 FULL market_resolved 704 704 0 6 FULL new_market 1,233 1,233 0 0 FULL price_change 103,327,426 103,325,432 1,994 355 FULL tick_size_change 1,928 1,928 0 99 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 12,995,958 12,247,845 4ms 10ms 101ms 6.0s 0 transport_latency_assumed best_bid_ask g 13,596,510 588 79ms 97ms 287ms 13.0s 0 transport_latency_assumed best_bid_ask h 13,016,764 169,516 18ms 34ms 143ms 1.5min 0 transport_latency_assumed best_bid_ask i 13,597,266 137,168 22ms 27ms 95ms 4.3s 0 transport_latency_assumed best_bid_ask k 12,414,434 1,043,785 14ms 19ms 87ms 8.5s 0 transport_latency_assumed book c 518,358 331,030 5.2min 3.6d 33.8d 118.4d 0 book_staleness book g 104,418 3,976 85ms 1.8s 3.5d 99.8d 0 book_staleness book h 514,510 147,250 6.8min 3.5d 33.8d 118.4d 0 book_staleness book i 99,540 2,990 24ms 104ms 39.5min 99.9d 0 book_staleness book k 925,710 793,996 10.2min 4.1d 40.9d 118.4d 0 book_staleness last_trade_price c 45,390 41,644 5ms 20ms 185ms 1.4s 0 transport_latency_assumed last_trade_price g 47,328 21 84ms 259ms 3.3s 13.0s 0 transport_latency_assumed last_trade_price h 45,326 1,023 20ms 54ms 288ms 20.7s 0 transport_latency_assumed last_trade_price i 47,378 532 24ms 61ms 425ms 3.9s 0 transport_latency_assumed last_trade_price k 42,961 4,394 15ms 34ms 198ms 7.3s 0 transport_latency_assumed market_resolved c 497 411 5ms 43.5s 5.3min 5.3min 0 transport_latency_assumed market_resolved g 497 not meas. 92ms 37.4s 52.1s 55.9s 0 transport_latency_assumed market_resolved h 497 32 32ms 54.2s 4.9min 4.9min 0 transport_latency_assumed market_resolved i 497 96 25ms 35.5s 50.0s 53.0s 0 transport_latency_assumed market_resolved k 565 165 17ms 8.7min 10.5min 10.6min 0 transport_latency_assumed new_market c 772 418 75ms 1.1min 6.0min 6.0min 0 transport_latency_assumed new_market g 768 101 241ms 21.0s 1.9min 2.3min 0 transport_latency_assumed new_market h 768 172 113ms 18.8s 2.1min 2.7min 0 transport_latency_assumed new_market i 768 230 89ms 18.8s 2.0min 2.7min 0 transport_latency_assumed new_market k 779 312 85ms 59.6s 4.9min 5.6min 0 transport_latency_assumed price_change c 98,982,270 92,732,648 5ms 12ms 115ms 6.0s 0 transport_latency_assumed price_change g 103,265,736 5,534 80ms 105ms 416ms 13.0s 0 transport_latency_assumed price_change h 98,818,274 1,456,664 18ms 37ms 171ms 1.7min 0 transport_latency_assumed price_change i 103,290,270 1,112,208 22ms 30ms 132ms 4.3s 0 transport_latency_assumed price_change k 94,458,804 8,018,378 14ms 21ms 105ms 8.5s 0 transport_latency_assumed tick_size_change c 1,808 1,655 5ms 18ms 76ms 313ms 0 transport_latency_assumed tick_size_change g 1,928 not meas. 79ms 102ms 217ms 612ms 0 transport_latency_assumed tick_size_change h 1,868 43 19ms 45ms 112ms 272ms 0 transport_latency_assumed tick_size_change i 1,928 44 22ms 29ms 125ms 334ms 0 transport_latency_assumed tick_size_change k 1,676 186 14ms 25ms 99ms 175ms 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/07/2026-09-25T07.parquet sha256sum 2026-09-25T07.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.