Hour audit: 2026-09-30T21
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-30T21 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-30T21:00:00.000009822+00:00 · last event 2026-09-30T21:59:59.999997318+00:00
VOLUME 99,607,467 rows · 1,053,969,967 bytes (1005.14 MiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured m: 99,466,356 · k: 99,461,181 · h: 99,457,897 · g: 99,446,093 · i: 99,439,935 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 67,834,226 (68.10%) · k: 21,729,675 (21.82%) · h: 8,784,502 (8.82%) · g: 239,207 (0.24%) · i: 1,019,857 (1.02%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 849327247b85e27d7c38178c6351218cc764f9694ce7ff06ebd02a0a4f7c9934
the corpus checksum ledger names this file with the same digest
joined 99,609,717 to merged 99,607,467, minus 2,250 (minus 0.0023%)
boundary drops 2,250 · 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-10-01T00:24:46Z as ghikm
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 9,442,735 112,815,775 0-36 71a713237f57140466df11fe20a726c1d8498b8d75a7ee65daa971f4c349db81 book 270,229 28,448,220 37-38 721bcf3be972367877fd5dcc4bd79e71cba5cf42c540166e0039dddc2a724621 last_trade_price 49,521 2,887,607 39-39 a8c83ccc152e857470957efe4e324506ab7dba017c405a1352ea86a3be4743f5 market_resolved 1,279 186,083 40-40 413812de2fd656489b8a318c682239b0a19c04a0b234b5fbfe36eafb7d4a4210 new_market 585 64,204 41-41 4bdabe0b8c89e1341153ffe889833d5f12d83c55ac0a3fa3c254ac33b5ad7faf price_change 89,841,066 908,349,758 42-384 838afbe8fa4de724d04ac533cf71e716cdc4c65b52e7aa308376c031f81b56b3 tick_size_change 2,052 77,674 385-385 6925e92c13f91fe700555be2ed2638d448efb85f7cc573705cd5b6756fba4779 EVENT MIX count share price_change 89,841,066 90.20% best_bid_ask 9,442,735 9.48% book 270,229 0.27% last_trade_price 49,521 0.05% tick_size_change 2,052 <0.01% market_resolved 1,279 <0.01% new_market 585 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,442,920 9,442,735 185 65 FULL book 270,233 270,229 4 79,007 FULL last_trade_price 49,522 49,521 1 0 FULL market_resolved 1,279 1,279 0 0 FULL new_market 585 585 0 0 FULL price_change 89,843,126 89,841,066 2,060 22 FULL tick_size_change 2,052 2,052 0 1 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,441,525 19,954 80ms 108ms 268ms 10.7s 0 transport_latency_assumed best_bid_ask h 9,442,049 834,490 26ms 66ms 230ms 39.9s 0 transport_latency_assumed best_bid_ask i 9,442,150 84,802 61ms 100ms 238ms 6.1s 0 transport_latency_assumed best_bid_ask k 9,442,192 2,030,862 18ms 54ms 197ms 38.2s 0 transport_latency_assumed best_bid_ask m 9,442,418 6,472,627 7ms 41ms 170ms 986ms 0 transport_latency_assumed book g 150,093 44,088 118ms 9.4h 24.4d 124.0d 0 book_staleness book h 141,092 45,473 48ms 7.4h 23.4d 123.9d 0 book_staleness book i 130,179 28,092 80ms 4.5h 23.4d 123.9d 0 book_staleness book k 135,223 52,675 40ms 6.1h 23.4d 124.0d 0 book_staleness book m 134,110 99,901 22ms 5.4h 22.1d 124.0d 0 book_staleness last_trade_price g 49,505 116 91ms 211ms 1.1s 10.7s 0 transport_latency_assumed last_trade_price h 49,510 4,463 28ms 95ms 395ms 32.6s 0 transport_latency_assumed last_trade_price i 49,504 478 70ms 141ms 514ms 1.7s 0 transport_latency_assumed last_trade_price k 49,508 11,120 27ms 99ms 348ms 6.3s 0 transport_latency_assumed last_trade_price m 49,508 33,344 10ms 67ms 244ms 867ms 0 transport_latency_assumed market_resolved g 1,161 4 84ms 24.6s 54.0s 54.1s 0 transport_latency_assumed market_resolved h 1,161 123 33ms 29.2s 52.6s 55.9s 0 transport_latency_assumed market_resolved i 1,161 11 75ms 25.5s 54.0s 56.0s 0 transport_latency_assumed market_resolved k 1,161 350 22ms 78ms 49.8s 54.2s 0 transport_latency_assumed market_resolved m 1,161 791 17ms 29.8s 53.8s 53.9s 0 transport_latency_assumed new_market g 409 43 195ms 10.8s 37.1s 1.5min 0 transport_latency_assumed new_market h 409 91 54ms 10.3s 38.0s 1.3min 0 transport_latency_assumed new_market i 409 83 97ms 10.1s 42.6s 1.4min 0 transport_latency_assumed new_market k 409 110 55ms 10.3s 36.9s 1.9min 0 transport_latency_assumed new_market m 409 258 31ms 10.2s 37.7s 40.3s 0 transport_latency_assumed price_change g 89,801,348 174,998 81ms 120ms 381ms 10.7s 0 transport_latency_assumed price_change h 89,821,624 7,899,670 26ms 70ms 258ms 42.7s 0 transport_latency_assumed price_change i 89,814,480 906,366 62ms 104ms 277ms 6.1s 0 transport_latency_assumed price_change k 89,830,640 19,634,010 19ms 59ms 225ms 38.2s 0 transport_latency_assumed price_change m 89,836,698 61,226,022 8ms 44ms 181ms 1.3s 0 transport_latency_assumed tick_size_change g 2,052 4 80ms 102ms 278ms 415ms 0 transport_latency_assumed tick_size_change h 2,052 192 24ms 62ms 189ms 399ms 0 transport_latency_assumed tick_size_change i 2,052 25 64ms 96ms 262ms 306ms 0 transport_latency_assumed tick_size_change k 2,048 548 15ms 50ms 192ms 390ms 0 transport_latency_assumed tick_size_change m 2,052 1,283 10ms 39ms 199ms 233ms 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-30/21/2026-09-30T21.parquet sha256sum 2026-09-30T21.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.