Hour audit: 2026-09-05T03
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-05T03 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-05T03:00:00.106220467+00:00 · last event 2026-09-05T03:59:59.999992471+00:00
VOLUME 101,758,140 rows · 1,023,861,542 bytes (976.43 MiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured c: 101,367,287 · h: 101,359,330 · e: 101,347,759 · b: 96,966,170 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 7,508 (0.01%) · h: 25,406 (0.02%) · e: 101,347,611 (99.60%) · b: 377,615 (0.37%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 101,758,140 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 770b4fbaef81f24be03536423515fc1f133ad1b1806ebf664ae5df19ba1a702f
the corpus checksum ledger names this file with the same digest
joined 101,758,921 to merged 101,758,140, minus 781 (minus 0.0008%)
boundary drops 781 · 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-05T04:54:05Z as bceh
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 10,529,573 113,728,256 0-40 5e41a57b41822d78d35f33b4b0652441a3329abb1cd34759a879694340cd1032 book 484,071 53,035,532 41-42 9dc213de3ac83a2578bfa0a3b7ebed2c7176830dea205753f54c1ebf907c56ee last_trade_price 45,406 2,583,712 43-43 fb7093aaacc9dd819035110b11fa0b04469c081cb4d0b41917b6ffd04bc920e4 market_resolved 2,102 318,990 44-44 0041a79ab2dd53adef8cef600b78646f27c0b89e7a7ac835d8457ac3c568e1ca new_market 874 97,599 45-45 3cebbd61dbfa0e3c4ffbe39e780bddafac21a4186d900fe5fcc36a7264aefeb1 price_change 90,691,830 852,782,068 46-391 9b5d2895e961e52d3b59f226976875ec5fe3e41cfc0171c834546f61608c3c5a tick_size_change 4,284 156,455 392-392 f06a81396f30710317fc237a52a268c784aad9e5e6e73483430d0cd9097e2632 EVENT MIX count share price_change 90,691,830 89.12% best_bid_ask 10,529,573 10.35% book 484,071 0.48% last_trade_price 45,406 0.04% tick_size_change 4,284 <0.01% market_resolved 2,102 <0.01% new_market 874 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,529,650 10,529,573 77 628 FULL book 484,093 484,071 22 188,043 FULL last_trade_price 45,406 45,406 0 63 FULL market_resolved 2,102 2,102 0 11 FULL new_market 874 874 0 0 FULL price_change 90,692,512 90,691,830 682 184 FULL tick_size_change 4,284 4,284 0 66 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 10,039,187 10 55ms 67ms 175ms 2.8s 0 transport_latency_assumed best_bid_ask c 10,529,362 414 4ms 6ms 45ms 5.6s 0 transport_latency_assumed best_bid_ask e 10,527,439 10,527,423 38ms 44ms 177ms 5.4s 0 transport_latency_assumed best_bid_ask h 10,529,087 1,726 17ms 22ms 87ms 23.4s 0 transport_latency_assumed book b 471,750 376,174 1.6min 6.6h 32.3d 98.2d 0 book_staleness book c 97,405 3,796 5ms 20ms 1.2h 79.7d 0 book_staleness book e 102,800 102,800 40ms 1.1s 9.9h 33.3d 0 book_staleness book h 94,556 1,301 19ms 42ms 2.6s 79.6d 0 book_staleness last_trade_price b 43,261 2 64ms 101ms 458ms 5.0s 0 transport_latency_assumed last_trade_price c 45,385 8 9ms 36ms 209ms 5.0s 0 transport_latency_assumed last_trade_price e 45,279 45,279 44ms 78ms 564ms 5.4s 0 transport_latency_assumed last_trade_price h 45,382 117 22ms 55ms 242ms 6.9s 0 transport_latency_assumed market_resolved b 1,998 92 56ms 186ms 5.0min 5.3min 0 transport_latency_assumed market_resolved c 2,009 1 4ms 6ms 31ms 50.1s 0 transport_latency_assumed market_resolved e 2,009 2,009 39ms 112ms 388ms 658ms 0 transport_latency_assumed market_resolved h 2,009 not meas. 18ms 48ms 148ms 3.3s 0 transport_latency_assumed new_market b 646 11 137ms 14.2s 34.1s 35.2min 0 transport_latency_assumed new_market c 646 53 51ms 13.6s 30.7s 22.7min 0 transport_latency_assumed new_market e 646 646 115ms 11.4s 29.8s 27.0min 0 transport_latency_assumed new_market h 646 164 109ms 15.8s 36.0s 24.3min 0 transport_latency_assumed price_change b 86,405,308 1,326 56ms 68ms 195ms 2.8s 0 transport_latency_assumed price_change c 90,688,196 3,236 4ms 7ms 51ms 5.6s 0 transport_latency_assumed price_change e 90,665,302 90,665,170 39ms 49ms 196ms 5.5s 0 transport_latency_assumed price_change h 90,683,366 22,098 17ms 23ms 93ms 36.2s 0 transport_latency_assumed tick_size_change b 4,020 not meas. 55ms 66ms 104ms 364ms 0 transport_latency_assumed tick_size_change c 4,284 not meas. 4ms 6ms 14ms 39ms 0 transport_latency_assumed tick_size_change e 4,284 4,284 38ms 44ms 110ms 161ms 0 transport_latency_assumed tick_size_change h 4,284 not meas. 17ms 19ms 35ms 75ms 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-05/03/2026-09-05T03.parquet sha256sum 2026-09-05T03.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.