Hour audit: 2026-09-22T22
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-22T22 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-22T22:00:00.000988058+00:00 · last event 2026-09-22T22:59:59.996823426+00:00
VOLUME 111,830,341 rows · 1,207,692,434 bytes (1.12 GiB) · 7 products, all holding rows
WITNESSES cfhik — 5 machines contributed rows
captured k: 110,557,966 · f: 110,357,557 · h: 110,328,469 · i: 108,421,797 · c: 96,459,121 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 18,770,633 (16.78%) · f: 148,727 (0.13%) · h: 2,668,420 (2.39%) · i: 2,040,428 (1.82%) · c: 88,202,133 (78.87%) (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,830,341 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 746b1e792193235df3e6f9a1f232a0a55fee4d0c762a5efc95311904537d1c0e
the corpus checksum ledger names this file with the same digest
joined 111,832,703 to merged 111,830,341, minus 2,362 (minus 0.0021%)
boundary drops 2,362 · 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-23T00:43:11Z as cfhik
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 our incident register was checked against the venue's own status feed at 2026-09-23T20:35Z and names no event in this hour. That is a statement about what they published, not a check that every message they sent reached us.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 11,377,613 131,625,649 0-43 1ff1016f4da37e01167a91d5742d14e1774d08278aa852911a9ff4e99686960f book 1,578,554 83,340,317 44-50 b92cfabc6eabead04e46adbe3c42ced95c21a94bd4f07899045b5a283931d7e5 last_trade_price 56,615 3,210,006 51-51 20a1f48657cb2419739c6b5a080f0cb6db91a99524be08b612c5d3d37224bb2a market_resolved 2,456 350,464 52-52 deb76573c13cbd16b25c5ad9076fb9109eb4dac0f94ca7bd4dc9930cdbafe6ca new_market 1,547 160,295 53-53 12f26ffea3386dead3fd7b5dba7ae9f3029e3bef5c65e04612f4900c7d4b7b29 price_change 98,811,116 987,639,893 54-430 87e266852e54f04ce3a2a72576434deccebf7b6a0b5e9e1328769444f549fb68 tick_size_change 2,440 90,501 431-431 19157042d24035def1ad12f1135eb6fd6d8d8c2ab772f13bfaf6668918d0946f EVENT MIX count share price_change 98,811,116 88.36% best_bid_ask 11,377,613 10.17% book 1,578,554 1.41% last_trade_price 56,615 0.05% market_resolved 2,456 <0.01% tick_size_change 2,440 <0.01% new_market 1,547 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,377,707 11,377,613 94 2,238 FULL book 1,579,878 1,578,554 1,324 188,449 FULL last_trade_price 56,615 56,615 0 298 FULL market_resolved 2,456 2,456 0 269 FULL new_market 1,547 1,547 0 0 FULL price_change 98,812,060 98,811,116 944 915 FULL tick_size_change 2,440 2,440 0 74 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,785,211 9,012,982 5ms 13ms 115ms 6.4s 0 transport_latency_assumed best_bid_ask f 11,371,687 5,343 49ms 66ms 235ms 16.4s 0 transport_latency_assumed best_bid_ask h 11,367,172 237,313 17ms 31ms 168ms 43.8s 0 transport_latency_assumed best_bid_ask i 11,184,026 184,708 20ms 27ms 110ms 4.2s 0 transport_latency_assumed best_bid_ask k 11,373,844 1,937,267 12ms 22ms 125ms 39.3s 0 transport_latency_assumed book c 1,355,882 1,193,719 11.8min 3.4d 41.9d 116.0d 0 book_staleness book f 300,200 83,582 46.5s 1.1d 31.4d 116.0d 0 book_staleness book h 343,716 119,301 1.5min 1.1d 31.4d 116.0d 0 book_staleness book i 209,130 39,149 358ms 15.5h 31.4d 116.0d 0 book_staleness book k 391,347 142,803 2.3min 1.2d 31.4d 116.0d 0 book_staleness last_trade_price c 49,188 44,168 6ms 25ms 203ms 2.5s 0 transport_latency_assumed last_trade_price f 55,392 152 52ms 290ms 3.1s 16.4s 0 transport_latency_assumed last_trade_price h 55,562 1,739 19ms 81ms 396ms 38.9s 0 transport_latency_assumed last_trade_price i 53,909 1,130 22ms 132ms 685ms 3.2s 0 transport_latency_assumed last_trade_price k 56,125 9,426 14ms 55ms 289ms 8.1s 0 transport_latency_assumed market_resolved c 1,975 1,702 5ms 41.2s 5.8min 7.7min 0 transport_latency_assumed market_resolved f 2,168 not meas. 49ms 15.6s 53.6s 1.0min 0 transport_latency_assumed market_resolved h 2,168 51 18ms 15.5s 57.5s 1.0min 0 transport_latency_assumed market_resolved i 2,160 302 21ms 17.3s 59.0s 2.4min 0 transport_latency_assumed market_resolved k 2,168 401 13ms 91ms 59.4s 1.0min 0 transport_latency_assumed new_market c 1,177 614 82ms 6.7min 7.1min 9.2min 0 transport_latency_assumed new_market f 1,038 120 144ms 13.6s 2.2min 2.7min 0 transport_latency_assumed new_market h 1,038 298 108ms 13.4s 2.2min 2.7min 0 transport_latency_assumed new_market i 1,038 306 97ms 16.2s 2.1min 2.6min 0 transport_latency_assumed new_market k 1,038 209 126ms 14.8s 2.1min 2.6min 0 transport_latency_assumed price_change c 85,263,516 77,946,894 5ms 16ms 131ms 6.4s 0 transport_latency_assumed price_change f 98,624,632 59,530 49ms 81ms 428ms 16.4s 0 transport_latency_assumed price_change h 98,556,373 2,309,670 18ms 37ms 215ms 45.2s 0 transport_latency_assumed price_change i 96,969,126 1,814,784 20ms 33ms 181ms 4.2s 0 transport_latency_assumed price_change k 98,731,004 16,680,238 12ms 27ms 153ms 39.3s 0 transport_latency_assumed tick_size_change c 2,172 2,054 5ms 9ms 104ms 242ms 0 transport_latency_assumed tick_size_change f 2,440 not meas. 49ms 70ms 251ms 621ms 0 transport_latency_assumed tick_size_change h 2,440 48 18ms 40ms 208ms 996ms 0 transport_latency_assumed tick_size_change i 2,408 49 20ms 29ms 92ms 214ms 0 transport_latency_assumed tick_size_change k 2,440 289 12ms 22ms 211ms 1.7s 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-22/22/2026-09-22T22.parquet sha256sum 2026-09-22T22.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.