Hour audit: 2026-09-05T07
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-05T07 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-05T07:00:00.028898075+00:00 · last event 2026-09-05T07:59:59.999997983+00:00
VOLUME 93,387,400 rows · 928,812,728 bytes (885.78 MiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured c: 92,994,289 · h: 92,974,066 · b: 92,964,701 · e: 90,458,438 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 7,655 (0.01%) · h: 2,918,415 (3.13%) · b: 3,835 (0.00%) · e: 90,457,495 (96.86%) (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 93,387,400 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 d66eb169b1118d15c99900228fb3216b13d44f1d81cd48f44fd26371a96ee2cd
the corpus checksum ledger names this file with the same digest
joined 93,388,819 to merged 93,387,400, minus 1,419 (minus 0.0015%)
boundary drops 1,419 · 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-05T08:52:02Z 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 8,405,532 92,553,710 0-32 110bfa3f6e0801642151fdd0ea65ce5c0f0adca4825d1beeba0ebbe8a8ee947f book 490,878 53,845,880 33-34 a457ee26b0ee894dbf63e5d7bd05362cf1cb9fd55a9ada6f3041c31d9fdbb4f0 last_trade_price 49,107 2,827,305 35-35 bb9903b82433fd086575fe35a0e3129625959f147ebff6b13fd2fc5d8ada5899 market_resolved 570 88,993 36-36 6125e61e2819d2239b00404367612d42a1527a99df839c89987bd3b262e5e4fe new_market 2,251 233,376 37-37 168fac8000cdaba9f6725b11326f2dadb03e34b09fd674f019df2e8aa3962b54 price_change 84,437,110 778,123,624 38-360 c646e879149d91cceff6cb48a2679c857540b5fc7fc46c8afdaa9082015dbda4 tick_size_change 1,952 72,112 361-361 c76a894334d7d9b7db07ee7f23ac0c2864250039f9e140b62e86bb63412b2214 EVENT MIX count share price_change 84,437,110 90.42% best_bid_ask 8,405,532 9.00% book 490,878 0.53% last_trade_price 49,107 0.05% new_market 2,251 <0.01% tick_size_change 1,952 <0.01% market_resolved 570 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,405,669 8,405,532 137 519 FULL book 490,914 490,878 36 186,514 FULL last_trade_price 49,107 49,107 0 52 FULL market_resolved 570 570 0 59 FULL new_market 2,251 2,251 0 0 FULL price_change 84,438,356 84,437,110 1,246 416 FULL tick_size_change 1,952 1,952 0 26 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 8,403,060 214 56ms 68ms 258ms 4.5s 0 transport_latency_assumed best_bid_ask c 8,404,940 932 0ms 3ms 89ms 6.0s 0 transport_latency_assumed best_bid_ask e 8,146,838 8,146,745 38ms 43ms 198ms 4.5s 0 transport_latency_assumed best_bid_ask h 8,403,803 257,641 17ms 21ms 239ms 24.8s 0 transport_latency_assumed book b 105,878 2,212 59ms 182ms 33.8min 79.9d 0 book_staleness book c 102,980 491 1ms 9ms 2.4s 9.4s 0 book_staleness book e 481,101 481,067 1.5min 9.1h 32.0d 98.4d 0 book_staleness book h 107,448 7,108 20ms 77ms 2.7h 79.9d 0 book_staleness last_trade_price b 49,088 4 62ms 117ms 726ms 5.0s 0 transport_latency_assumed last_trade_price c 49,089 4 5ms 31ms 213ms 5.8s 0 transport_latency_assumed last_trade_price e 47,330 47,330 44ms 87ms 660ms 5.0s 0 transport_latency_assumed last_trade_price h 49,044 1,769 22ms 53ms 421ms 7.5s 0 transport_latency_assumed market_resolved b 544 not meas. 59ms 379ms 58.3s 58.9s 0 transport_latency_assumed market_resolved c 544 not meas. 0ms 7ms 59.8s 1.0min 0 transport_latency_assumed market_resolved e 485 485 39ms 262ms 666ms 906ms 0 transport_latency_assumed market_resolved h 544 85 18ms 133ms 47.8s 48.2s 0 transport_latency_assumed new_market b 1,528 137 197ms 20.0s 32.2s 1.4min 0 transport_latency_assumed new_market c 1,528 164 68ms 20.3s 32.7s 1.0min 0 transport_latency_assumed new_market e 1,528 1,528 160ms 21.6s 34.4s 1.1min 0 transport_latency_assumed new_market h 1,528 422 147ms 22.1s 36.5s 1.9min 0 transport_latency_assumed price_change b 84,402,651 1,268 56ms 70ms 339ms 5.0s 0 transport_latency_assumed price_change c 84,433,256 6,064 0ms 3ms 121ms 6.1s 0 transport_latency_assumed price_change e 81,779,308 81,778,492 38ms 46ms 275ms 5.0s 0 transport_latency_assumed price_change h 84,409,747 2,651,286 17ms 23ms 295ms 24.8s 0 transport_latency_assumed tick_size_change b 1,952 not meas. 56ms 67ms 112ms 361ms 0 transport_latency_assumed tick_size_change c 1,952 not meas. 0ms 3ms 17ms 214ms 0 transport_latency_assumed tick_size_change e 1,848 1,848 38ms 42ms 121ms 475ms 0 transport_latency_assumed tick_size_change h 1,952 104 17ms 20ms 386ms 718ms 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/07/2026-09-05T07.parquet sha256sum 2026-09-05T07.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.