Hour audit: 2026-09-22T15
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.
1 finding
- a machine expected this hour contributed nothing. Of the 7 machines expected to be capturing this hour, 1 contributed no rows: j. The hour is still whole on minutes; it simply rests on 6 machines rather than 7.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-22T15 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-22T15:00:00.000050367+00:00 · last event 2026-09-22T15:59:59.999982867+00:00
VOLUME 116,704,065 rows · 1,300,156,176 bytes (1.21 GiB) · 7 products, all holding rows
WITNESSES cefhik — 6 machines contributed rows
captured c: 116,518,737 · k: 116,289,138 · h: 116,216,036 · f: 115,879,583 · e: 115,489,110 · i: 112,631,998 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 101,032,402 (86.57%) · k: 12,703,125 (10.88%) · h: 2,244,494 (1.92%) · f: 38,670 (0.03%) · e: 45,185 (0.04%) · i: 640,189 (0.55%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 116,704,065 rows exactly, so those pairs supplied none
7 expected (cefhijk), 1 contributed nothing: j
INTEGRITY sha256 9237d3768589c0801286256d0b29b0bb8f229854f2da71857675d5c905c850a6
the corpus checksum ledger names this file with the same digest
joined 116,706,311 to merged 116,704,065, minus 2,246 (minus 0.0019%)
boundary drops 2,246 · 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-22T23:43:42Z as cefhik
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 7/8 pass, 1 finding
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
FINDING a machine expected this hour contributed nothing
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 10,630,630 129,734,558 0-40 f40cddc290c3120830fe39b6cd0f0a35ccec268a4a2529325b3ba13a6f0498a4 book 570,391 44,351,788 41-43 92a01790d17c68dacfc8448ff3e0e4beed7651b6f2a08b820784eaf9c79ae862 last_trade_price 77,802 4,384,065 44-44 c9cd88785aef6275ac84c6c155f002a3f6ad97d9660ef4753b446303bb2f7286 market_resolved 942 142,667 45-45 90dde4e494992d7e356689d925a603d8191001d1f49673137345fcea5331dcbe new_market 600 64,779 46-46 fceb9fe36ddd1e511d1a71bce35f1b3710debf609bfb89b34ecc2d65f7f64d7f price_change 105,421,196 1,120,052,481 47-449 0c41ae81d40dff91047e8ff6b477a76ce4c3d12f2ea635040a0cce5e6d76f703 tick_size_change 2,504 92,651 450-450 eda111a0d3f87cf1b9620be4c50ae76bfba8a526c25b6421da34c3fe6b444a49 EVENT MIX count share price_change 105,421,196 90.33% best_bid_ask 10,630,630 9.11% book 570,391 0.49% last_trade_price 77,802 0.07% tick_size_change 2,504 <0.01% market_resolved 942 <0.01% new_market 600 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,630,770 10,630,630 140 72,148 PARTIAL book 571,396 570,391 1,005 107,600 PARTIAL last_trade_price 77,805 77,802 3 3,475 PARTIAL market_resolved 942 942 0 871 PARTIAL new_market 600 600 0 405 PARTIAL price_change 105,422,294 105,421,196 1,098 128,457 PARTIAL tick_size_change 2,504 2,504 0 626 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,626,405 9,299,767 6ms 18ms 110ms 3.4s 0 transport_latency_assumed best_bid_ask e 10,606,954 2,886 44ms 68ms 1.2s 16.4s 0 transport_latency_assumed best_bid_ask f 10,622,409 1,821 49ms 67ms 266ms 22.4s 0 transport_latency_assumed best_bid_ask h 10,628,280 180,455 18ms 32ms 119ms 7.7s 0 transport_latency_assumed best_bid_ask i 10,497,728 56,920 22ms 43ms 793ms 8.7s 0 transport_latency_assumed best_bid_ask k 10,629,754 1,088,781 12ms 22ms 87ms 1.8s 0 transport_latency_assumed book c 467,538 439,480 1.2min 1.2d 31.1d 115.7d 0 book_staleness book e 161,155 9,366 56ms 5.3s 23.9h 97.2d 0 book_staleness book f 163,813 9,625 59ms 8.0s 1.0d 115.7d 0 book_staleness book h 161,656 8,486 22ms 103ms 1.8h 97.2d 0 book_staleness book i 207,159 66,718 74ms 22.8h 23.9h 115.7d 0 book_staleness book k 177,409 36,716 15ms 29.9s 5.9d 115.7d 0 book_staleness last_trade_price c 77,486 65,987 7ms 28ms 194ms 3.0s 0 transport_latency_assumed last_trade_price e 75,239 29 59ms 2.5s 9.0s 16.4s 0 transport_latency_assumed last_trade_price f 75,489 61 60ms 2.7s 12.3s 22.4s 0 transport_latency_assumed last_trade_price h 77,542 1,698 20ms 69ms 395ms 4.6s 0 transport_latency_assumed last_trade_price i 69,721 337 24ms 741ms 4.0s 8.1s 0 transport_latency_assumed last_trade_price k 77,661 9,690 13ms 38ms 183ms 1.0s 0 transport_latency_assumed market_resolved c 871 627 7ms 50.2s 55.3s 55.4s 0 transport_latency_assumed market_resolved e 871 not meas. 47ms 48.5s 53.4s 1.0min 0 transport_latency_assumed market_resolved f 871 21 51ms 44.6s 1.0min 1.0min 0 transport_latency_assumed market_resolved h 871 179 20ms 42.0s 47.8s 55.1s 0 transport_latency_assumed market_resolved i 871 42 23ms 53.5s 1.5min 1.5min 0 transport_latency_assumed market_resolved k 871 73 14ms 49.7s 54.9s 54.9s 0 transport_latency_assumed new_market c 405 184 57ms 13.5s 21.8s 1.2min 0 transport_latency_assumed new_market e 405 46 164ms 13.1s 1.2min 1.7min 0 transport_latency_assumed new_market f 405 26 163ms 12.1s 49.7s 1.6min 0 transport_latency_assumed new_market h 405 104 77ms 11.4s 57.7s 1.7min 0 transport_latency_assumed new_market i 405 48 95ms 11.5s 22.0s 1.4min 0 transport_latency_assumed new_market k 405 192 53ms 12.3s 23.4s 1.7min 0 transport_latency_assumed price_change c 105,343,528 91,224,080 6ms 21ms 128ms 3.6s 0 transport_latency_assumed price_change e 104,641,982 32,858 45ms 125ms 6.0s 16.5s 0 transport_latency_assumed price_change f 105,014,092 27,116 50ms 101ms 4.2s 22.4s 0 transport_latency_assumed price_change h 105,344,780 2,053,558 19ms 38ms 175ms 8.1s 0 transport_latency_assumed price_change i 101,853,634 516,124 22ms 76ms 2.2s 8.8s 0 transport_latency_assumed price_change k 105,400,534 11,567,460 13ms 25ms 104ms 3.2s 0 transport_latency_assumed tick_size_change c 2,504 2,277 6ms 12ms 67ms 301ms 0 transport_latency_assumed tick_size_change e 2,504 not meas. 44ms 85ms 323ms 6.3s 0 transport_latency_assumed tick_size_change f 2,504 not meas. 49ms 61ms 164ms 247ms 0 transport_latency_assumed tick_size_change h 2,502 14 18ms 33ms 124ms 175ms 0 transport_latency_assumed tick_size_change i 2,480 not meas. 22ms 48ms 7.1s 7.4s 0 transport_latency_assumed tick_size_change k 2,504 213 12ms 18ms 78ms 186ms 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-22/15/2026-09-22T15.parquet sha256sum 2026-09-22T15.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.