Hour audit: 2026-09-22T12
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-22T12 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-22T12:00:00.000022395+00:00 · last event 2026-09-22T12:59:59.999968291+00:00
VOLUME 102,383,200 rows · 1,075,606,941 bytes (1.00 GiB) · 7 products, all holding rows
WITNESSES cefhi — 5 machines contributed rows
captured c: 102,272,995 · f: 102,205,107 · h: 102,173,624 · e: 102,145,429 · i: 101,125,698 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 96,202,568 (93.96%) · f: 100,871 (0.10%) · h: 3,929,645 (3.84%) · e: 178,351 (0.17%) · i: 1,971,765 (1.93%) (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 102,383,200 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 a9bdff20c98c61be9047c59e3d14c0d4025e79d24681a50fbbe3cde15d3b4b79
the corpus checksum ledger names this file with the same digest
joined 102,384,382 to merged 102,383,200, minus 1,182 (minus 0.0012%)
boundary drops 1,182 · 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-22T14:01:32Z as cefhi
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 8,946,870 105,924,656 0-34 21db0b8c874302df7714f3404def9e6f4bbebca5682d26209abad2b348959054 book 213,201 19,904,895 35-35 cd1d22fc030276d511e7337884626fc63f4d6bd1207cd4948d6e73c9038ca8db last_trade_price 67,976 3,829,539 36-36 e5e49eaee54f98c393fde6f334aef655052e41b0b8b1898477bf9d37e59d6a83 market_resolved 910 144,065 37-37 d2663f0f7850c24a0219689bded90118ed18f62ef303c9c3c10e1a8b5d692657 new_market 907 96,587 38-38 57520b188b499130d05b1477bdf555f5ecbf926d9546de49437cb716be655db9 price_change 93,150,560 944,436,444 39-394 5171ae96fd1ce73b110f7fb1b05d01fecad5d15773d1e4500d294eb494ca7c2a tick_size_change 2,776 102,344 395-395 5cc77e00c8dac6e32e9d804de29bb7cd4817b2e20d8983e24d37449e55bde8e4 EVENT MIX count share price_change 93,150,560 90.98% best_bid_ask 8,946,870 8.74% book 213,201 0.21% last_trade_price 67,976 0.07% tick_size_change 2,776 <0.01% market_resolved 910 <0.01% new_market 907 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,946,946 8,946,870 76 128 FULL book 213,487 213,201 286 15,887 FULL last_trade_price 67,976 67,976 0 1 FULL market_resolved 910 910 0 0 FULL new_market 907 907 0 0 FULL price_change 93,151,380 93,150,560 820 174 FULL tick_size_change 2,776 2,776 0 4 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,945,902 8,448,312 5ms 13ms 94ms 5.1s 0 transport_latency_assumed best_bid_ask e 8,939,898 10,509 41ms 53ms 247ms 11.8s 0 transport_latency_assumed best_bid_ask f 8,943,020 4,710 49ms 62ms 218ms 14.0s 0 transport_latency_assumed best_bid_ask h 8,942,077 306,768 19ms 29ms 138ms 22.5s 0 transport_latency_assumed best_bid_ask i 8,900,096 176,571 21ms 37ms 476ms 5.9s 0 transport_latency_assumed book c 140,061 129,860 7ms 38ms 18.0min 97.1d 0 book_staleness book e 148,936 13,765 45ms 3.8s 2.9d 115.6d 0 book_staleness book f 151,113 15,210 54ms 6.2s 3.9d 97.1d 0 book_staleness book h 147,383 17,050 22ms 231ms 1.2d 115.6d 0 book_staleness book i 164,511 37,316 30ms 4.0min 32.7min 1.0d 0 book_staleness last_trade_price c 67,754 63,128 6ms 24ms 188ms 924ms 0 transport_latency_assumed last_trade_price e 67,055 188 44ms 596ms 5.0s 11.8s 0 transport_latency_assumed last_trade_price f 67,286 178 53ms 533ms 5.8s 14.1s 0 transport_latency_assumed last_trade_price h 67,522 3,287 20ms 64ms 461ms 5.8s 0 transport_latency_assumed last_trade_price i 64,415 1,195 23ms 525ms 2.5s 5.9s 0 transport_latency_assumed market_resolved c 877 809 5ms 19ms 1.1min 1.1min 0 transport_latency_assumed market_resolved e 877 54 41ms 278ms 53.0s 1.0min 0 transport_latency_assumed market_resolved f 877 not meas. 51ms 291ms 53.1s 1.0min 0 transport_latency_assumed market_resolved h 877 21 19ms 110ms 53.3s 1.0min 0 transport_latency_assumed market_resolved i 877 26 21ms 55ms 40.6s 1.1min 0 transport_latency_assumed new_market c 627 333 79ms 11.2s 32.3s 1.6min 0 transport_latency_assumed new_market e 627 108 175ms 16.4s 27.7s 1.6min 0 transport_latency_assumed new_market f 627 89 182ms 11.8s 24.7s 1.5min 0 transport_latency_assumed new_market h 627 189 129ms 12.4s 24.5s 34.9s 0 transport_latency_assumed new_market i 627 188 103ms 15.2s 21.8s 1.3min 0 transport_latency_assumed price_change c 93,114,998 87,557,484 5ms 16ms 114ms 5.6s 0 transport_latency_assumed price_change e 92,985,260 153,726 41ms 74ms 1.1s 11.8s 0 transport_latency_assumed price_change f 93,039,408 80,684 50ms 79ms 830ms 14.0s 0 transport_latency_assumed price_change h 93,012,362 3,602,250 19ms 35ms 193ms 22.5s 0 transport_latency_assumed price_change i 91,992,412 1,756,416 22ms 56ms 1.0s 5.9s 0 transport_latency_assumed tick_size_change c 2,776 2,642 5ms 11ms 317ms 659ms 0 transport_latency_assumed tick_size_change e 2,776 1 41ms 101ms 427ms 3.0s 0 transport_latency_assumed tick_size_change f 2,776 not meas. 50ms 68ms 570ms 764ms 0 transport_latency_assumed tick_size_change h 2,776 80 19ms 35ms 401ms 2.3s 0 transport_latency_assumed tick_size_change i 2,760 53 22ms 51ms 821ms 888ms 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/12/2026-09-22T12.parquet sha256sum 2026-09-22T12.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.