Hour audit: 2026-09-08T03
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-08T03 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-08T03:00:00.000035901+00:00 · last event 2026-09-08T03:59:59.999656976+00:00
VOLUME 94,634,906 rows · 976,703,676 bytes (931.46 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 94,524,902 · c: 93,852,496 · e: 93,822,144 · g: 93,821,349 · f: 93,817,961 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 3,914,541 (4.14%) · c: 90,442,101 (95.57%) · e: 196,394 (0.21%) · g: 13,169 (0.01%) · f: 68,701 (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,634,906 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 61b69ab69bb3b27b261f6b526eb400f2f16a85318be36d3f8e34ed2dd89166c8
the corpus checksum ledger names this file with the same digest
joined 94,637,572 to merged 94,634,906, minus 2,666 (minus 0.0028%)
boundary drops 2,666 · 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-08T04:55:45Z 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 9,656,609 104,141,214 0-36 c1614d8bb14dbc1bd7ee3425d4bc2a9d36a8a93b0a4a8945b1c8bbe81fe96d5c book 888,838 60,985,273 37-40 1db187feb82def8e24d3c20e906660feb2ec813c2d94113270a6e9b884a63b64 last_trade_price 55,314 3,098,697 41-41 582b890dfc329b21b21a476eb1edcc7a17a332e3b32d33512b04dc5d14afa6f4 market_resolved 999 162,765 42-42 23288fe98d2136f4311cba7e9084b5bcd6f399f9254c95ee9ee750a29dd53192 new_market 1,120 118,932 43-43 2a937b3dc0f67106dba8c3ac3457f156e910279cf531d3990de4d160b8996cec price_change 84,029,278 807,017,603 44-364 6a2f56e22e8e22de8386c4f572e2ef6095a7fa90fd89e2037a730f11ccf53dd3 tick_size_change 2,748 98,992 365-365 be708fd55e742e41eb659b45a3cde6a322f9ea9c8a746d53a613281ef47ebd94 EVENT MIX count share price_change 84,029,278 88.79% best_bid_ask 9,656,609 10.20% book 888,838 0.94% last_trade_price 55,314 0.06% tick_size_change 2,748 <0.01% new_market 1,120 <0.01% market_resolved 999 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,656,809 9,656,609 200 114 FULL book 888,844 888,838 6 177,873 FULL last_trade_price 55,314 55,314 0 3 FULL market_resolved 999 999 0 0 FULL new_market 1,120 1,120 0 0 FULL price_change 84,031,738 84,029,278 2,460 251 FULL tick_size_change 2,748 2,748 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,656,201 9,326,394 4ms 8ms 69ms 3.4s 0 transport_latency_assumed best_bid_ask e 9,655,384 19,652 38ms 42ms 123ms 4.4s 0 transport_latency_assumed best_bid_ask f 9,655,266 7,146 47ms 53ms 142ms 5.5s 0 transport_latency_assumed best_bid_ask g 9,654,700 615 80ms 99ms 279ms 18.1s 0 transport_latency_assumed best_bid_ask h 9,645,356 302,802 16ms 20ms 110ms 9.9s 0 transport_latency_assumed book c 117,130 108,937 6ms 24ms 57.9min 82.7d 0 book_staleness book e 115,352 1,193 39ms 85ms 2.8s 41.4d 0 book_staleness book f 115,086 861 49ms 93ms 2.6s 82.6d 0 book_staleness book g 125,600 6,781 87ms 2.2s 16.9h 101.2d 0 book_staleness book h 882,437 771,066 12.5min 16.6h 30.6d 101.2d 0 book_staleness last_trade_price c 55,203 52,370 9ms 37ms 186ms 5.0s 0 transport_latency_assumed last_trade_price e 55,288 171 43ms 88ms 795ms 5.1s 0 transport_latency_assumed last_trade_price f 55,288 63 53ms 96ms 673ms 5.6s 0 transport_latency_assumed last_trade_price g 55,259 8 95ms 167ms 2.5s 18.4s 0 transport_latency_assumed last_trade_price h 55,243 2,702 21ms 50ms 271ms 6.6s 0 transport_latency_assumed market_resolved c 977 956 4ms 7ms 41ms 256ms 0 transport_latency_assumed market_resolved e 977 19 39ms 127ms 59.4s 1.0min 0 transport_latency_assumed market_resolved f 977 not meas. 49ms 187ms 59.6s 1.0min 0 transport_latency_assumed market_resolved g 977 not meas. 85ms 258ms 60.0s 1.0min 0 transport_latency_assumed market_resolved h 977 24 17ms 48ms 215ms 3.7s 0 transport_latency_assumed new_market c 775 404 76ms 17.3s 53.2s 1.0min 0 transport_latency_assumed new_market e 775 133 122ms 19.7s 52.5s 1.0min 0 transport_latency_assumed new_market f 775 163 167ms 34.5s 1.0min 1.7min 0 transport_latency_assumed new_market g 775 67 212ms 33.3s 58.4s 1.1min 0 transport_latency_assumed new_market h 775 353 96ms 30.4s 55.9s 1.1min 0 transport_latency_assumed price_change c 84,019,462 80,950,368 4ms 8ms 75ms 3.6s 0 transport_latency_assumed price_change e 83,991,620 175,226 38ms 45ms 155ms 4.5s 0 transport_latency_assumed price_change f 83,987,821 60,468 48ms 55ms 176ms 5.7s 0 transport_latency_assumed price_change g 83,981,290 5,698 81ms 101ms 349ms 18.1s 0 transport_latency_assumed price_change h 83,937,366 2,837,518 16ms 21ms 118ms 9.9s 0 transport_latency_assumed tick_size_change c 2,748 2,672 4ms 7ms 35ms 237ms 0 transport_latency_assumed tick_size_change e 2,748 not meas. 38ms 42ms 103ms 120ms 0 transport_latency_assumed tick_size_change f 2,748 not meas. 48ms 61ms 120ms 143ms 0 transport_latency_assumed tick_size_change g 2,748 not meas. 80ms 97ms 199ms 239ms 0 transport_latency_assumed tick_size_change h 2,748 76 16ms 21ms 53ms 79ms 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-08/03/2026-09-08T03.parquet sha256sum 2026-09-08T03.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.