Hour audit: 2026-09-29T23
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-29T23 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-29T23:00:00.000169742+00:00 · last event 2026-09-29T23:59:59.999959832+00:00
VOLUME 108,250,985 rows · 1,221,796,951 bytes (1.14 GiB) · 7 products, all holding rows
WITNESSES cghikm — 6 machines contributed rows
captured k: 107,658,407 · c: 107,646,955 · i: 107,596,190 · g: 107,508,840 · h: 106,742,303 · m: 106,046,440 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 718,394 (0.66%) · c: 35,513,227 (32.81%) · i: 502,800 (0.46%) · g: 24,400 (0.02%) · h: 333,959 (0.31%) · m: 71,158,205 (65.73%) (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 108,250,985 rows exactly, so those pairs supplied none
6 expected, all 6 contributed
INTEGRITY sha256 6ee5c3a33107aac42dfff52d7ee0132c7567e3567229e10608bbd3212c08c3e7
the corpus checksum ledger names this file with the same digest
joined 108,252,693 to merged 108,250,985, minus 1,708 (minus 0.0016%)
boundary drops 1,708 · 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-30T12:42:13Z as cghikm
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 11,086,778 136,226,121 0-42 a8d1ecfa456cbb79de6aadbbd27db7b6977cb68d273b81845f234d1971e4ae73 book 731,564 62,204,976 43-45 5a063ec76bc293eeaa916cd4b5bf8099dd76147b3b30dd2fdb3ce89f0f7d9a02 last_trade_price 55,755 3,110,767 46-46 46d090bd9dd291039f6c71add93bb3c916043d6ea5113c113a238ceb68c9f2b1 market_resolved 3,746 557,938 47-47 2dda98a6bcc96057906cea187647ce1071ea3f511a1e1ef981881a239bfc1407 new_market 900 93,508 48-48 f24d1550a9386598aaf9a1d5f63ff70e56ca81722029c9a96a9619b8948ee712 price_change 96,370,010 1,018,283,721 49-416 23d37a36ba8fdb7c8abe591d2494201c8d0599f2ee60d78df9a221500750a428 tick_size_change 2,232 83,690 417-417 5e45d0529a1a046612a27d30a213646909f815b27f0aff4586666f07458fa246 EVENT MIX count share price_change 96,370,010 89.02% best_bid_ask 11,086,778 10.24% book 731,564 0.68% last_trade_price 55,755 0.05% market_resolved 3,746 <0.01% tick_size_change 2,232 <0.01% new_market 900 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,086,954 11,086,778 176 665 FULL book 731,614 731,564 50 211,271 FULL last_trade_price 55,755 55,755 0 42 FULL market_resolved 3,746 3,746 0 37 FULL new_market 900 900 0 0 FULL price_change 96,371,492 96,370,010 1,482 999 FULL tick_size_change 2,232 2,232 0 18 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,085,471 3,673,085 5ms 13ms 111ms 12.8s 0 transport_latency_assumed best_bid_ask g 11,081,710 322 80ms 101ms 341ms 17.2s 0 transport_latency_assumed best_bid_ask h 11,059,736 23,351 18ms 24ms 155ms 1.0min 0 transport_latency_assumed best_bid_ask i 11,066,566 11,320 21ms 28ms 151ms 8.7s 0 transport_latency_assumed best_bid_ask k 11,084,653 52,115 13ms 21ms 97ms 54.3s 0 transport_latency_assumed best_bid_ask m 11,011,958 7,326,585 4ms 7ms 41ms 7.3s 0 transport_latency_assumed book c 161,159 65,931 9ms 7.3h 22.5d 104.6d 0 book_staleness book g 139,364 19,423 105ms 57.2min 21.2d 123.1d 0 book_staleness book h 211,296 85,090 278ms 23.3h 32.2d 123.0d 0 book_staleness book i 587,975 380,665 16.4min 2.2d 38.4d 123.1d 0 book_staleness book k 188,352 63,165 30ms 17.0h 24.8d 123.1d 0 book_staleness book m 158,024 117,290 7ms 8.4h 22.5d 104.5d 0 book_staleness last_trade_price c 55,537 16,338 6ms 29ms 242ms 1.8s 0 transport_latency_assumed last_trade_price g 54,284 13 95ms 1.4s 8.6s 17.2s 0 transport_latency_assumed last_trade_price h 54,162 121 19ms 90ms 615ms 5.7s 0 transport_latency_assumed last_trade_price i 53,929 60 24ms 352ms 1.9s 2.7s 0 transport_latency_assumed last_trade_price k 55,580 703 15ms 42ms 275ms 5.5s 0 transport_latency_assumed last_trade_price m 53,519 38,520 5ms 10ms 94ms 1.2s 0 transport_latency_assumed market_resolved c 3,459 1,084 5ms 37ms 51.6s 53.9s 0 transport_latency_assumed market_resolved g 3,459 1 82ms 19.4s 51.5s 2.0min 0 transport_latency_assumed market_resolved h 3,458 7 18ms 76ms 47.2s 56.1s 0 transport_latency_assumed market_resolved i 3,459 496 21ms 25.4s 53.3s 57.7s 0 transport_latency_assumed market_resolved k 3,459 15 14ms 18.3s 49.7s 57.5s 0 transport_latency_assumed market_resolved m 3,423 2,143 4ms 18ms 50.7s 2.4min 0 transport_latency_assumed new_market c 572 182 77ms 9.3s 19.3s 1.4min 0 transport_latency_assumed new_market g 572 61 250ms 13.4s 52.5s 1.6min 0 transport_latency_assumed new_market h 572 80 116ms 7.0s 60.0s 1.8min 0 transport_latency_assumed new_market i 572 105 100ms 12.6s 30.4s 1.3min 0 transport_latency_assumed new_market k 572 137 131ms 15.2s 32.9s 1.7min 0 transport_latency_assumed new_market m 572 335 50ms 13.4s 29.7s 1.6min 0 transport_latency_assumed price_change c 96,338,525 31,755,868 5ms 16ms 132ms 13.0s 0 transport_latency_assumed price_change g 96,227,219 4,580 81ms 117ms 888ms 17.4s 0 transport_latency_assumed price_change h 95,410,851 225,290 18ms 30ms 254ms 1.0min 0 transport_latency_assumed price_change i 95,881,457 110,154 21ms 35ms 399ms 8.7s 0 transport_latency_assumed price_change k 96,323,559 602,255 13ms 24ms 124ms 56.6s 0 transport_latency_assumed price_change m 94,816,780 63,671,863 4ms 8ms 50ms 7.6s 0 transport_latency_assumed tick_size_change c 2,232 739 5ms 12ms 237ms 420ms 0 transport_latency_assumed tick_size_change g 2,232 not meas. 80ms 96ms 286ms 487ms 0 transport_latency_assumed tick_size_change h 2,228 20 18ms 27ms 101ms 469ms 0 transport_latency_assumed tick_size_change i 2,232 not meas. 21ms 28ms 104ms 266ms 0 transport_latency_assumed tick_size_change k 2,232 4 13ms 20ms 114ms 434ms 0 transport_latency_assumed tick_size_change m 2,164 1,469 4ms 7ms 37ms 159ms 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-29/23/2026-09-29T23.parquet sha256sum 2026-09-29T23.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.