Hour audit: 2026-09-22T21
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-22T21 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-22T21:00:00.000968814+00:00 · last event 2026-09-22T21:59:59.999743724+00:00
VOLUME 107,750,629 rows · 1,205,323,247 bytes (1.12 GiB) · 7 products, all holding rows
WITNESSES cfhik — 5 machines contributed rows
captured h: 105,969,932 · f: 105,753,919 · i: 102,597,414 · k: 101,321,366 · c: 87,226,694 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 6,171,384 (5.73%) · f: 248,711 (0.23%) · i: 4,610,269 (4.28%) · k: 20,201,909 (18.75%) · c: 76,518,356 (71.01%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 e3773140fc67bd06a85e83056bf1efd5ee703ed6cbb504665aaa833dcca7688e
the corpus checksum ledger names this file with the same digest
joined 107,753,246 to merged 107,750,629, minus 2,617 (minus 0.0024%)
boundary drops 2,617 · 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-23T01:39:59Z as cfhik
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 10,943,976 134,388,310 0-41 466548e319077689ebeb98f9fbb4d67d591cf4d7f55532d9a19eb5fadadfec86 book 2,023,153 89,364,406 42-49 bcc06487e9c3a79a0171b4f571511d471e6654f7bf9ca229b5b11bce59ce6f8d last_trade_price 49,261 2,868,029 50-50 7e40b8a84e14afb13f684c980cbffce304c55b46d6e3e051ee3777f7b3d939ba market_resolved 659 91,442 51-51 0b26b49cd0dfbb47caf698a7d9cc7fa03ef6a8443f01acd1e345e136a60a6681 new_market 10,926 1,063,386 52-52 bab4161878fa8d4a5712295a63cee19644f5b726aa613e20a2eb240983b3058b price_change 94,720,398 976,234,386 53-414 a5406f3bd70044ac59551bfe89ca02a3a361c61578617572d871aaab773d10cf tick_size_change 2,256 85,718 415-415 6d6b068427c4e264448a93f850cf40d617eab2de94bc9e9917778238328c7c41 EVENT MIX count share price_change 94,720,398 87.91% best_bid_ask 10,943,976 10.16% book 2,023,153 1.88% last_trade_price 49,261 0.05% new_market 10,926 0.01% tick_size_change 2,256 <0.01% market_resolved 659 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,943,979 10,943,976 3 5,559 FULL book 2,025,743 2,023,153 2,590 188,715 FULL last_trade_price 49,261 49,261 0 511 FULL market_resolved 659 659 0 45 FULL new_market 10,926 10,926 0 288 FULL price_change 94,720,422 94,720,398 24 5,558 FULL tick_size_change 2,256 2,256 0 101 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,847,758 7,779,160 5ms 26ms 227ms 4.8s 0 transport_latency_assumed best_bid_ask f 10,938,343 20,009 49ms 108ms 420ms 27.8s 0 transport_latency_assumed best_bid_ask h 10,937,402 631,838 18ms 50ms 546ms 53.6s 0 transport_latency_assumed best_bid_ask i 10,619,558 473,055 20ms 37ms 166ms 7.4s 0 transport_latency_assumed best_bid_ask k 10,412,535 2,039,914 12ms 35ms 246ms 52.0s 0 transport_latency_assumed book c 1,705,817 1,525,642 6.6min 3.3d 42.1d 116.0d 0 book_staleness book f 219,606 62,815 5.4s 21.4h 31.3d 115.9d 0 book_staleness book h 376,882 143,774 1.7min 1.2d 31.3d 116.0d 0 book_staleness book i 128,238 23,568 52ms 3.1min 6.7d 97.4d 0 book_staleness book k 595,568 267,354 3.5min 2.2d 38.5d 116.0d 0 book_staleness last_trade_price c 39,027 34,222 6ms 46ms 308ms 3.4s 0 transport_latency_assumed last_trade_price f 48,354 74 96ms 2.3s 11.9s 27.9s 0 transport_latency_assumed last_trade_price h 48,572 2,625 20ms 187ms 900ms 39.8s 0 transport_latency_assumed last_trade_price i 48,566 1,825 23ms 246ms 1.1s 3.7s 0 transport_latency_assumed last_trade_price k 47,085 10,515 14ms 89ms 352ms 26.0s 0 transport_latency_assumed market_resolved c 576 436 9ms 5.9min 10.2min 13.1min 0 transport_latency_assumed market_resolved f 546 1 70ms 632ms 36.1s 54.9s 0 transport_latency_assumed market_resolved h 546 38 27ms 249ms 34.7s 53.7s 0 transport_latency_assumed market_resolved i 532 58 25ms 314ms 1.5min 2.5min 0 transport_latency_assumed market_resolved k 542 126 32ms 51.2s 4.2min 4.2min 0 transport_latency_assumed new_market c 7,038 3,466 80ms 6.2min 12.6min 16.2min 0 transport_latency_assumed new_market f 6,764 894 140ms 2.8min 12.7min 16.1min 0 transport_latency_assumed new_market h 6,764 2,411 87ms 3.0min 13.2min 13.8d 0 transport_latency_assumed new_market i 6,764 2,306 91ms 2.8min 12.5min 13.8d 0 transport_latency_assumed new_market k 6,704 1,849 103ms 2.9min 14.7min 39.9min 0 transport_latency_assumed price_change c 76,624,554 67,173,682 5ms 30ms 235ms 5.8s 0 transport_latency_assumed price_change f 94,538,050 164,916 50ms 150ms 2.0s 28.0s 0 transport_latency_assumed price_change h 94,597,514 5,390,552 18ms 61ms 606ms 53.9s 0 transport_latency_assumed price_change i 91,791,588 4,109,396 20ms 49ms 261ms 8.0s 0 transport_latency_assumed price_change k 90,256,716 17,881,852 13ms 42ms 261ms 53.0s 0 transport_latency_assumed tick_size_change c 1,924 1,748 5ms 14ms 115ms 340ms 0 transport_latency_assumed tick_size_change f 2,256 2 49ms 128ms 503ms 662ms 0 transport_latency_assumed tick_size_change h 2,252 146 18ms 39ms 294ms 663ms 0 transport_latency_assumed tick_size_change i 2,168 61 20ms 36ms 149ms 204ms 0 transport_latency_assumed tick_size_change k 2,216 299 13ms 27ms 154ms 255ms 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/21/2026-09-22T21.parquet sha256sum 2026-09-22T21.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.