Hour audit: 2026-09-09T17
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-09T17 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-09T17:00:00.000000098+00:00 · last event 2026-09-09T17:59:59.999512814+00:00
VOLUME 111,105,289 rows · 1,223,410,175 bytes (1.14 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 109,861,402 · g: 109,849,416 · e: 109,645,180 · f: 109,634,754 · c: 95,503,450 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 18,264,314 (16.44%) · g: 185,348 (0.17%) · e: 2,053,895 (1.85%) · f: 584,208 (0.53%) · c: 90,017,524 (81.02%) (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 111,105,289 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 8dfb68109ac3ecc9ea20dadf579caa0b9d53e04cb3f7d96c9bda3a782a252758
the corpus checksum ledger names this file with the same digest
joined 111,110,309 to merged 111,105,289, minus 5,020 (minus 0.0045%)
boundary drops 5,020 · 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-09T19:36:30Z 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,323,772 129,685,093 0-43 d579d190aaa0474af4ecdd592169031789f38355db5a96a8e9d0a6f79d3fcc8b book 1,578,990 88,054,922 44-50 d8bf7723f4127377d13add4a3a46e459513b21f0e5d76e1cc52feb4d244e9be8 last_trade_price 68,403 3,943,724 51-51 4fc56b69c7f53f866477b5f720491e76a85b191debe01980c22a9e052e8d3e5c market_resolved 1,109 126,344 52-52 fee2f6e9f0e838e45a4565335810d8d4361bc1e4cb95e1f6725dc2355c0cd42f new_market 2,999 278,762 53-53 99df809ade02983436ebf96d7471577ed23e068b0cca5be6b761f98f50422de9 price_change 98,125,632 999,891,562 54-428 7a78b231dfc2e47b9e67db07835b18cb940c1620b6ba10e90c73612dca3de8fc tick_size_change 4,384 161,586 429-429 34b2ac73a868e51bef18827083e7ae4beab452a6a8571ca2985eea47867e39f2 EVENT MIX count share price_change 98,125,632 88.32% best_bid_ask 11,323,772 10.19% book 1,578,990 1.42% last_trade_price 68,403 0.06% tick_size_change 4,384 <0.01% new_market 2,999 <0.01% market_resolved 1,109 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,324,007 11,323,772 235 3,398 FULL book 1,580,432 1,578,990 1,442 193,128 FULL last_trade_price 68,404 68,403 1 466 FULL market_resolved 1,109 1,109 0 1 FULL new_market 2,999 2,999 0 0 FULL price_change 98,128,974 98,125,632 3,342 1,781 FULL tick_size_change 4,384 4,384 0 71 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,777,549 9,243,326 5ms 14ms 169ms 9.6s 0 transport_latency_assumed best_bid_ask e 11,321,342 204,820 40ms 53ms 256ms 6.1s 0 transport_latency_assumed best_bid_ask f 11,320,919 55,242 45ms 62ms 276ms 5.4s 0 transport_latency_assumed best_bid_ask g 11,315,100 3,940 84ms 136ms 533ms 35.4s 0 transport_latency_assumed best_bid_ask h 11,318,788 1,816,444 17ms 34ms 285ms 43.3s 0 transport_latency_assumed book c 1,357,088 1,277,957 17.1min 21.3h 31.8d 102.8d 0 book_staleness book e 143,921 4,743 43ms 422ms 3.1s 84.3d 0 book_staleness book f 145,106 2,899 49ms 380ms 34.5s 84.3d 0 book_staleness book g 495,957 132,491 3.5min 13.2h 27.6d 102.8d 0 book_staleness book h 411,158 160,900 1.5min 11.6h 18.2d 102.8d 0 book_staleness last_trade_price c 56,944 53,199 11ms 52ms 284ms 4.9s 0 transport_latency_assumed last_trade_price e 68,293 1,356 56ms 330ms 2.3s 6.1s 0 transport_latency_assumed last_trade_price f 68,142 535 61ms 273ms 2.2s 5.4s 0 transport_latency_assumed last_trade_price g 67,619 182 103ms 483ms 6.8s 34.0s 0 transport_latency_assumed last_trade_price h 68,139 13,131 24ms 104ms 537ms 6.1s 0 transport_latency_assumed market_resolved c 971 929 7ms 8.5min 14.0min 15.2min 0 transport_latency_assumed market_resolved e 760 25 41ms 220ms 58.3s 1.0min 0 transport_latency_assumed market_resolved f 760 6 46ms 199ms 51.6s 53.6s 0 transport_latency_assumed market_resolved g 759 7 86ms 352ms 921ms 1.5s 0 transport_latency_assumed market_resolved h 760 142 18ms 116ms 55.2s 57.2s 0 transport_latency_assumed new_market c 2,033 1,119 145ms 6.1min 10.8min 10.9min 0 transport_latency_assumed new_market e 1,759 524 166ms 23.2s 1.3min 1.7min 0 transport_latency_assumed new_market f 1,759 350 164ms 26.3s 1.3min 1.7min 0 transport_latency_assumed new_market g 1,759 246 330ms 26.7s 1.2min 1.5min 0 transport_latency_assumed new_market h 1,759 760 137ms 25.8s 1.3min 1.7min 0 transport_latency_assumed price_change c 84,304,765 79,437,079 5ms 16ms 191ms 9.6s 0 transport_latency_assumed price_change e 98,104,721 1,842,384 40ms 66ms 422ms 6.1s 0 transport_latency_assumed price_change f 98,093,684 525,168 46ms 75ms 412ms 5.4s 0 transport_latency_assumed price_change g 97,963,838 48,482 85ms 162ms 925ms 35.4s 0 transport_latency_assumed price_change h 98,056,414 16,272,519 17ms 39ms 315ms 43.4s 0 transport_latency_assumed tick_size_change c 4,100 3,915 5ms 12ms 104ms 398ms 0 transport_latency_assumed tick_size_change e 4,384 43 40ms 45ms 197ms 437ms 0 transport_latency_assumed tick_size_change f 4,384 8 45ms 52ms 254ms 448ms 0 transport_latency_assumed tick_size_change g 4,384 not meas. 83ms 149ms 509ms 1.8s 0 transport_latency_assumed tick_size_change h 4,384 418 17ms 31ms 130ms 1.1s 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/17/2026-09-09T17.parquet sha256sum 2026-09-09T17.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.