Hour audit: 2026-09-02T20
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-02T20 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-02T20:00:00.005783995+00:00 · last event 2026-09-02T20:59:59.999996389+00:00
VOLUME 111,043,047 rows · 1,194,833,460 bytes (1.11 GiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured c: 109,346,292 · h: 109,344,953 · e: 108,565,273 · b: 91,592,337 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 219,224 (0.20%) · h: 1,100,880 (0.99%) · e: 108,554,970 (97.76%) · b: 1,167,973 (1.05%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 111,043,047 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 341e04ba407fae9a5a9279d8b8498f8bd84f81459566ffb2fc958bc7fcdebe7a
the corpus checksum ledger names this file with the same digest
joined 111,061,959 to merged 111,043,047, minus 18,912 (minus 0.0170%)
boundary drops 18,912 · 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-02T22:40:24Z as bceh
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,647,556 136,291,860 0-44 b879e4dd29c43bc6f88b144cd1f06f0b625327c8715d70774a07ded2305175c2 book 2,156,078 100,146,725 45-53 2da074285a8ca53f36c4ab572ce994bd5e276de2a501c414deb1b118c759cc71 last_trade_price 60,350 3,454,519 54-54 a2f1bbeb571feb467f5c3e7d975d886205da619c164e046a978724489a42748c market_resolved 1,668 207,356 55-55 3cfa26566b754c37153dd99f753c464e6d481ded6c0191eda063b1d5176cf433 new_market 10,514 889,886 56-56 acac818ff917b3c8779df1849a17344ab3276e996a1de5f5a0c19666f0938460 price_change 97,158,481 952,267,369 57-427 88d55841596c65dec0191f0ab9e0e5257ac8f0b3d846dc70efea49da49a46de3 tick_size_change 8,400 311,107 428-428 6e677413de45121f32b6542c558780e9910918ade9b846bdf9398cf0213226b6 EVENT MIX count share price_change 97,158,481 87.50% best_bid_ask 11,647,556 10.49% book 2,156,078 1.94% last_trade_price 60,350 0.05% new_market 10,514 <0.01% tick_size_change 8,400 <0.01% market_resolved 1,668 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,649,169 11,647,556 1,613 3,880 FULL book 2,160,150 2,156,078 4,072 89,224 FULL last_trade_price 60,357 60,350 7 341 FULL market_resolved 1,668 1,668 0 69 FULL new_market 10,542 10,514 28 174 FULL price_change 97,171,673 97,158,481 13,192 1,714 FULL tick_size_change 8,400 8,400 0 436 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 9,711,306 230 55ms 168ms 823ms 24.2s 0 transport_latency_assumed best_bid_ask c 11,643,810 7,167 5ms 21ms 395ms 4.0s 0 transport_latency_assumed best_bid_ask e 11,597,880 11,596,998 43ms 234ms 1.8s 58.2s 0 transport_latency_assumed best_bid_ask h 11,632,291 43,161 18ms 61ms 836ms 1.5min 0 transport_latency_assumed book b 1,701,940 1,162,913 3.5min 6.1h 31.3d 95.9d 0 book_staleness book c 494,691 201,112 1.2min 2.9h 25.9d 95.9d 0 book_staleness book e 522,598 521,274 1.5min 3.2h 26.1d 95.9d 0 book_staleness book h 525,848 270,779 1.4min 3.0h 26.9d 95.9d 0 book_staleness last_trade_price b 47,300 1 86ms 1.8s 11.8s 26.3s 0 transport_latency_assumed last_trade_price c 60,295 8 11ms 83ms 491ms 5.0s 0 transport_latency_assumed last_trade_price e 56,059 56,056 74ms 2.3s 11.9s 51.1s 0 transport_latency_assumed last_trade_price h 60,254 4,285 30ms 363ms 2.5s 38.0s 0 transport_latency_assumed market_resolved b 1,446 403 67ms 11.2min 17.9min 19.8min 0 transport_latency_assumed market_resolved c 1,257 1 5ms 34ms 58.1s 1.0min 0 transport_latency_assumed market_resolved e 1,256 1,256 44ms 512ms 58.6s 1.0min 0 transport_latency_assumed market_resolved h 1,256 8 19ms 153ms 55.1s 58.1s 0 transport_latency_assumed new_market b 7,374 2,324 534ms 7.9min 13.6min 15.8min 0 transport_latency_assumed new_market c 5,514 914 102ms 1.4min 3.8min 4.8min 0 transport_latency_assumed new_market e 5,489 5,489 152ms 1.3min 4.2min 5.1min 0 transport_latency_assumed new_market h 5,514 1,787 208ms 1.5min 4.6min 5.3min 0 transport_latency_assumed price_change b 80,116,315 2,102 55ms 202ms 1.6s 30.9s 0 transport_latency_assumed price_change c 97,132,325 10,022 5ms 21ms 390ms 6.8s 0 transport_latency_assumed price_change e 96,373,591 96,365,497 43ms 289ms 4.1s 58.3s 0 transport_latency_assumed price_change h 97,111,390 780,860 18ms 66ms 929ms 1.5min 0 transport_latency_assumed tick_size_change b 6,656 not meas. 55ms 131ms 424ms 811ms 0 transport_latency_assumed tick_size_change c 8,400 not meas. 5ms 9ms 93ms 492ms 0 transport_latency_assumed tick_size_change e 8,400 8,400 46ms 191ms 545ms 11.5s 0 transport_latency_assumed tick_size_change h 8,400 not meas. 18ms 39ms 266ms 39.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-02/20/2026-09-02T20.parquet sha256sum 2026-09-02T20.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.