Hour audit: 2026-09-11T06
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-11T06 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-11T06:00:00.000008704+00:00 · last event 2026-09-11T06:59:59.999240032+00:00
VOLUME 100,519,816 rows · 1,006,567,898 bytes (959.94 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 100,362,508 · e: 100,331,904 · h: 100,318,559 · f: 100,311,741 · g: 100,283,204 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 96,983,091 (96.48%) · e: 380,857 (0.38%) · h: 2,915,526 (2.90%) · f: 175,504 (0.17%) · g: 64,838 (0.06%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 100,519,816 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 1d4f5919a2b049cff4f5f252ff14f997689794adc23d551aa8e92e9adbe05d1c
the corpus checksum ledger names this file with the same digest
joined 100,524,290 to merged 100,519,816, minus 4,474 (minus 0.0045%)
boundary drops 4,474 · 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-11T07:57:11Z 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 8,944,184 100,886,023 0-34 e3365523ec821f5443f6bb640d5134d067031e9c29085668b99eb845fcdc64d6 book 300,642 32,510,579 35-36 f3ddffcea6d95a4ec3cb9c9239adf2b7daa54bb2516e1cb9c02adc5d83321ca6 last_trade_price 44,135 2,589,958 37-37 074bdab0b560ed07530b81ba206522d550b45538ed3ead386028d85c16e13aa4 market_resolved 488 80,462 38-38 6ceeda73973e02930137318e9416878d6b9c4b77cf6342bcd4077b77cd34144c new_market 829 81,820 39-39 22912cd55e4d98234fdc688fa93268b143b25540f6e6e432be68455ce1425b30 price_change 91,227,678 869,199,050 40-388 a610e212bc0b1fd1c2bcf1d6379abf0fc548e35d66ba38ebd0a3d5cfcf13ebe3 tick_size_change 1,860 68,660 389-389 4e37ae232c6fe09a73871c0ddf003933d2c48d4ee4e83370df1cb1bbfc641d8f EVENT MIX count share price_change 91,227,678 90.76% best_bid_ask 8,944,184 8.90% book 300,642 0.30% last_trade_price 44,135 0.04% tick_size_change 1,860 <0.01% new_market 829 <0.01% market_resolved 488 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,944,387 8,944,184 203 112 FULL book 300,644 300,642 2 94,823 FULL last_trade_price 44,136 44,135 1 1 FULL market_resolved 488 488 0 0 FULL new_market 829 829 0 2 FULL price_change 91,231,946 91,227,678 4,268 98 FULL tick_size_change 1,860 1,860 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,943,785 8,673,545 5ms 8ms 80ms 2.8s 0 transport_latency_assumed best_bid_ask e 8,942,363 22,162 39ms 43ms 125ms 7.6s 0 transport_latency_assumed best_bid_ask f 8,942,824 7,982 44ms 50ms 142ms 6.3s 0 transport_latency_assumed best_bid_ask g 8,942,090 1,142 75ms 90ms 257ms 21.4s 0 transport_latency_assumed best_bid_ask h 8,943,228 239,353 16ms 21ms 102ms 16.5s 0 transport_latency_assumed book c 153,123 141,507 10ms 5.8h 16.5d 104.4d 0 book_staleness book e 157,272 54,762 69ms 7.0h 18.4d 104.4d 0 book_staleness book f 128,323 31,721 50ms 1.7h 5.7d 104.4d 0 book_staleness book g 138,758 39,566 90ms 3.8h 9.3d 104.4d 0 book_staleness book h 126,218 33,086 22ms 1.3h 5.7d 104.4d 0 book_staleness last_trade_price c 44,107 42,353 10ms 38ms 179ms 4.9s 0 transport_latency_assumed last_trade_price e 44,029 154 45ms 107ms 712ms 7.6s 0 transport_latency_assumed last_trade_price f 44,102 57 53ms 111ms 1.1s 6.4s 0 transport_latency_assumed last_trade_price g 43,956 13 88ms 198ms 1.1s 21.5s 0 transport_latency_assumed last_trade_price h 44,081 1,558 22ms 61ms 267ms 5.1s 0 transport_latency_assumed market_resolved c 474 452 5ms 11ms 51.8s 51.8s 0 transport_latency_assumed market_resolved e 474 1 42ms 195ms 52.2s 52.2s 0 transport_latency_assumed market_resolved f 474 1 49ms 198ms 52.2s 52.2s 0 transport_latency_assumed market_resolved g 474 9 89ms 349ms 686ms 1.0min 0 transport_latency_assumed market_resolved h 474 25 19ms 76ms 51.4s 1.0min 0 transport_latency_assumed new_market c 527 282 95ms 15.5s 1.4min 1.7min 0 transport_latency_assumed new_market e 526 174 126ms 21.0s 1.6min 1.8min 0 transport_latency_assumed new_market f 525 123 156ms 20.8s 1.4min 1.7min 0 transport_latency_assumed new_market g 526 56 241ms 33.8s 1.5min 2.0min 0 transport_latency_assumed new_market h 527 194 126ms 13.7s 1.5min 1.9min 0 transport_latency_assumed price_change c 91,218,632 88,123,150 5ms 9ms 140ms 8.1s 0 transport_latency_assumed price_change e 91,185,380 303,596 39ms 44ms 217ms 7.7s 0 transport_latency_assumed price_change f 91,193,633 135,620 44ms 52ms 233ms 6.4s 0 transport_latency_assumed price_change g 91,155,540 24,052 75ms 93ms 379ms 21.7s 0 transport_latency_assumed price_change h 91,202,171 2,641,260 17ms 24ms 174ms 17.8s 0 transport_latency_assumed tick_size_change c 1,860 1,802 5ms 8ms 106ms 259ms 0 transport_latency_assumed tick_size_change e 1,860 8 38ms 43ms 84ms 180ms 0 transport_latency_assumed tick_size_change f 1,860 not meas. 44ms 52ms 163ms 329ms 0 transport_latency_assumed tick_size_change g 1,860 not meas. 75ms 89ms 268ms 528ms 0 transport_latency_assumed tick_size_change h 1,860 50 17ms 20ms 166ms 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-11/06/2026-09-11T06.parquet sha256sum 2026-09-11T06.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.