Hour audit: 2026-09-16T16
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-16T16 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-16T16:00:00.000087327+00:00 · last event 2026-09-16T16:59:59.999988306+00:00
VOLUME 119,091,702 rows · 1,288,887,433 bytes (1.20 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 118,165,653 · e: 117,988,262 · f: 113,424,120 · g: 112,925,702 · c: 112,866,805 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 11,084,558 (9.31%) · e: 1,116,416 (0.94%) · f: 777,000 (0.65%) · g: 308,945 (0.26%) · c: 105,804,783 (88.84%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 119,091,702 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 d5985830ee84d1d735ffbd2d069b80d4e1dff49c4feddc8677fd0f544c76f2a3
the corpus checksum ledger names this file with the same digest
joined 119,094,191 to merged 119,091,702, minus 2,489 (minus 0.0021%)
boundary drops 2,489 · 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-16T18:00:11Z 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,853,632 130,209,985 0-41 730c231ac88635d587a724e5f67690c84fa7dcb166cb6b01346114958b9ce45b book 981,149 75,043,342 42-45 cc8f01545787387ee12c8c77b90b39609311ba9e2868c7586351482b72d91a34 last_trade_price 59,710 3,464,511 46-46 ac2f5be03d3f34d3cd47b3ea627f4734f1ac4bd2018c4f494ecc3dd011aaaa2e market_resolved 1,434 212,975 47-47 1d2a13d60a8627b60247667a3142ee42afdc4bad72a5e44dac3581695a3c4b3c new_market 2,735 270,807 48-48 fd9d8854973a240a77f0c8cdf6855df7e022c9d24f2481bc6beeb85348a6307f price_change 107,188,834 1,078,175,888 49-457 439166d8929848a87200507fdf2931c9a3103d9701f924e19876752d81a9d854 tick_size_change 4,208 155,695 458-458 15a3ccda2c9ee46223405d4b4c99667b9a5b53500cb01490747dbe0f1e799602 EVENT MIX count share price_change 107,188,834 90.01% best_bid_ask 10,853,632 9.11% book 981,149 0.82% last_trade_price 59,710 0.05% tick_size_change 4,208 <0.01% new_market 2,735 <0.01% market_resolved 1,434 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,853,932 10,853,632 300 1,202 FULL book 981,165 981,149 16 174,262 FULL last_trade_price 59,711 59,710 1 241 FULL market_resolved 1,434 1,434 0 56 FULL new_market 2,735 2,735 0 0 FULL price_change 107,191,006 107,188,834 2,172 282 FULL tick_size_change 4,208 4,208 0 139 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,291,635 9,673,637 5ms 17ms 158ms 4.1s 0 transport_latency_assumed best_bid_ask e 10,847,646 102,049 42ms 61ms 297ms 18.3s 0 transport_latency_assumed best_bid_ask f 10,413,379 52,601 44ms 65ms 312ms 15.9s 0 transport_latency_assumed best_bid_ask g 10,368,823 2,942 79ms 119ms 603ms 40.5s 0 transport_latency_assumed best_bid_ask h 10,850,294 1,022,403 19ms 36ms 262ms 36.7s 0 transport_latency_assumed book c 558,965 539,795 1.9min 17.0h 35.1d 109.8d 0 book_staleness book e 131,330 6,542 48ms 3.1s 24.8min 91.2d 0 book_staleness book f 509,443 156,450 1.9min 14.0h 34.9d 109.8d 0 book_staleness book g 515,861 261,552 1.8min 14.7h 34.9d 109.8d 0 book_staleness book h 131,496 16,810 25ms 284ms 18.2min 91.2d 0 book_staleness last_trade_price c 56,655 53,224 11ms 58ms 277ms 4.9s 0 transport_latency_assumed last_trade_price e 58,841 467 68ms 1.2s 11.1s 18.3s 0 transport_latency_assumed last_trade_price f 55,684 304 67ms 685ms 8.0s 15.9s 0 transport_latency_assumed last_trade_price g 54,575 41 115ms 2.5s 18.5s 40.5s 0 transport_latency_assumed last_trade_price h 59,364 5,674 28ms 143ms 752ms 8.4s 0 transport_latency_assumed market_resolved c 1,317 1,262 6ms 19ms 5.1min 5.8min 0 transport_latency_assumed market_resolved e 1,313 3 45ms 196ms 648ms 55.0s 0 transport_latency_assumed market_resolved f 1,321 75 48ms 254ms 5.2min 6.2min 0 transport_latency_assumed market_resolved g 1,273 17 89ms 329ms 913ms 2.1min 0 transport_latency_assumed market_resolved h 1,313 77 22ms 74ms 481ms 54.6s 0 transport_latency_assumed new_market c 1,736 1,091 91ms 21.4s 2.1min 4.6min 0 transport_latency_assumed new_market e 1,736 356 211ms 23.9s 1.6min 2.4min 0 transport_latency_assumed new_market f 1,742 289 211ms 23.0s 2.1min 5.0min 0 transport_latency_assumed new_market g 1,736 153 329ms 18.4s 1.7min 3.9min 0 transport_latency_assumed new_market h 1,736 846 126ms 21.9s 1.6min 2.4min 0 transport_latency_assumed price_change c 101,952,449 95,531,917 6ms 20ms 185ms 4.1s 0 transport_latency_assumed price_change e 106,943,188 1,006,986 42ms 89ms 2.0s 18.3s 0 transport_latency_assumed price_change f 102,438,687 567,268 44ms 89ms 1.3s 15.9s 0 transport_latency_assumed price_change g 101,979,398 44,240 81ms 182ms 4.1s 40.6s 0 transport_latency_assumed price_change h 107,117,242 10,038,423 19ms 43ms 388ms 37.0s 0 transport_latency_assumed tick_size_change c 4,048 3,857 6ms 13ms 70ms 191ms 0 transport_latency_assumed tick_size_change e 4,208 13 42ms 54ms 222ms 4.8s 0 transport_latency_assumed tick_size_change f 3,864 13 44ms 65ms 178ms 646ms 0 transport_latency_assumed tick_size_change g 4,036 not meas. 79ms 101ms 489ms 774ms 0 transport_latency_assumed tick_size_change h 4,208 325 19ms 31ms 72ms 305ms 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-16/16/2026-09-16T16.parquet sha256sum 2026-09-16T16.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.