Hour audit: 2026-09-11T18
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-11T18 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-11T18:00:00.000056854+00:00 · last event 2026-09-11T18:59:59.999963099+00:00
VOLUME 127,991,978 rows · 1,387,450,788 bytes (1.29 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured g: 125,147,999 · h: 125,056,312 · e: 125,027,617 · c: 88,988,271 · f: 33,773,490 (each machine's own feed; these overlap and do not sum to the file)
supplied g: 233,925 (0.18%) · h: 40,108,133 (31.34%) · e: 3,150,352 (2.46%) · c: 84,356,560 (65.91%) · f: 143,008 (0.11%) (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 127,991,978 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 e4a54bb6db125d504373238f617bc8e4bf715bbeb2b770ea41d5e0925a300cb4
the corpus checksum ledger names this file with the same digest
joined 127,996,297 to merged 127,991,978, minus 4,319 (minus 0.0034%)
boundary drops 4,319 · 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-12T05:03:12Z 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 12,339,362 140,786,315 0-47 16196cf9e95fc56c939a088cd7433a2dc098679dffb6736c6d384b67d6cd482e book 3,045,693 111,231,473 48-59 08ce3da9d41f61bde77eef0691b4a5be56f8dd068fefe4def4ba734d96cc7663 last_trade_price 65,959 3,756,908 60-60 8326697b52391eaa17045d33e66ab2c5db0fdc35f3838f00dae2865173c0bc00 market_resolved 2,283 163,230 61-61 94231583ab9a28f32d56d34b922ea35183ed41c5236026e1a8392ed1ee2c3760 new_market 2,711 187,970 62-62 2f7f5b7c68c917e3e790a1e500c39f1fdde87e56bf25fbea928aaaf4a8c9d3eb price_change 112,530,530 1,129,671,009 63-492 e535598f3c046457c956b18295a8111ed06f39d252abf42fbf9d9a14c5a49756 tick_size_change 5,440 196,555 493-493 85980cfb49b122c10eb45452bb67e682cea95b82f2d6e605d4c6aeee3e77f5c6 EVENT MIX count share price_change 112,530,530 87.92% best_bid_ask 12,339,362 9.64% book 3,045,693 2.38% last_trade_price 65,959 0.05% tick_size_change 5,440 <0.01% new_market 2,711 <0.01% market_resolved 2,283 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,339,598 12,339,362 236 27,283 FULL book 3,047,087 3,045,693 1,394 206,964 FULL last_trade_price 65,960 65,959 1 2,507 FULL market_resolved 2,283 2,283 0 535 FULL new_market 2,711 2,711 0 1,075 FULL price_change 112,533,218 112,530,530 2,688 24,710 FULL tick_size_change 5,440 5,440 0 1,150 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,565,121 8,112,354 5ms 14ms 120ms 3.7s 0 transport_latency_assumed best_bid_ask e 12,336,668 301,495 38ms 50ms 219ms 13.3s 0 transport_latency_assumed best_bid_ask f 3,538,653 13,194 45ms 64ms 238ms 2.4s 0 transport_latency_assumed best_bid_ask g 12,331,781 11,321 81ms 113ms 474ms 27.0s 0 transport_latency_assumed best_bid_ask h 12,338,419 3,900,998 19ms 34ms 252ms 54.8s 0 transport_latency_assumed book c 2,935,674 2,872,705 16.4min 1.2h 31.0d 104.9d 0 book_staleness book e 141,332 8,098 41ms 178ms 9.9min 86.3d 0 book_staleness book f 46,790 2,045 48ms 149ms 24.8min 86.3d 0 book_staleness book g 377,597 116,931 58.5s 47.1min 20.2d 104.9d 0 book_staleness book h 140,794 45,914 23ms 91ms 38.3s 104.9d 0 book_staleness last_trade_price c 43,870 41,246 11ms 50ms 248ms 5.0s 0 transport_latency_assumed last_trade_price e 65,627 2,265 47ms 150ms 1.3s 13.2s 0 transport_latency_assumed last_trade_price f 21,719 230 54ms 132ms 613ms 5.0s 0 transport_latency_assumed last_trade_price g 65,529 190 96ms 413ms 4.8s 27.3s 0 transport_latency_assumed last_trade_price h 65,835 22,028 26ms 92ms 470ms 9.2s 0 transport_latency_assumed market_resolved c 2,044 2,022 10.8min 25.4min 32.0min 33.5min 0 transport_latency_assumed market_resolved e 928 25 39ms 116ms 265ms 433ms 0 transport_latency_assumed market_resolved f 393 3 47ms 123ms 354ms 440ms 0 transport_latency_assumed market_resolved g 928 1 86ms 235ms 413ms 723ms 0 transport_latency_assumed market_resolved h 928 232 20ms 60ms 139ms 509ms 0 transport_latency_assumed new_market c 2,331 1,827 4.9min 12.5min 24.5min 33.9min 0 transport_latency_assumed new_market e 1,122 270 186ms 13.4s 29.9s 1.3min 0 transport_latency_assumed new_market f 47 6 62ms 195ms 13.4s 13.5s 0 transport_latency_assumed new_market g 1,122 134 285ms 13.5s 28.9s 1.0min 0 transport_latency_assumed new_market h 1,122 474 155ms 12.8s 27.4s 1.4min 0 transport_latency_assumed price_change c 77,435,403 73,322,753 5ms 15ms 127ms 9.6s 0 transport_latency_assumed price_change e 112,476,500 2,838,122 38ms 56ms 325ms 13.5s 0 transport_latency_assumed price_change f 30,164,568 127,522 46ms 68ms 312ms 2.6s 0 transport_latency_assumed price_change g 112,365,606 105,348 82ms 132ms 859ms 27.4s 0 transport_latency_assumed price_change h 112,503,774 36,136,785 19ms 37ms 291ms 55.0s 0 transport_latency_assumed tick_size_change c 3,828 3,653 5ms 12ms 59ms 116ms 0 transport_latency_assumed tick_size_change e 5,440 77 38ms 46ms 132ms 856ms 0 transport_latency_assumed tick_size_change f 1,320 8 46ms 61ms 95ms 313ms 0 transport_latency_assumed tick_size_change g 5,436 not meas. 81ms 99ms 279ms 2.0s 0 transport_latency_assumed tick_size_change h 5,440 1,702 19ms 28ms 70ms 471ms 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/18/2026-09-11T18.parquet sha256sum 2026-09-11T18.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.