Hour audit: 2026-09-20T08
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-20T08 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-20T08:00:00.003561210+00:00 · last event 2026-09-20T08:59:59.999959195+00:00
VOLUME 112,002,660 rows · 1,186,813,368 bytes (1.11 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 111,549,539 · h: 111,546,462 · e: 111,406,376 · g: 111,228,250 · f: 104,965,470 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 105,654,859 (94.33%) · h: 5,201,285 (4.64%) · e: 491,582 (0.44%) · g: 34,169 (0.03%) · f: 620,765 (0.55%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 112,002,660 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 deb79ac8f2251edfd0fc802fc2fdc16b082b362d4fe5b03780462a6f3873ef79
the corpus checksum ledger names this file with the same digest
joined 112,005,312 to merged 112,002,660, minus 2,652 (minus 0.0024%)
boundary drops 2,652 · 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-20T10:36:02Z as cefgh
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 12,358,405 140,463,381 0-47 20a27bf9f2e4f26624c19e24f2222b20f02f5906e23757dc1c6438b5f3122e01 book 507,298 53,162,871 48-49 0fc739ff9c312555e18d74767cdb1fdb70636a6880bcf6e99be0a4a7b6d7aa22 last_trade_price 56,382 3,306,398 50-50 a1a38e397c404eb786abeb93211a379fde277cb3276236afb0ce298b0d4acf13 market_resolved 25,171 3,811,247 51-51 97dd6bf5cc876935d0ae4dd87369f83b014febf1b53f9c067a33c082e884f7da new_market 9,498 1,210,635 52-52 cdaeb570a2a6ba6740574657dbe15d5687a42b2eabd22e694a7d9afabd27be41 price_change 99,041,742 983,431,452 53-430 fe32fe8cb5cbeb40a505ad21d5f0b50737bef893e957c8c140409736c02e0bfd tick_size_change 4,164 153,409 431-431 9503939ae375964c0582b83d67e3e12291dfae02ed11ee4bd663f479cf0104ca EVENT MIX count share price_change 99,041,742 88.43% best_bid_ask 12,358,405 11.03% book 507,298 0.45% last_trade_price 56,382 0.05% market_resolved 25,171 0.02% new_market 9,498 <0.01% tick_size_change 4,164 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,358,663 12,358,405 258 1,752 FULL book 507,456 507,298 158 169,144 FULL last_trade_price 56,385 56,382 3 151 FULL market_resolved 25,172 25,171 1 23,358 FULL new_market 9,536 9,498 38 6,589 FULL price_change 99,043,936 99,041,742 2,194 805 FULL tick_size_change 4,164 4,164 0 61 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 12,355,329 11,754,278 5ms 13ms 145ms 7.4s 0 transport_latency_assumed best_bid_ask e 12,353,179 49,857 40ms 51ms 261ms 26.2s 0 transport_latency_assumed best_bid_ask f 11,548,457 24,520 46ms 60ms 286ms 18.6s 0 transport_latency_assumed best_bid_ask g 12,350,787 2,334 75ms 98ms 551ms 37.1s 0 transport_latency_assumed best_bid_ask h 12,354,452 527,416 18ms 33ms 234ms 51.8s 0 transport_latency_assumed book c 134,930 120,096 7ms 1.5min 11.6d 111.8d 0 book_staleness book e 123,504 6,017 43ms 1.2s 18.9h 113.4d 0 book_staleness book f 460,005 346,668 3.4min 1.5d 38.5d 113.4d 0 book_staleness book g 126,906 9,093 86ms 9.8s 1.7d 94.9d 0 book_staleness book h 138,896 25,424 24ms 3.4min 12.9d 113.4d 0 book_staleness last_trade_price c 56,056 52,340 6ms 26ms 293ms 3.7s 0 transport_latency_assumed last_trade_price e 55,726 364 42ms 194ms 4.3s 26.2s 0 transport_latency_assumed last_trade_price f 52,171 177 49ms 207ms 5.0s 18.6s 0 transport_latency_assumed last_trade_price g 55,130 44 82ms 348ms 6.8s 36.9s 0 transport_latency_assumed last_trade_price h 56,127 3,457 19ms 64ms 476ms 44.0s 0 transport_latency_assumed market_resolved c 1,736 1,669 5ms 15ms 35.0s 1.0min 0 transport_latency_assumed market_resolved e 1,737 11 42ms 200ms 35.1s 1.0min 0 transport_latency_assumed market_resolved f 24,972 23,431 4.1h 6.7h 7.6h 7.7h 0 transport_latency_assumed market_resolved g 1,737 4 79ms 324ms 919ms 15.1s 0 transport_latency_assumed market_resolved h 1,737 56 20ms 84ms 35.3s 1.2min 0 transport_latency_assumed new_market c 1,862 1,165 100ms 26.6s 51.2s 6.7h 0 transport_latency_assumed new_market e 1,862 495 193ms 27.4s 46.4s 1.1min 0 transport_latency_assumed new_market f 8,451 6,849 2.7h 6.6h 9.6h 14.3h 0 transport_latency_assumed new_market g 1,862 222 311ms 26.5s 47.7s 3.5h 0 transport_latency_assumed new_market h 1,862 767 149ms 27.1s 51.4s 1.1min 0 transport_latency_assumed price_change c 98,995,462 93,721,342 5ms 15ms 170ms 7.9s 0 transport_latency_assumed price_change e 98,866,204 434,830 41ms 64ms 514ms 26.2s 0 transport_latency_assumed price_change f 92,867,494 219,116 47ms 74ms 567ms 18.6s 0 transport_latency_assumed price_change g 98,687,664 22,472 76ms 128ms 1.3s 37.1s 0 transport_latency_assumed price_change h 98,989,224 4,643,982 18ms 38ms 273ms 51.8s 0 transport_latency_assumed tick_size_change c 4,164 3,969 5ms 11ms 129ms 471ms 0 transport_latency_assumed tick_size_change e 4,164 8 40ms 49ms 302ms 572ms 0 transport_latency_assumed tick_size_change f 3,920 4 47ms 60ms 379ms 726ms 0 transport_latency_assumed tick_size_change g 4,164 not meas. 75ms 91ms 735ms 1.7s 0 transport_latency_assumed tick_size_change h 4,164 183 18ms 31ms 171ms 828ms 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-20/08/2026-09-20T08.parquet sha256sum 2026-09-20T08.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.