Hour audit: 2026-09-09T22
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-09T22 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-09T22:00:00.000027311+00:00 · last event 2026-09-09T22:59:59.999650194+00:00
VOLUME 112,690,593 rows · 1,191,649,025 bytes (1.11 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 110,603,057 · f: 110,597,394 · h: 110,592,874 · g: 110,589,317 · c: 87,644,624 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 2,257,140 (2.00%) · f: 491,913 (0.44%) · h: 25,891,360 (22.98%) · g: 91,043 (0.08%) · c: 83,959,137 (74.50%) (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 112,690,593 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 0a8c2f8391ad2f2ed75de3ec1566d7858376a822c47482f8ba4c560175a05096
the corpus checksum ledger names this file with the same digest
joined 112,694,700 to merged 112,690,593, minus 4,107 (minus 0.0036%)
boundary drops 4,107 · 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-10T00:35:35Z 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,647,274 120,057,321 0-40 a80d7fb10726d1945e16f5c7ca0ad89234b965b02129f4034943f4e9c88951ac book 2,102,390 89,452,517 41-49 2d3fff6a5707aefb99d709780e5a57fb5b7e25cb07409a73e9e2744041008072 last_trade_price 56,534 3,195,677 50-50 6734f2aac32625fbdfe0e45f36d116a1a730100a5301c7631b6f5374878809b4 market_resolved 3,797 397,806 51-51 b6a861ac483a89efdfaec2edb95f5487dea32eee25dbfe12c1e8e95d4c08e7b8 new_market 1,430 131,702 52-52 3586f0f82ba0f221ed1b64258e051ba9dfe058f9ccc4854cf63c2c3bebcd4bf5 price_change 99,875,684 977,002,285 53-433 08f5dc9b95e76e068ad74e15c4ad36bee159b2c9142d7b4a81e0087e8c345c10 tick_size_change 3,484 127,838 434-434 155a9d17ed446943138c4b99f863bd6514f87e231f9033b45e6f872a50636d37 EVENT MIX count share price_change 99,875,684 88.63% best_bid_ask 10,647,274 9.45% book 2,102,390 1.87% last_trade_price 56,534 0.05% market_resolved 3,797 <0.01% tick_size_change 3,484 <0.01% new_market 1,430 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,647,539 10,647,274 265 4,904 FULL book 2,102,982 2,102,390 592 199,293 FULL last_trade_price 56,535 56,534 1 553 FULL market_resolved 3,798 3,797 1 113 FULL new_market 1,430 1,430 0 69 FULL price_change 99,878,932 99,875,684 3,248 4,678 FULL tick_size_change 3,484 3,484 0 182 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,208,272 7,878,989 5ms 11ms 101ms 3.6s 0 transport_latency_assumed best_bid_ask e 10,645,762 210,942 40ms 50ms 189ms 5.1s 0 transport_latency_assumed best_bid_ask f 10,645,806 39,129 47ms 60ms 215ms 5.5s 0 transport_latency_assumed best_bid_ask g 10,644,281 4,597 83ms 113ms 540ms 12.8s 0 transport_latency_assumed best_bid_ask h 10,646,566 2,513,617 17ms 30ms 134ms 8.2s 0 transport_latency_assumed book c 2,068,278 2,057,173 27.5min 21.2h 32.2d 103.0d 0 book_staleness book e 122,809 6,542 44ms 556ms 5.1h 84.5d 0 book_staleness book f 120,953 4,241 50ms 389ms 1.6h 84.5d 0 book_staleness book g 138,734 9,782 93ms 4.4min 2.5d 84.5d 0 book_staleness book h 118,872 24,652 21ms 87ms 3.9s 84.3d 0 book_staleness last_trade_price c 44,200 42,276 10ms 42ms 184ms 5.0s 0 transport_latency_assumed last_trade_price e 56,438 1,277 54ms 240ms 3.3s 5.2s 0 transport_latency_assumed last_trade_price f 56,488 677 61ms 242ms 2.7s 5.5s 0 transport_latency_assumed last_trade_price g 56,473 238 97ms 231ms 2.7s 12.8s 0 transport_latency_assumed last_trade_price h 56,460 12,066 24ms 89ms 473ms 6.9s 0 transport_latency_assumed market_resolved c 3,225 3,173 9ms 16.8min 20.7min 21.0min 0 transport_latency_assumed market_resolved e 2,368 49 80ms 166ms 356ms 59.2s 0 transport_latency_assumed market_resolved f 2,368 9 99ms 187ms 377ms 914ms 0 transport_latency_assumed market_resolved g 2,368 1 119ms 287ms 860ms 1.9s 0 transport_latency_assumed market_resolved h 2,368 565 33ms 62ms 167ms 59.4s 0 transport_latency_assumed new_market c 1,034 698 123ms 10.2min 16.7min 16.8min 0 transport_latency_assumed new_market e 802 205 117ms 23.4s 1.4min 3.2min 0 transport_latency_assumed new_market f 802 157 158ms 29.6s 1.4min 1.8min 0 transport_latency_assumed new_market g 802 78 186ms 19.5s 1.4min 6.1min 0 transport_latency_assumed new_market h 802 292 92ms 19.0s 1.6min 5.6min 0 transport_latency_assumed price_change c 77,316,859 73,974,172 5ms 12ms 136ms 5.0s 0 transport_latency_assumed price_change e 99,771,394 2,038,092 41ms 59ms 385ms 5.2s 0 transport_latency_assumed price_change f 99,767,493 447,696 47ms 70ms 384ms 6.3s 0 transport_latency_assumed price_change g 99,743,175 76,347 84ms 125ms 633ms 13.6s 0 transport_latency_assumed price_change h 99,764,322 23,339,377 17ms 34ms 199ms 8.8s 0 transport_latency_assumed tick_size_change c 2,756 2,656 5ms 10ms 56ms 175ms 0 transport_latency_assumed tick_size_change e 3,484 33 40ms 46ms 122ms 269ms 0 transport_latency_assumed tick_size_change f 3,484 4 46ms 53ms 116ms 321ms 0 transport_latency_assumed tick_size_change g 3,484 not meas. 81ms 95ms 307ms 1.6s 0 transport_latency_assumed tick_size_change h 3,484 791 17ms 24ms 87ms 262ms 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-09/22/2026-09-09T22.parquet sha256sum 2026-09-09T22.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.