Hour audit: 2026-09-22T17
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-22T17 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-22T17:00:00.000155242+00:00 · last event 2026-09-22T17:59:59.999669580+00:00
VOLUME 115,281,984 rows · 1,269,332,889 bytes (1.18 GiB) · 7 products, all holding rows
WITNESSES cefhik — 6 machines contributed rows
captured c: 114,830,083 · k: 114,816,604 · h: 114,760,185 · f: 114,719,140 · e: 114,535,182 · i: 113,554,489 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 103,619,531 (89.88%) · k: 8,871,669 (7.70%) · h: 1,759,366 (1.53%) · f: 59,370 (0.05%) · e: 67,653 (0.06%) · i: 904,395 (0.78%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 115,281,984 rows exactly, so those pairs supplied none
6 expected, all 6 contributed
INTEGRITY sha256 24fe1b7627f15fd0f5e556e179be4771f4481f4adfe49c1ccfd0222d3263a1f9
the corpus checksum ledger names this file with the same digest
joined 115,284,362 to merged 115,281,984, minus 2,378 (minus 0.0021%)
boundary drops 2,378 · 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-22T20:15:54Z 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 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,704,218 127,980,150 0-40 e4d30e22d8742cd2ba665b95ece811b3f04e9794bec1d4f31c3a71cd4bcaa333 book 570,618 50,504,473 41-43 77ee354c2dfe0b76200708ceadbbcdea37764f34d17224a8fc7a0050c33f1e84 last_trade_price 67,357 3,833,961 44-44 5f8412f227452d0db66f86735183788d5ac21258037b3058144288c9fa53ca7a market_resolved 658 103,928 45-45 6c11dc351c36ba1513595806531aee98f6a251ede8a814c01adf96837d9ab931 new_market 1,473 148,045 46-46 4167ce10c4d2fc0b2a2963ef085a05a36269c4a08b64a2c2363bf23b3e99a704 price_change 103,935,120 1,085,352,824 47-443 8dab2b59ae7e8b79b7f6c045b0798abbda92247d77a32c9118279b6efb99b499 tick_size_change 2,540 94,316 444-444 98cffc3b8cedf185a17fece35fed1dc864c5aa57c25d8ab2ebdd4d100050558e EVENT MIX count share price_change 103,935,120 90.16% best_bid_ask 10,704,218 9.29% book 570,618 0.49% last_trade_price 67,357 0.06% tick_size_change 2,540 <0.01% new_market 1,473 <0.01% market_resolved 658 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,704,434 10,704,218 216 153 FULL book 571,260 570,618 642 138,583 FULL last_trade_price 67,361 67,357 4 3 FULL market_resolved 658 658 0 1 FULL new_market 1,473 1,473 0 47 FULL price_change 103,936,636 103,935,120 1,516 274 FULL tick_size_change 2,540 2,540 0 6 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,701,930 9,716,931 5ms 16ms 122ms 4.1s 0 transport_latency_assumed best_bid_ask e 10,696,250 4,827 43ms 63ms 337ms 17.0s 0 transport_latency_assumed best_bid_ask f 10,700,146 3,158 49ms 66ms 295ms 15.6s 0 transport_latency_assumed best_bid_ask h 10,701,702 148,801 18ms 34ms 159ms 42.0s 0 transport_latency_assumed best_bid_ask i 10,636,134 57,936 24ms 45ms 609ms 11.2s 0 transport_latency_assumed best_bid_ask k 10,701,976 772,565 13ms 21ms 109ms 14.2s 0 transport_latency_assumed book c 166,627 146,152 8ms 8.7min 15.3d 115.8d 0 book_staleness book e 148,115 13,166 51ms 7.3s 3.1d 97.3d 0 book_staleness book f 159,643 20,055 61ms 2.8min 13.4d 97.3d 0 book_staleness book h 163,017 27,354 24ms 4.9min 13.4d 115.8d 0 book_staleness book i 475,503 327,435 1.9min 23.8h 31.2d 115.8d 0 book_staleness book k 165,747 36,456 18ms 6.8min 15.3d 115.8d 0 book_staleness last_trade_price c 67,112 59,439 6ms 28ms 239ms 1.5s 0 transport_latency_assumed last_trade_price e 66,097 83 50ms 971ms 8.4s 17.1s 0 transport_latency_assumed last_trade_price f 66,487 78 55ms 977ms 8.5s 15.6s 0 transport_latency_assumed last_trade_price h 66,954 1,360 20ms 82ms 443ms 9.1s 0 transport_latency_assumed last_trade_price i 62,796 309 26ms 601ms 3.2s 11.2s 0 transport_latency_assumed last_trade_price k 66,909 6,088 14ms 45ms 251ms 4.0s 0 transport_latency_assumed market_resolved c 634 502 6ms 29.1s 54.2s 54.2s 0 transport_latency_assumed market_resolved e 635 1 45ms 30.2s 51.9s 1.0min 0 transport_latency_assumed market_resolved f 635 not meas. 51ms 35.4s 59.9s 59.9s 0 transport_latency_assumed market_resolved h 635 98 20ms 27.9s 59.1s 59.2s 0 transport_latency_assumed market_resolved i 635 14 25ms 31.4s 1.8min 1.8min 0 transport_latency_assumed market_resolved k 635 43 14ms 29.0s 52.9s 52.9s 0 transport_latency_assumed new_market c 910 441 90ms 39.5s 181.0d 215.8d 0 transport_latency_assumed new_market e 863 102 190ms 21.9s 56.3s 1.6min 0 transport_latency_assumed new_market f 863 91 184ms 23.6s 48.6s 1.2min 0 transport_latency_assumed new_market h 863 309 143ms 24.7s 1.0min 1.7min 0 transport_latency_assumed new_market i 863 205 136ms 20.3s 46.5s 1.2min 0 transport_latency_assumed new_market k 863 325 128ms 22.8s 52.4s 1.6min 0 transport_latency_assumed price_change c 103,890,330 93,693,672 5ms 18ms 134ms 5.2s 0 transport_latency_assumed price_change e 103,620,682 49,474 44ms 91ms 1.8s 17.1s 0 transport_latency_assumed price_change f 103,788,826 35,988 49ms 90ms 1.8s 15.6s 0 transport_latency_assumed price_change h 103,824,474 1,581,412 18ms 40ms 200ms 42.1s 0 transport_latency_assumed price_change i 102,376,042 518,490 24ms 73ms 1.5s 11.3s 0 transport_latency_assumed price_change k 103,877,934 8,056,084 13ms 24ms 127ms 14.3s 0 transport_latency_assumed tick_size_change c 2,540 2,394 5ms 10ms 53ms 235ms 0 transport_latency_assumed tick_size_change e 2,540 not meas. 43ms 57ms 147ms 1.3s 0 transport_latency_assumed tick_size_change f 2,540 not meas. 49ms 55ms 128ms 525ms 0 transport_latency_assumed tick_size_change h 2,540 32 18ms 27ms 69ms 180ms 0 transport_latency_assumed tick_size_change i 2,516 6 24ms 53ms 532ms 860ms 0 transport_latency_assumed tick_size_change k 2,540 108 13ms 19ms 55ms 93ms 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/17/2026-09-22T17.parquet sha256sum 2026-09-22T17.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.