Hour audit: 2026-09-23T04
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-23T04 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-23T04:00:00.000102893+00:00 · last event 2026-09-23T04:59:59.999893291+00:00
VOLUME 116,722,860 rows · 1,230,774,330 bytes (1.15 GiB) · 7 products, all holding rows
WITNESSES cfhik — 5 machines contributed rows
captured c: 116,168,235 · h: 116,138,734 · i: 116,135,140 · k: 111,597,958 · f: 109,244,718 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 106,409,656 (91.16%) · h: 1,840,191 (1.58%) · i: 1,622,613 (1.39%) · k: 6,678,310 (5.72%) · f: 172,090 (0.15%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 1a8d56a6b00e62949f25c9c1ace28e472bb487942b0d9b49a889baa90de97d3b
the corpus checksum ledger names this file with the same digest
joined 116,724,620 to merged 116,722,860, minus 1,760 (minus 0.0015%)
boundary drops 1,760 · 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-23T07:07:02Z 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 13,074,160 148,518,683 0-49 a7267a802f077a009d873d57b74f290d657c331ba649719711fa1855d0344ca9 book 658,575 57,813,987 50-52 c23646dd09e26434f51eb59ec3f6786ef2982b72840de8d75e63dd5049828e06 last_trade_price 50,171 2,867,357 53-53 7c55ac0e7d129d212ff256fec7a54c5a282c28d82ece0c07c3b5e68c33412e52 market_resolved 1,508 225,254 54-54 b96ab6cc229a53c88226fa878727a29df4e6e2210a491769d5b0d7f3a88cf1d6 new_market 2,686 278,958 55-55 e1f56c413f380dd893d504afc812d589e9e5926d65ec31efd17946212e9a8046 price_change 102,929,500 1,019,516,841 56-448 57e82db131115492fd2bb153a5f0ab3d3c2f66a0a25fbf7f8bbed36285389a86 tick_size_change 6,260 225,655 449-449 7889ee121c4d588d4a150e5ef526bef4587672acac75df0247afe93c16b6afe0 EVENT MIX count share price_change 102,929,500 88.18% best_bid_ask 13,074,160 11.20% book 658,575 0.56% last_trade_price 50,171 0.04% tick_size_change 6,260 <0.01% new_market 2,686 <0.01% market_resolved 1,508 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,074,310 13,074,160 150 510 FULL book 658,939 658,575 364 190,224 FULL last_trade_price 50,171 50,171 0 109 FULL market_resolved 1,508 1,508 0 3 FULL new_market 2,686 2,686 0 0 FULL price_change 102,930,746 102,929,500 1,246 152 FULL tick_size_change 6,260 6,260 0 23 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 13,073,503 12,088,375 5ms 12ms 178ms 5.7s 0 transport_latency_assumed best_bid_ask f 12,283,098 7,003 48ms 63ms 296ms 11.6s 0 transport_latency_assumed best_bid_ask h 13,072,618 177,467 18ms 30ms 335ms 33.6s 0 transport_latency_assumed best_bid_ask i 13,072,257 167,113 21ms 29ms 127ms 2.1s 0 transport_latency_assumed best_bid_ask k 12,542,100 634,202 13ms 19ms 173ms 10.0s 0 transport_latency_assumed book c 133,806 109,941 7ms 17.0min 15.8d 116.3d 0 book_staleness book f 494,366 105,075 6.5min 2.5d 38.6d 116.2d 0 book_staleness book h 130,290 20,624 24ms 12.8min 15.7d 116.3d 0 book_staleness book i 127,256 19,797 26ms 10.0min 15.7d 116.3d 0 book_staleness book k 503,796 403,138 6.1min 2.3d 38.6d 116.3d 0 book_staleness last_trade_price c 50,050 44,500 6ms 27ms 332ms 4.1s 0 transport_latency_assumed last_trade_price f 46,038 59 50ms 206ms 5.1s 11.6s 0 transport_latency_assumed last_trade_price h 50,041 1,054 20ms 65ms 549ms 8.8s 0 transport_latency_assumed last_trade_price i 49,876 823 23ms 73ms 411ms 1.3s 0 transport_latency_assumed last_trade_price k 47,747 3,735 14ms 37ms 325ms 10.0s 0 transport_latency_assumed market_resolved c 1,399 1,137 5ms 33.4s 1.0min 1.0min 0 transport_latency_assumed market_resolved f 1,400 15 49ms 41.0s 6.0min 6.7min 0 transport_latency_assumed market_resolved h 1,402 17 19ms 22.7s 52.8s 1.0min 0 transport_latency_assumed market_resolved i 1,402 229 23ms 25.2s 58.8s 1.0min 0 transport_latency_assumed market_resolved k 1,400 110 13ms 40.2s 4.5min 5.2min 0 transport_latency_assumed new_market c 1,843 984 104ms 15.6s 1.8min 3.1min 0 transport_latency_assumed new_market f 1,843 304 173ms 14.7s 1.8min 4.7min 0 transport_latency_assumed new_market h 1,843 393 173ms 16.2s 1.7min 2.2min 0 transport_latency_assumed new_market i 1,843 465 134ms 14.9s 1.8min 3.1min 0 transport_latency_assumed new_market k 1,843 540 135ms 15.5s 1.7min 3.1min 0 transport_latency_assumed price_change c 102,901,374 94,158,898 5ms 15ms 201ms 5.9s 0 transport_latency_assumed price_change f 96,411,805 59,630 48ms 74ms 417ms 11.6s 0 transport_latency_assumed price_change h 102,876,280 1,640,560 18ms 36ms 357ms 37.6s 0 transport_latency_assumed price_change i 102,876,246 1,434,142 21ms 34ms 162ms 2.1s 0 transport_latency_assumed price_change k 98,494,856 5,636,270 13ms 23ms 190ms 10.0s 0 transport_latency_assumed tick_size_change c 6,260 5,821 5ms 11ms 65ms 236ms 0 transport_latency_assumed tick_size_change f 6,168 4 48ms 64ms 134ms 270ms 0 transport_latency_assumed tick_size_change h 6,260 76 18ms 34ms 125ms 2.2s 0 transport_latency_assumed tick_size_change i 6,260 44 21ms 29ms 83ms 385ms 0 transport_latency_assumed tick_size_change k 6,216 315 13ms 23ms 76ms 455ms 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-23/04/2026-09-23T04.parquet sha256sum 2026-09-23T04.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.