Hour audit: 2026-09-11T00
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-11T00 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-11T00:00:00.000006249+00:00 · last event 2026-09-11T00:59:59.999989940+00:00
VOLUME 113,553,044 rows · 1,193,585,096 bytes (1.11 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 112,752,494 · e: 112,749,092 · h: 112,746,386 · g: 112,485,378 · c: 108,095,010 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 507,089 (0.45%) · e: 1,186,692 (1.05%) · h: 9,072,841 (7.99%) · g: 59,179 (0.05%) · c: 102,727,243 (90.47%) (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 113,553,044 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 e65cf1e158ead7df66e943afe66af0a0264edb86a15aa9fb1b5b540127bfd7df
the corpus checksum ledger names this file with the same digest
joined 113,555,640 to merged 113,553,044, minus 2,596 (minus 0.0023%)
boundary drops 2,596 · 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-11T01:59:21Z 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,419,286 125,666,762 0-43 cfbfd2c65b4bfcfa33516171954a049c82270a66b8135db745f647aa5fab563d book 1,041,530 80,026,260 44-47 32481b042916a2ebe15bdb1af7af71621133fcecc408f5cab463439f678ba2d7 last_trade_price 46,545 2,688,590 48-48 7d63205bdf7b5e989ed9ab2368a15e0633dc56cbd884fa057d5d8873e3301a77 market_resolved 347 55,931 49-49 2238b69b0331da8b0a5f96ff29957fea64d4065410ec319d8dc462adbc159ad5 new_market 1,078 110,193 50-50 54caf5c5b83c4748a5ee6a6a2b1219efc273b8660d0482b6b6a1c9deb2e427df price_change 101,041,842 983,655,593 51-436 515ae3e5d75cea0098bd743b8329b14562a0107e78236ed34152cbe85f58f2fe tick_size_change 2,416 90,019 437-437 eb502fc2c327cf4b029a59d0d72a3cdd78446b90ed18e47073579d2786892b4e EVENT MIX count share price_change 101,041,842 88.98% best_bid_ask 11,419,286 10.06% book 1,041,530 0.92% last_trade_price 46,545 0.04% tick_size_change 2,416 <0.01% new_market 1,078 <0.01% market_resolved 347 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,419,459 11,419,286 173 541 FULL book 1,041,540 1,041,530 10 200,781 FULL last_trade_price 46,546 46,545 1 100 FULL market_resolved 347 347 0 0 FULL new_market 1,078 1,078 0 0 FULL price_change 101,044,254 101,041,842 2,412 467 FULL tick_size_change 2,416 2,416 0 10 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,923,695 10,431,139 5ms 11ms 162ms 20.4s 0 transport_latency_assumed best_bid_ask e 11,414,896 98,071 39ms 47ms 192ms 6.7s 0 transport_latency_assumed best_bid_ask f 11,414,729 30,788 45ms 56ms 215ms 9.5s 0 transport_latency_assumed best_bid_ask g 11,416,109 3,620 79ms 97ms 364ms 15.3s 0 transport_latency_assumed best_bid_ask h 11,415,996 855,668 17ms 27ms 209ms 45.5s 0 transport_latency_assumed book c 615,255 592,774 8.9min 23.5h 29.2d 104.1d 0 book_staleness book e 455,631 151,684 6.2min 20.4h 26.4d 104.1d 0 book_staleness book f 425,936 135,361 5.5min 19.8h 26.4d 104.1d 0 book_staleness book g 107,073 6,156 84ms 3.2s 1.3d 104.1d 0 book_staleness book h 472,034 155,555 6.6min 20.6h 26.4d 104.1d 0 book_staleness last_trade_price c 43,560 41,113 10ms 43ms 250ms 6.7s 0 transport_latency_assumed last_trade_price e 46,412 497 47ms 108ms 637ms 6.7s 0 transport_latency_assumed last_trade_price f 46,473 209 53ms 130ms 648ms 9.4s 0 transport_latency_assumed last_trade_price g 46,378 26 91ms 210ms 2.1s 15.3s 0 transport_latency_assumed last_trade_price h 46,434 4,700 22ms 66ms 394ms 25.6s 0 transport_latency_assumed market_resolved c 324 317 5ms 14ms 4.0min 4.7min 0 transport_latency_assumed market_resolved e 324 3 43ms 192ms 44.5s 58.3s 0 transport_latency_assumed market_resolved f 324 not meas. 49ms 211ms 537ms 1.0min 0 transport_latency_assumed market_resolved g 324 not meas. 87ms 362ms 549ms 836ms 0 transport_latency_assumed market_resolved h 324 27 20ms 116ms 54.2s 58.8s 0 transport_latency_assumed new_market c 704 398 113ms 12.5s 23.2s 55.7s 0 transport_latency_assumed new_market e 704 210 192ms 15.1s 23.7s 53.9s 0 transport_latency_assumed new_market f 704 112 210ms 12.4s 24.6s 1.0min 0 transport_latency_assumed new_market g 704 67 316ms 12.7s 24.2s 54.4s 0 transport_latency_assumed new_market h 704 291 147ms 15.2s 23.7s 54.1s 0 transport_latency_assumed price_change c 96,509,092 91,659,318 5ms 13ms 268ms 27.1s 0 transport_latency_assumed price_change e 100,828,709 936,199 40ms 52ms 333ms 6.7s 0 transport_latency_assumed price_change f 100,861,916 340,617 46ms 63ms 361ms 9.8s 0 transport_latency_assumed price_change g 100,912,374 49,306 79ms 108ms 560ms 15.3s 0 transport_latency_assumed price_change h 100,808,478 8,056,402 17ms 32ms 335ms 47.5s 0 transport_latency_assumed tick_size_change c 2,380 2,184 5ms 11ms 565ms 626ms 0 transport_latency_assumed tick_size_change e 2,416 28 40ms 121ms 466ms 474ms 0 transport_latency_assumed tick_size_change f 2,412 2 45ms 52ms 103ms 213ms 0 transport_latency_assumed tick_size_change g 2,416 4 78ms 93ms 214ms 315ms 0 transport_latency_assumed tick_size_change h 2,416 198 17ms 42ms 89ms 653ms 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/00/2026-09-11T00.parquet sha256sum 2026-09-11T00.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.