Hour audit: 2026-09-05T04
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-05T04 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-05T04:00:00.032016742+00:00 · last event 2026-09-05T04:59:59.999983803+00:00
VOLUME 94,883,833 rows · 924,597,037 bytes (881.76 MiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured b: 94,746,039 · c: 94,741,964 · e: 94,732,169 · h: 94,729,236 (each machine's own feed; these overlap and do not sum to the file)
supplied b: 53,422 (0.06%) · c: 35,903 (0.04%) · e: 94,730,710 (99.84%) · h: 63,798 (0.07%) (rows of the merged file that came from it; these partition it)
5 product-machine pairs publish no supplied count; the figures above still sum to the file's 94,883,833 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 7e133235844c6368e25d8a6619814d1db8090da8467bb4860945a1fbe6bbb190
the corpus checksum ledger names this file with the same digest
joined 94,889,186 to merged 94,883,833, minus 5,353 (minus 0.0056%)
boundary drops 5,353 · 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-05T05:52:46Z 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,070,408 108,547,216 0-38 31bd96f4712b5f6ed14bb1b04862996e32dd638303945ba96faad49a84dd1983 book 261,911 26,768,704 39-39 2ec6de58e7a0613a29af3671dcd655575015dd8a80a1f5a65448d9cc0394307a last_trade_price 46,276 2,636,151 40-40 4bca47554a8f66f2861d2a6366de128a52c2663ac00eee15d999acbb7eba4348 market_resolved 1,303 211,372 41-41 2f009765a9a2e3b574c7482f5941bacf940f961153e810f66d6dce9559a1b23f new_market 2,985 318,882 42-42 3ae507c5f7827da0697772c78e102eb724cbefb4e6fa7fa73f31e92f39dde3ad price_change 84,497,746 784,916,411 43-365 e63112d511ebff10dcdeb906c04b1651d943612897230e0fff69060a757939b5 tick_size_change 3,204 116,031 366-366 74f9a1d0e0bbbfbc21bf359df1065fdfef0ae0be6e99f9e6c53b88f20d78c059 EVENT MIX count share price_change 84,497,746 89.05% best_bid_ask 10,070,408 10.61% book 261,911 0.28% last_trade_price 46,276 0.05% tick_size_change 3,204 <0.01% new_market 2,985 <0.01% market_resolved 1,303 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,070,627 10,070,408 219 195 FULL book 261,921 261,911 10 72,711 FULL last_trade_price 46,276 46,276 0 0 FULL market_resolved 1,303 1,303 0 1 FULL new_market 2,985 2,985 0 0 FULL price_change 84,502,870 84,497,746 5,124 86 FULL tick_size_change 3,204 3,204 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 10,067,196 104 55ms 69ms 361ms 8.3s 0 transport_latency_assumed best_bid_ask c 10,069,572 762 4ms 7ms 170ms 5.4s 0 transport_latency_assumed best_bid_ask e 10,067,203 10,067,044 40ms 53ms 303ms 7.0s 0 transport_latency_assumed best_bid_ask h 10,067,687 2,498 18ms 23ms 556ms 1.6min 0 transport_latency_assumed book b 160,342 51,916 99ms 1.2h 19.3d 98.2d 0 book_staleness book c 133,044 30,327 6ms 10.0min 13.6d 79.8d 0 book_staleness book e 146,037 146,029 47ms 52.1min 24.4d 98.2d 0 book_staleness book h 133,995 33,639 23ms 14.1min 13.6d 98.2d 0 book_staleness last_trade_price b 46,226 6 62ms 152ms 1.1s 8.3s 0 transport_latency_assumed last_trade_price c 46,203 6 9ms 39ms 303ms 4.8s 0 transport_latency_assumed last_trade_price e 46,187 46,187 47ms 127ms 1.4s 7.1s 0 transport_latency_assumed last_trade_price h 46,051 77 23ms 61ms 643ms 38.7s 0 transport_latency_assumed market_resolved b 1,303 not meas. 66ms 243ms 643ms 1.0min 0 transport_latency_assumed market_resolved c 1,303 not meas. 4ms 9ms 317ms 46.9s 0 transport_latency_assumed market_resolved e 1,302 1,302 44ms 194ms 686ms 55.5s 0 transport_latency_assumed market_resolved h 1,303 1 20ms 95ms 1.5s 53.7s 0 transport_latency_assumed new_market b 2,110 60 202ms 19.4s 53.5s 13.0min 0 transport_latency_assumed new_market c 2,110 352 103ms 20.3s 58.1s 30.5min 0 transport_latency_assumed new_market e 2,110 2,110 156ms 21.1s 50.3s 53.8s 0 transport_latency_assumed new_market h 2,110 463 157ms 21.4s 51.6s 2.1min 0 transport_latency_assumed price_change b 84,465,658 1,336 55ms 74ms 473ms 8.3s 0 transport_latency_assumed price_change c 84,486,528 4,456 4ms 8ms 227ms 5.4s 0 transport_latency_assumed price_change e 84,466,126 84,464,834 41ms 72ms 434ms 7.1s 0 transport_latency_assumed price_change h 84,474,886 27,120 18ms 25ms 656ms 1.6min 0 transport_latency_assumed tick_size_change b 3,204 not meas. 55ms 66ms 141ms 683ms 0 transport_latency_assumed tick_size_change c 3,204 not meas. 4ms 6ms 22ms 1.3s 0 transport_latency_assumed tick_size_change e 3,204 3,204 40ms 54ms 125ms 370ms 0 transport_latency_assumed tick_size_change h 3,204 not meas. 18ms 20ms 309ms 3.7s 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/04/2026-09-05T04.parquet sha256sum 2026-09-05T04.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.