Hour audit: 2026-09-10T05
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-10T05 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-10T05:00:00.000001663+00:00 · last event 2026-09-10T05:59:59.999673674+00:00
VOLUME 102,248,445 rows · 999,771,325 bytes (953.46 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 102,225,064 · f: 102,192,087 · h: 102,170,870 · e: 102,157,705 · g: 102,151,357 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 98,580,460 (96.41%) · f: 138,951 (0.14%) · h: 3,162,887 (3.09%) · e: 340,311 (0.33%) · g: 25,836 (0.03%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 102,248,445 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 a39ac48b65712d55c5187ccc17b74f0f094c09f1344d5f7af871d9c12c268b7e
the corpus checksum ledger names this file with the same digest
joined 102,251,516 to merged 102,248,445, minus 3,071 (minus 0.0030%)
boundary drops 3,071 · 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-10T06:58:42Z 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,613,916 106,717,900 0-36 424ab883203a190c848c2f30458c54183daa63ed331445c6298ac7818937e982 book 155,671 14,318,732 37-37 6f6d2755970cf1d8ca202668e95c3faf30c876a30e29eb78bc6b04f5b68133a3 last_trade_price 62,229 3,411,862 38-38 e1d3ab730930448464bda50f54a6f3e2ba4c9a309c24f416826748aa2b7b62b4 market_resolved 1,362 221,052 39-39 7175364c1ec258d3caa9aeca1ec0e37caedc5a5fede92b5c360cc205076650f0 new_market 1,387 151,254 40-40 6a0898327ca2ab869d537a21b0c7c0effc2e5d3a2c493cc2f0a48b53f39a1a98 price_change 92,411,696 873,703,939 41-393 b4bfd869145cd07b6e2e6ecdf7b62e55887acfa2a11ff1e1183c224f2c830533 tick_size_change 2,184 80,810 394-394 d377452dbf5533df70b9a29621f75cee8e2b2a91969b81ff1b5310f71f2d27b5 EVENT MIX count share price_change 92,411,696 90.38% best_bid_ask 9,613,916 9.40% book 155,671 0.15% last_trade_price 62,229 0.06% tick_size_change 2,184 <0.01% new_market 1,387 <0.01% market_resolved 1,362 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,614,179 9,613,916 263 142 FULL book 155,675 155,671 4 10,048 FULL last_trade_price 62,229 62,229 0 0 FULL market_resolved 1,362 1,362 0 1 FULL new_market 1,387 1,387 0 0 FULL price_change 92,414,500 92,411,696 2,804 127 FULL tick_size_change 2,184 2,184 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,613,672 9,274,304 5ms 9ms 100ms 4.2s 0 transport_latency_assumed best_bid_ask e 9,612,351 32,332 40ms 45ms 147ms 4.2s 0 transport_latency_assumed best_bid_ask f 9,611,964 13,076 45ms 52ms 162ms 33.6s 0 transport_latency_assumed best_bid_ask g 9,610,399 1,049 77ms 100ms 329ms 32.7s 0 transport_latency_assumed best_bid_ask h 9,612,624 293,155 17ms 23ms 149ms 16.6s 0 transport_latency_assumed book c 136,625 130,217 6ms 32ms 2.6h 84.8d 0 book_staleness book e 134,024 2,884 42ms 115ms 1.1min 84.8d 0 book_staleness book f 133,621 2,037 47ms 118ms 16.8s 101.7d 0 book_staleness book g 146,582 14,724 90ms 4.4s 1.0d 84.8d 0 book_staleness book h 133,302 5,809 20ms 60ms 2.9s 84.8d 0 book_staleness last_trade_price c 62,133 59,589 9ms 39ms 176ms 5.0s 0 transport_latency_assumed last_trade_price e 62,076 407 46ms 103ms 830ms 5.0s 0 transport_latency_assumed last_trade_price f 62,005 130 52ms 110ms 520ms 33.5s 0 transport_latency_assumed last_trade_price g 61,913 23 93ms 206ms 2.4s 32.8s 0 transport_latency_assumed last_trade_price h 62,071 2,080 23ms 67ms 329ms 16.5s 0 transport_latency_assumed market_resolved c 1,362 1,329 5ms 10ms 65ms 276ms 0 transport_latency_assumed market_resolved e 1,362 not meas. 43ms 120ms 290ms 665ms 0 transport_latency_assumed market_resolved f 1,361 2 50ms 128ms 351ms 1.3s 0 transport_latency_assumed market_resolved g 1,362 not meas. 90ms 246ms 535ms 965ms 0 transport_latency_assumed market_resolved h 1,362 31 25ms 56ms 151ms 3.8s 0 transport_latency_assumed new_market c 988 580 90ms 21.4s 58.5s 13.8min 0 transport_latency_assumed new_market e 988 188 134ms 11.1s 58.0s 1.2min 0 transport_latency_assumed new_market f 988 208 142ms 13.6s 1.0min 3.5min 0 transport_latency_assumed new_market g 988 100 231ms 24.6s 1.0min 1.2min 0 transport_latency_assumed new_market h 988 311 114ms 24.8s 59.9s 11.0min 0 transport_latency_assumed price_change c 92,408,100 89,112,313 5ms 10ms 102ms 4.9s 0 transport_latency_assumed price_change e 92,344,720 304,492 40ms 47ms 173ms 6.0s 0 transport_latency_assumed price_change f 92,379,964 123,498 45ms 54ms 198ms 34.2s 0 transport_latency_assumed price_change g 92,327,929 9,940 77ms 108ms 386ms 32.8s 0 transport_latency_assumed price_change h 92,358,339 2,861,453 18ms 25ms 156ms 16.9s 0 transport_latency_assumed tick_size_change c 2,184 2,128 5ms 7ms 69ms 1.1s 0 transport_latency_assumed tick_size_change e 2,184 8 39ms 44ms 105ms 119ms 0 transport_latency_assumed tick_size_change f 2,184 not meas. 45ms 49ms 122ms 261ms 0 transport_latency_assumed tick_size_change g 2,184 not meas. 76ms 96ms 396ms 560ms 0 transport_latency_assumed tick_size_change h 2,184 48 17ms 20ms 117ms 1.5s 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/05/2026-09-10T05.parquet sha256sum 2026-09-10T05.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.