Hour audit: 2026-09-22T10
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-22T10 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-22T10:00:00.000101587+00:00 · last event 2026-09-22T10:59:59.999991131+00:00
VOLUME 104,354,165 rows · 1,105,964,949 bytes (1.03 GiB) · 7 products, all holding rows
WITNESSES cefhi — 5 machines contributed rows
captured c: 104,208,963 · f: 104,064,372 · h: 104,050,801 · e: 103,945,969 · i: 103,084,362 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 97,942,808 (93.86%) · f: 94,466 (0.09%) · h: 3,886,094 (3.72%) · e: 194,178 (0.19%) · i: 2,236,619 (2.14%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 dcd2af5ec8f1374a567789bfba1097143c09375469b530ce6020dcac88c33780
the corpus checksum ledger names this file with the same digest
joined 104,355,293 to merged 104,354,165, minus 1,128 (minus 0.0011%)
boundary drops 1,128 · 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-22T12:01:15Z as cefhi
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,412,473 101,761,665 0-32 f24321b324cb42ee270030dec60e1faa07974ce09fbcf2c5fff9f0fde21020cb book 327,470 29,611,440 33-34 dadadbafc3b87bd2792e0c4923d9ce1c8ac9e6e2433190ee240791ad7ce7af1b last_trade_price 55,685 3,172,716 35-35 23b713a46683af578f8eeb84f35f9bfcfe050fba1aaba1c95a41925a1f37f7bd market_resolved 1,024 158,897 36-36 36b21791ba1b93a4baa1649657b4f380bcb9f36ab06f18dfe2602762f72a016b new_market 3,213 309,948 37-37 4f37eb31631266c3f0c88aed74178af2c71236d208903a4efa11a3f3415f5ce1 price_change 95,550,072 969,604,407 38-402 2ab189216a4c3230a63396f2746513bda981f1188330df9e8dd06e59e92a27ed tick_size_change 4,228 153,458 403-403 35576481174d64a85a77a265ea0a3a735015d48c057341aab4acf0574a0f54f0 EVENT MIX count share price_change 95,550,072 91.56% best_bid_ask 8,412,473 8.06% book 327,470 0.31% last_trade_price 55,685 0.05% tick_size_change 4,228 <0.01% new_market 3,213 <0.01% market_resolved 1,024 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,412,561 8,412,473 88 637 FULL book 327,498 327,470 28 68,923 FULL last_trade_price 55,685 55,685 0 1 FULL market_resolved 1,024 1,024 0 5 FULL new_market 3,213 3,213 0 0 FULL price_change 95,551,084 95,550,072 1,012 136 FULL tick_size_change 4,228 4,228 0 5 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,409,220 7,915,930 5ms 14ms 175ms 7.1s 0 transport_latency_assumed best_bid_ask e 8,402,881 12,627 41ms 58ms 336ms 14.5s 0 transport_latency_assumed best_bid_ask f 8,406,770 5,190 48ms 67ms 345ms 19.1s 0 transport_latency_assumed best_bid_ask h 8,405,924 298,365 19ms 35ms 293ms 57.6s 0 transport_latency_assumed best_bid_ask i 8,368,064 180,361 24ms 39ms 235ms 7.7s 0 transport_latency_assumed book c 217,295 204,708 108ms 13.6h 30.8d 115.5d 0 book_staleness book e 136,549 22,181 47ms 4.7min 15.0d 115.5d 0 book_staleness book f 134,193 18,359 54ms 2.7min 12.0d 97.0d 0 book_staleness book h 124,571 15,423 23ms 512ms 1.6d 97.0d 0 book_staleness book i 176,094 66,799 76ms 17.4min 13.7d 115.5d 0 book_staleness last_trade_price c 55,582 51,900 6ms 24ms 260ms 5.3s 0 transport_latency_assumed last_trade_price e 54,829 139 44ms 340ms 3.1s 14.5s 0 transport_latency_assumed last_trade_price f 55,339 65 52ms 314ms 7.4s 19.0s 0 transport_latency_assumed last_trade_price h 55,380 2,571 20ms 74ms 556ms 36.9s 0 transport_latency_assumed last_trade_price i 52,571 1,010 25ms 198ms 1.6s 7.7s 0 transport_latency_assumed market_resolved c 974 881 5ms 34ms 52.8s 55.5s 0 transport_latency_assumed market_resolved e 974 82 42ms 443ms 57.8s 1.6min 0 transport_latency_assumed market_resolved f 974 7 49ms 483ms 58.0s 1.0min 0 transport_latency_assumed market_resolved h 974 19 19ms 319ms 46.9s 1.0min 0 transport_latency_assumed market_resolved i 969 35 24ms 144ms 59.9s 1.0min 0 transport_latency_assumed new_market c 1,994 951 120ms 24.1s 40.8s 2.0min 0 transport_latency_assumed new_market e 1,994 600 184ms 25.8s 46.5s 1.9min 0 transport_latency_assumed new_market f 1,994 274 216ms 26.5s 40.9s 1.8min 0 transport_latency_assumed new_market h 1,994 696 168ms 24.5s 39.3s 1.9min 0 transport_latency_assumed new_market i 1,994 692 131ms 27.2s 47.6s 1.5min 0 transport_latency_assumed price_change c 95,519,670 89,764,408 5ms 16ms 186ms 7.3s 0 transport_latency_assumed price_change e 95,344,514 158,538 42ms 76ms 650ms 14.5s 0 transport_latency_assumed price_change f 95,460,874 70,568 49ms 83ms 561ms 19.2s 0 transport_latency_assumed price_change h 95,457,730 3,568,932 19ms 40ms 322ms 58.4s 0 transport_latency_assumed price_change i 94,480,462 1,987,626 24ms 50ms 648ms 7.8s 0 transport_latency_assumed tick_size_change c 4,228 4,030 5ms 13ms 148ms 321ms 0 transport_latency_assumed tick_size_change e 4,228 11 41ms 90ms 282ms 1.1s 0 transport_latency_assumed tick_size_change f 4,228 3 48ms 59ms 207ms 765ms 0 transport_latency_assumed tick_size_change h 4,228 88 19ms 38ms 314ms 3.4s 0 transport_latency_assumed tick_size_change i 4,208 96 24ms 47ms 119ms 377ms 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/10/2026-09-22T10.parquet sha256sum 2026-09-22T10.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.