Hour audit: 2026-09-05T10
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-05T10 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-05T10:00:00.060251583+00:00 · last event 2026-09-05T10:59:59.999963590+00:00
VOLUME 108,868,524 rows · 1,125,676,105 bytes (1.05 GiB) · 7 products, all holding rows
WITNESSES bcefgh — 6 machines contributed rows
captured c: 108,428,644 · e: 108,428,273 · h: 108,417,831 · f: 108,341,280 · g: 108,281,299 · b: 104,026,092 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 91,837 (0.08%) · e: 50,586 (0.05%) · h: 10,530 (0.01%) · f: 122,206 (0.11%) · g: 108,277,249 (99.46%) · b: 316,116 (0.29%) (rows of the merged file that came from it; these partition it)
9 product-machine pairs publish no supplied count; the figures above still sum to the file's 108,868,524 rows exactly, so those pairs supplied none
6 expected, all 6 contributed
INTEGRITY sha256 442424a1512062178ca94e9b240723623058d9b9de4e120f67c4a0a6de2a5828
the corpus checksum ledger names this file with the same digest
joined 108,872,975 to merged 108,868,524, minus 4,451 (minus 0.0041%)
boundary drops 4,451 · 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-05T18:35:37Z as bcefgh
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,078,816 112,543,309 0-38 5107260a221e55e5fe147ca2589b34828fd7e27eea5e28c2fc717b5057d709ae book 531,177 55,895,919 39-41 c7efd6cce0844f73481d956e419e1b1198dc197b016d9ba50380226ee2f1b393 last_trade_price 53,974 3,143,920 42-42 2e3c60ddb692bdc52461b52a25765974d8eb164478212e8654b4f3b10ac9c5e4 market_resolved 688 112,579 43-43 aa6ae5cf1bbe61effb76f3151f500103efe65789c31d7bf9ae08c3037fc68f27 new_market 761 83,159 44-44 7b97cd75f6d1f1f008a0af2398427df57a4697af6c3bb590ab7d03ae4827f738 price_change 98,198,984 952,500,768 45-419 7df6c8d9b6662d6e9d3f75f11a67ec0d9cd15336e54d264c2b1c7139c2c1c961 tick_size_change 4,124 151,311 420-420 bbb91efeed282372b881799011f92f9ce253c2ef186f92a1d062b86b615b1fcb EVENT MIX count share price_change 98,198,984 90.20% best_bid_ask 10,078,816 9.26% book 531,177 0.49% last_trade_price 53,974 0.05% tick_size_change 4,124 <0.01% new_market 761 <0.01% market_resolved 688 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,079,210 10,078,816 394 652 FULL book 531,465 531,177 288 188,396 FULL last_trade_price 53,977 53,974 3 97 FULL market_resolved 688 688 0 37 FULL new_market 761 761 0 9 FULL price_change 98,202,750 98,198,984 3,766 342 FULL tick_size_change 4,124 4,124 0 59 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 9,607,079 not meas. 56ms 68ms 148ms 2.7s 0 transport_latency_assumed best_bid_ask c 10,068,265 572 6ms 53ms 77ms 8.3s 0 transport_latency_assumed best_bid_ask e 10,077,166 3,887 39ms 43ms 109ms 2.3s 0 transport_latency_assumed best_bid_ask f 10,070,977 8,674 48ms 55ms 213ms 2.4s 0 transport_latency_assumed best_bid_ask g 10,065,116 10,064,735 83ms 102ms 440ms 20.0s 0 transport_latency_assumed best_bid_ask h 10,078,178 948 18ms 21ms 76ms 7.4s 0 transport_latency_assumed book b 490,114 316,087 1.5min 10.0h 31.7d 98.5d 0 book_staleness book c 199,809 88,395 58ms 4.1h 21.9d 98.5d 0 book_staleness book e 111,175 1,574 41ms 70ms 675ms 36.1d 0 book_staleness book f 113,772 4,679 50ms 140ms 8.3min 1.0d 0 book_staleness book g 120,189 120,151 82ms 3.5s 6.1h 98.5d 0 book_staleness book h 110,941 291 21ms 40ms 319ms 6.7s 0 book_staleness last_trade_price b 51,614 1 65ms 108ms 481ms 5.0s 0 transport_latency_assumed last_trade_price c 53,874 4 17ms 66ms 226ms 7.2s 0 transport_latency_assumed last_trade_price e 53,954 452 45ms 79ms 388ms 5.0s 0 transport_latency_assumed last_trade_price f 53,281 963 54ms 99ms 791ms 5.0s 0 transport_latency_assumed last_trade_price g 52,552 52,549 89ms 149ms 1.4s 20.0s 0 transport_latency_assumed last_trade_price h 53,959 5 23ms 53ms 267ms 6.7s 0 transport_latency_assumed market_resolved b 639 16 57ms 250ms 4.6min 5.8min 0 transport_latency_assumed market_resolved c 667 not meas. 5ms 53ms 64ms 70ms 0 transport_latency_assumed market_resolved e 667 not meas. 40ms 184ms 479ms 626ms 0 transport_latency_assumed market_resolved f 667 8 47ms 52ms 873ms 1.1s 0 transport_latency_assumed market_resolved g 664 664 78ms 106ms 13.2s 57.6s 0 transport_latency_assumed market_resolved h 667 not meas. 18ms 70ms 372ms 56.3s 0 transport_latency_assumed new_market b 535 12 148ms 13.7s 32.2min 1.1h 0 transport_latency_assumed new_market c 529 6 62ms 12.5s 29.9s 1.1min 0 transport_latency_assumed new_market e 529 73 126ms 16.7s 36.9s 55.5s 0 transport_latency_assumed new_market f 529 128 136ms 19.3s 31.2s 40.8s 0 transport_latency_assumed new_market g 532 532 229ms 14.6s 45.6s 39.0min 0 transport_latency_assumed new_market h 529 10 84ms 16.3s 24.7s 1.1min 0 transport_latency_assumed price_change b 93,872,211 not meas. 56ms 68ms 174ms 2.8s 0 transport_latency_assumed price_change c 98,101,376 2,860 6ms 54ms 86ms 8.4s 0 transport_latency_assumed price_change e 98,180,658 44,600 39ms 44ms 129ms 2.3s 0 transport_latency_assumed price_change f 98,097,930 107,742 48ms 61ms 232ms 3.7s 0 transport_latency_assumed price_change g 98,038,134 98,034,506 81ms 117ms 470ms 20.0s 0 transport_latency_assumed price_change h 98,169,433 9,276 18ms 22ms 88ms 7.7s 0 transport_latency_assumed tick_size_change b 3,900 not meas. 56ms 67ms 112ms 289ms 0 transport_latency_assumed tick_size_change c 4,124 not meas. 6ms 53ms 66ms 244ms 0 transport_latency_assumed tick_size_change e 4,124 not meas. 39ms 43ms 81ms 991ms 0 transport_latency_assumed tick_size_change f 4,124 12 49ms 93ms 181ms 1.7s 0 transport_latency_assumed tick_size_change g 4,112 4,112 81ms 174ms 372ms 487ms 0 transport_latency_assumed tick_size_change h 4,124 not meas. 18ms 21ms 80ms 2.0s 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/10/2026-09-05T10.parquet sha256sum 2026-09-05T10.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.