Hour audit: 2026-09-07T12
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-07T12 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-07T12:00:00.000422425+00:00 · last event 2026-09-07T12:59:59.999606792+00:00
VOLUME 89,065,810 rows · 942,363,711 bytes (898.71 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured g: 88,598,655 · e: 88,497,835 · h: 88,437,742 · f: 88,411,558 · c: 85,098,011 (each machine's own feed; these overlap and do not sum to the file)
supplied g: 132,032 (0.15%) · e: 819,006 (0.92%) · h: 6,473,890 (7.27%) · f: 448,994 (0.50%) · c: 81,191,888 (91.16%) (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 89,065,810 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 d78be5a40ab6f258d48b9342a548317288c096446023cb5c9a928fa5f799ae7f
the corpus checksum ledger names this file with the same digest
joined 89,067,887 to merged 89,065,810, minus 2,077 (minus 0.0023%)
boundary drops 2,077 · 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-07T13:53:39Z 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 9,512,394 104,012,264 0-36 2202aabf0bc3f364da7542ecec6aa9411597ecb05abbfc206da56326fcb4fa89 book 518,575 53,309,769 37-38 d33d1b3cb38bb6f712ebe10420811f4b99f3a4f0a887a35710eefa9b1ad9070f last_trade_price 50,335 2,895,470 39-39 f41b2d751a5a329654105c841edda869c70120c08280d1f943fda04f73ee9a89 market_resolved 1,166 175,448 40-40 c13d8a63546fb2f53bdb04f56a7804e7a3278b77ffe8e5018dd6a22c942bd9e2 new_market 5,654 526,276 41-41 bdc358a7e12913259ed03ef5ba9dc943001370e253a3b03dc4ea4460050f5c1b price_change 78,975,086 780,331,414 42-343 d136b703f713a3dc58dbccd78a53b782dec8962eff9c44658e6d930aba38d4c1 tick_size_change 2,600 95,431 344-344 ca1a4dc1cf3f78f76410d891a466947a938ab95f3fe91f54be2a72d98560d5e5 EVENT MIX count share price_change 78,975,086 88.67% best_bid_ask 9,512,394 10.68% book 518,575 0.58% last_trade_price 50,335 0.06% new_market 5,654 <0.01% tick_size_change 2,600 <0.01% market_resolved 1,166 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,512,562 9,512,394 168 1,262 FULL book 519,117 518,575 542 172,229 FULL last_trade_price 50,336 50,335 1 77 FULL market_resolved 1,166 1,166 0 11 FULL new_market 5,654 5,654 0 28 FULL price_change 78,976,452 78,975,086 1,366 2,030 FULL tick_size_change 2,600 2,600 0 31 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,123,570 8,719,337 5ms 10ms 229ms 8.1s 0 transport_latency_assumed best_bid_ask e 9,506,036 88,595 39ms 51ms 363ms 13.8s 0 transport_latency_assumed best_bid_ask f 9,505,438 48,420 44ms 58ms 380ms 5.8s 0 transport_latency_assumed best_bid_ask g 9,502,644 5,646 80ms 130ms 770ms 39.6s 0 transport_latency_assumed best_bid_ask h 9,508,039 650,396 18ms 26ms 541ms 55.0s 0 transport_latency_assumed book c 466,945 418,366 3.8min 8.8h 29.9d 100.6d 0 book_staleness book e 121,784 10,527 43ms 10.6s 14.1h 100.6d 0 book_staleness book f 120,014 8,199 48ms 3.6s 13.2h 82.1d 0 book_staleness book g 190,117 69,644 671ms 2.3h 15.9d 100.6d 0 book_staleness book h 111,206 11,839 23ms 213ms 13.2min 82.0d 0 book_staleness last_trade_price c 47,864 45,318 10ms 51ms 329ms 6.9s 0 transport_latency_assumed last_trade_price e 50,068 562 46ms 250ms 3.6s 13.8s 0 transport_latency_assumed last_trade_price f 50,050 262 53ms 242ms 2.5s 6.1s 0 transport_latency_assumed last_trade_price g 49,632 34 96ms 593ms 15.4s 39.6s 0 transport_latency_assumed last_trade_price h 50,312 4,159 23ms 99ms 802ms 34.2s 0 transport_latency_assumed market_resolved c 1,110 1,042 5ms 141ms 6.1min 6.1min 0 transport_latency_assumed market_resolved e 1,082 22 40ms 271ms 6.4s 50.5s 0 transport_latency_assumed market_resolved f 1,082 5 46ms 276ms 4.7s 50.5s 0 transport_latency_assumed market_resolved g 1,082 11 85ms 413ms 1.1s 1.6s 0 transport_latency_assumed market_resolved h 1,082 86 18ms 111ms 5.3s 50.8s 0 transport_latency_assumed new_market c 3,644 2,027 226ms 4.4min 5.1min 1.6h 0 transport_latency_assumed new_market e 3,352 968 205ms 20.8s 46.2s 1.5min 0 transport_latency_assumed new_market f 3,352 475 240ms 21.0s 42.3s 1.2min 0 transport_latency_assumed new_market g 3,352 597 307ms 19.5s 30.5s 1.6min 0 transport_latency_assumed new_market h 3,352 1,587 166ms 17.7s 37.3s 1.6min 0 transport_latency_assumed price_change c 75,452,402 72,003,480 5ms 11ms 242ms 9.5s 0 transport_latency_assumed price_change e 78,812,913 718,300 40ms 68ms 475ms 13.9s 0 transport_latency_assumed price_change f 78,729,022 391,613 45ms 73ms 480ms 6.1s 0 transport_latency_assumed price_change g 78,849,228 56,100 81ms 174ms 1.2s 39.8s 0 transport_latency_assumed price_change h 78,761,151 5,805,593 18ms 30ms 503ms 58.2s 0 transport_latency_assumed tick_size_change c 2,476 2,318 5ms 17ms 166ms 401ms 0 transport_latency_assumed tick_size_change e 2,600 32 39ms 72ms 368ms 489ms 0 transport_latency_assumed tick_size_change f 2,600 20 45ms 91ms 283ms 641ms 0 transport_latency_assumed tick_size_change g 2,600 not meas. 80ms 198ms 567ms 13.7s 0 transport_latency_assumed tick_size_change h 2,600 230 18ms 31ms 243ms 2.4s 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-07/12/2026-09-07T12.parquet sha256sum 2026-09-07T12.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.