Hour audit: 2026-09-10T16
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-10T16 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-10T16:00:00.000057876+00:00 · last event 2026-09-10T16:59:59.999755571+00:00
VOLUME 115,095,535 rows · 1,233,116,335 bytes (1.15 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured g: 113,742,733 · e: 113,729,916 · f: 113,720,193 · h: 113,714,557 · c: 91,913,182 (each machine's own feed; these overlap and do not sum to the file)
supplied g: 60,954 (0.05%) · e: 1,545,839 (1.34%) · f: 401,592 (0.35%) · h: 28,406,071 (24.68%) · c: 84,681,079 (73.57%) (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 115,095,535 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 fae7eae86a59b7d2f90ab0cc5d5e019191b1c219f705aaf6ea7e6c2c1a89484e
the corpus checksum ledger names this file with the same digest
joined 115,107,118 to merged 115,095,535, minus 11,583 (minus 0.0101%)
boundary drops 11,583 · 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-10T18:36:03Z 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 11,029,414 124,320,906 0-42 247350280827c70581bd134ca4fc1690a95370521dd900b79ece933cdb201219 book 1,362,937 80,375,712 43-48 d547176423622be30619f2d7bf7e9ffd40efb986612e0a30c8264ba98f8e42fb last_trade_price 65,222 3,660,118 49-49 d40c0e27f13a9bcdf8ec9ce077d1e8f61b360186d027d92978599a871f01bcce market_resolved 1,756 205,505 50-50 f441dee68ef02bcaaf8ee00bdd7cdda9cab474aa37e6b396952176869dbbefe0 new_market 2,034 182,967 51-51 7b5721db5caeb33300f2ad2c84388dfbfd780d5be591810f7cd5e75a0edaef16 price_change 102,630,828 1,022,935,549 52-443 803845fddb6a01b0a2b8ef02a6bda372ba089304918321b605130cbaf7cf0e75 tick_size_change 3,344 122,985 444-444 a7aa6f35740f4237c917acee8d86ca0f40e53a26e4bfa201244761071e280a4d EVENT MIX count share price_change 102,630,828 89.17% best_bid_ask 11,029,414 9.58% book 1,362,937 1.18% last_trade_price 65,222 0.06% tick_size_change 3,344 <0.01% new_market 2,034 <0.01% market_resolved 1,756 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,029,596 11,029,414 182 3,538 FULL book 1,371,713 1,362,937 8,776 194,603 FULL last_trade_price 65,222 65,222 0 401 FULL market_resolved 1,765 1,756 9 172 FULL new_market 2,036 2,034 2 16 FULL price_change 102,633,442 102,630,828 2,614 2,241 FULL tick_size_change 3,344 3,344 0 116 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,825,056 8,096,410 6ms 19ms 158ms 4.0s 0 transport_latency_assumed best_bid_ask e 11,027,162 145,826 39ms 48ms 189ms 9.2s 0 transport_latency_assumed best_bid_ask f 11,027,227 32,197 46ms 57ms 216ms 5.3s 0 transport_latency_assumed best_bid_ask g 11,025,808 2,408 79ms 99ms 386ms 12.2s 0 transport_latency_assumed best_bid_ask h 11,028,193 2,752,573 18ms 28ms 174ms 38.6s 0 transport_latency_assumed book c 1,327,943 1,302,195 14.2min 1.2d 29.9d 103.8d 0 book_staleness book e 138,482 5,339 42ms 188ms 52.1s 103.7d 0 book_staleness book f 137,586 2,147 49ms 169ms 2.9s 85.2d 0 book_staleness book g 160,654 16,127 91ms 3.4min 3.2d 103.7d 0 book_staleness book h 138,199 37,129 23ms 69ms 7.2s 85.1d 0 book_staleness last_trade_price c 49,786 45,615 11ms 57ms 316ms 5.0s 0 transport_latency_assumed last_trade_price e 65,133 959 51ms 172ms 1.3s 9.2s 0 transport_latency_assumed last_trade_price f 65,181 491 57ms 169ms 1.3s 5.3s 0 transport_latency_assumed last_trade_price g 65,060 48 96ms 300ms 4.0s 12.3s 0 transport_latency_assumed last_trade_price h 65,118 18,109 25ms 76ms 546ms 8.7s 0 transport_latency_assumed market_resolved c 1,352 1,270 9ms 12.5min 21.8min 22.7min 0 transport_latency_assumed market_resolved e 1,186 72 43ms 257ms 1.0min 1.0min 0 transport_latency_assumed market_resolved f 1,186 3 49ms 259ms 1.0min 1.0min 0 transport_latency_assumed market_resolved g 1,186 35 90ms 337ms 942ms 1.3s 0 transport_latency_assumed market_resolved h 1,186 376 20ms 92ms 58.7s 1.0min 0 transport_latency_assumed new_market c 1,652 1,096 161ms 10.6min 12.7min 17.9min 0 transport_latency_assumed new_market e 1,120 240 158ms 17.2s 46.2s 1.2min 0 transport_latency_assumed new_market f 1,120 177 175ms 16.7s 48.4s 1.6min 0 transport_latency_assumed new_market g 1,120 100 292ms 12.3s 47.9s 1.6min 0 transport_latency_assumed new_market h 1,120 421 114ms 426ms 37.0s 1.6min 0 transport_latency_assumed price_change c 81,704,509 75,231,784 6ms 20ms 163ms 5.1s 0 transport_latency_assumed price_change e 102,493,489 1,393,376 40ms 54ms 315ms 9.2s 0 transport_latency_assumed price_change f 102,484,549 366,568 47ms 65ms 332ms 5.3s 0 transport_latency_assumed price_change g 102,485,565 42,236 79ms 115ms 646ms 12.4s 0 transport_latency_assumed price_change h 102,477,397 25,596,864 19ms 31ms 217ms 40.3s 0 transport_latency_assumed tick_size_change c 2,884 2,709 6ms 14ms 83ms 135ms 0 transport_latency_assumed tick_size_change e 3,344 27 40ms 50ms 149ms 576ms 0 transport_latency_assumed tick_size_change f 3,344 9 46ms 53ms 168ms 680ms 0 transport_latency_assumed tick_size_change g 3,340 not meas. 79ms 95ms 236ms 1.1s 0 transport_latency_assumed tick_size_change h 3,344 599 18ms 27ms 61ms 160ms 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/16/2026-09-10T16.parquet sha256sum 2026-09-10T16.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.