Hour audit: 2026-09-10T13
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-10T13 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-10T13:00:00.000043175+00:00 · last event 2026-09-10T13:59:59.999864330+00:00
VOLUME 114,252,193 rows · 1,231,784,014 bytes (1.15 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 113,154,127 · e: 113,135,496 · f: 113,084,589 · g: 112,924,726 · c: 99,541,089 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 19,730,029 (17.27%) · e: 1,121,833 (0.98%) · f: 426,944 (0.37%) · g: 40,609 (0.04%) · c: 92,932,778 (81.34%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 114,252,193 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 cd5f9448c9f8c4f288221e66eee75e534b78b4e47415c12d3e4743c4219065e3
the corpus checksum ledger names this file with the same digest
joined 114,254,433 to merged 114,252,193, minus 2,240 (minus 0.0020%)
boundary drops 2,240 · 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-10T14:59:26Z 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 10,789,898 123,058,258 0-41 5929edaa405e68d67d0fdb6fadcde1882d932b406543e558ec16224cd9af421f book 1,209,486 79,209,645 42-46 a5790defcd033b875a573baa5604d71ef13288ca9dbd42675448034d9a219840 last_trade_price 78,162 4,325,389 47-47 d33816fdb71cf5e46f09042db6d62a2b191dfcbdf111d183861745ab08f1f5a0 market_resolved 767 120,619 48-48 894d597264ba8a591362906194b05ad51404e1f19f393a8dc89383617e4a4d6a new_market 1,984 206,271 49-49 00d965c629eab5a37f148a394524ca0ae83c8bd75fe069efe4d688ee6aa4b28d price_change 102,168,684 1,023,444,028 50-439 63965fe5ba0148215c91b75f94ed5c301e837de4894def046c6db9d02d09fc49 tick_size_change 3,212 118,647 440-440 1a5e38ea3d32213891ce909285149aa8454fb95c41483588545f0ef36d5d480a EVENT MIX count share price_change 102,168,684 89.42% best_bid_ask 10,789,898 9.44% book 1,209,486 1.06% last_trade_price 78,162 0.07% tick_size_change 3,212 <0.01% new_market 1,984 <0.01% market_resolved 767 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,790,114 10,789,898 216 2,722 FULL book 1,209,500 1,209,486 14 193,168 FULL last_trade_price 78,162 78,162 0 257 FULL market_resolved 767 767 0 77 FULL new_market 1,984 1,984 0 9 FULL price_change 102,170,694 102,168,684 2,010 1,123 FULL tick_size_change 3,212 3,212 0 62 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,384,033 8,768,724 6ms 16ms 198ms 8.6s 0 transport_latency_assumed best_bid_ask e 10,786,002 105,720 40ms 53ms 345ms 13.4s 0 transport_latency_assumed best_bid_ask f 10,785,806 36,062 47ms 62ms 291ms 20.3s 0 transport_latency_assumed best_bid_ask g 10,783,012 2,433 80ms 115ms 618ms 28.8s 0 transport_latency_assumed best_bid_ask h 10,788,063 1,876,959 18ms 30ms 299ms 46.0s 0 transport_latency_assumed book c 1,179,544 1,164,598 11.5min 1.1d 29.8d 103.7d 0 book_staleness book e 166,121 4,196 43ms 373ms 23.4s 85.0d 0 book_staleness book f 165,939 3,598 51ms 288ms 3.0min 85.1d 0 book_staleness book g 173,918 7,242 91ms 2.0s 14.4h 85.1d 0 book_staleness book h 165,753 29,852 22ms 85ms 3.5s 85.1d 0 book_staleness last_trade_price c 67,452 62,475 11ms 53ms 372ms 5.0s 0 transport_latency_assumed last_trade_price e 77,953 905 55ms 303ms 5.0s 13.4s 0 transport_latency_assumed last_trade_price f 77,648 667 61ms 238ms 3.4s 20.4s 0 transport_latency_assumed last_trade_price g 77,068 70 99ms 454ms 7.2s 28.7s 0 transport_latency_assumed last_trade_price h 78,027 14,045 25ms 90ms 631ms 38.5s 0 transport_latency_assumed market_resolved c 680 651 6ms 33ms 6.3min 6.8min 0 transport_latency_assumed market_resolved e 734 9 41ms 170ms 493ms 29.2s 0 transport_latency_assumed market_resolved f 734 1 48ms 186ms 447ms 29.2s 0 transport_latency_assumed market_resolved g 734 not meas. 85ms 325ms 866ms 45.8s 0 transport_latency_assumed market_resolved h 734 106 19ms 67ms 217ms 29.5s 0 transport_latency_assumed new_market c 1,352 708 111ms 15.9s 45.6s 1.1h 0 transport_latency_assumed new_market e 1,350 287 200ms 19.2s 27.2s 1.4min 0 transport_latency_assumed new_market f 1,350 376 155ms 14.6s 30.4s 2.0min 0 transport_latency_assumed new_market g 1,350 96 360ms 13.8s 33.7s 2.0min 0 transport_latency_assumed new_market h 1,350 517 161ms 17.3s 27.1s 31.6s 0 transport_latency_assumed price_change c 88,905,064 82,932,878 6ms 18ms 222ms 11.1s 0 transport_latency_assumed price_change e 102,100,124 1,010,688 40ms 65ms 664ms 13.4s 0 transport_latency_assumed price_change f 102,049,900 386,224 48ms 74ms 484ms 20.5s 0 transport_latency_assumed price_change g 101,885,432 30,768 83ms 149ms 1.3s 28.9s 0 transport_latency_assumed price_change h 102,116,988 17,808,126 18ms 34ms 327ms 47.9s 0 transport_latency_assumed tick_size_change c 2,964 2,744 6ms 21ms 402ms 781ms 0 transport_latency_assumed tick_size_change e 3,212 28 40ms 100ms 545ms 784ms 0 transport_latency_assumed tick_size_change f 3,212 16 47ms 77ms 655ms 1.6s 0 transport_latency_assumed tick_size_change g 3,212 not meas. 83ms 181ms 1.2s 1.5s 0 transport_latency_assumed tick_size_change h 3,212 424 18ms 35ms 2.2s 27.3s 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-10/13/2026-09-10T13.parquet sha256sum 2026-09-10T13.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.