Hour audit: 2026-09-23T05
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-23T05 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-23T05:00:00.000009179+00:00 · last event 2026-09-23T05:59:59.999856832+00:00
VOLUME 109,120,745 rows · 1,132,600,503 bytes (1.05 GiB) · 7 products, all holding rows
WITNESSES cfhik — 5 machines contributed rows
captured f: 108,814,508 · c: 108,768,531 · k: 108,562,365 · i: 108,537,604 · h: 108,484,168 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 391,076 (0.36%) · c: 100,827,124 (92.40%) · k: 5,823,339 (5.34%) · i: 719,513 (0.66%) · h: 1,359,693 (1.25%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 109,120,745 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 006e6e40c245f4a5da741a6251efd2d2a0a711faad57fbb82ffc9209a65675ea
the corpus checksum ledger names this file with the same digest
joined 109,121,842 to merged 109,120,745, minus 1,097 (minus 0.0010%)
boundary drops 1,097 · 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-23T08:06:12Z 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,093,988 145,783,158 0-49 25a809015391638904bd3037cf5f6599eb317c987b06b1a75949f147a164098f book 614,537 47,099,022 50-52 dc364b70f08068938f55258498c5e96b8931fc83f9c74d65c645f44f2c722a51 last_trade_price 48,811 2,768,022 53-53 ce14913667932f1feba05038e4b6e3eb8e39ca479d5abf2c612cb1d3353af63c market_resolved 1,592 246,916 54-54 32def3b4223932996fa06d274b4ab4b4e31815be4e011907cc7494be5461e170 new_market 1,535 155,335 55-55 9dedbe68937d57bf6fa1745148bc4ac0cd5c3c03868c032cda025f63d7b5aba8 price_change 95,357,398 935,200,428 56-419 1dd774fd33524cadc43b93c8f28d281d2e78eb46b1d4806b4160b8f4d5d01971 tick_size_change 2,884 105,852 420-420 9e2250d02dc361aa51a3e73f7bdb21efe6271a587f87155685022a00e9c9a5f9 EVENT MIX count share price_change 95,357,398 87.39% best_bid_ask 13,093,988 12.00% book 614,537 0.56% last_trade_price 48,811 0.04% tick_size_change 2,884 <0.01% market_resolved 1,592 <0.01% new_market 1,535 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,094,130 13,093,988 142 111 FULL book 614,577 614,537 40 148,333 FULL last_trade_price 48,811 48,811 0 0 FULL market_resolved 1,595 1,592 3 3 FULL new_market 1,535 1,535 0 0 FULL price_change 95,358,310 95,357,398 912 122 FULL tick_size_change 2,884 2,884 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 13,091,154 12,265,817 4ms 9ms 94ms 4.0s 0 transport_latency_assumed best_bid_ask f 13,087,584 4,811 48ms 56ms 180ms 13.8s 0 transport_latency_assumed best_bid_ask h 13,091,614 136,137 18ms 25ms 132ms 8.4s 0 transport_latency_assumed best_bid_ask i 13,092,552 75,095 22ms 28ms 96ms 4.1s 0 transport_latency_assumed best_bid_ask k 13,092,949 612,128 12ms 17ms 93ms 7.5s 0 transport_latency_assumed book c 337,093 260,415 2.7min 1.6d 31.7d 116.3d 0 book_staleness book f 431,774 325,131 3.3min 2.4d 38.0d 116.3d 0 book_staleness book h 105,280 8,428 21ms 179ms 13.6h 97.8d 0 book_staleness book i 105,364 6,765 24ms 271ms 1.4d 97.8d 0 book_staleness book k 106,831 13,798 15ms 159ms 1.6d 116.3d 0 book_staleness last_trade_price c 48,505 43,789 5ms 20ms 171ms 2.2s 0 transport_latency_assumed last_trade_price f 48,363 72 50ms 163ms 3.0s 13.8s 0 transport_latency_assumed last_trade_price h 48,440 887 19ms 52ms 319ms 4.0s 0 transport_latency_assumed last_trade_price i 48,602 413 24ms 79ms 556ms 2.6s 0 transport_latency_assumed last_trade_price k 48,660 3,650 13ms 30ms 210ms 3.0s 0 transport_latency_assumed market_resolved c 1,536 1,324 5ms 29.0s 59.6s 1.0min 0 transport_latency_assumed market_resolved f 1,536 not meas. 49ms 30.6s 1.0min 1.0min 0 transport_latency_assumed market_resolved h 1,533 6 18ms 25.7s 56.4s 58.7s 0 transport_latency_assumed market_resolved i 1,533 222 23ms 23.7s 55.2s 56.7s 0 transport_latency_assumed market_resolved k 1,536 40 13ms 29.7s 59.9s 1.0min 0 transport_latency_assumed new_market c 1,013 504 70ms 33.8s 1.9min 2.5min 0 transport_latency_assumed new_market f 1,013 168 141ms 17.7s 2.2min 2.5min 0 transport_latency_assumed new_market h 1,013 291 122ms 45.9s 2.5min 2.7min 0 transport_latency_assumed new_market i 1,013 224 103ms 32.8s 2.0min 2.6min 0 transport_latency_assumed new_market k 1,013 348 95ms 38.2s 1.8min 2.5min 0 transport_latency_assumed price_change c 95,286,346 88,252,568 5ms 12ms 125ms 12.0s 0 transport_latency_assumed price_change f 95,241,354 60,894 48ms 64ms 311ms 13.9s 0 transport_latency_assumed price_change h 95,233,404 1,213,928 18ms 30ms 183ms 8.8s 0 transport_latency_assumed price_change i 95,285,656 636,786 22ms 33ms 155ms 4.2s 0 transport_latency_assumed price_change k 95,308,492 5,193,222 12ms 20ms 126ms 8.1s 0 transport_latency_assumed tick_size_change c 2,884 2,707 5ms 9ms 47ms 89ms 0 transport_latency_assumed tick_size_change f 2,884 not meas. 48ms 56ms 107ms 135ms 0 transport_latency_assumed tick_size_change h 2,884 16 18ms 32ms 59ms 466ms 0 transport_latency_assumed tick_size_change i 2,884 8 22ms 28ms 102ms 222ms 0 transport_latency_assumed tick_size_change k 2,884 153 13ms 17ms 59ms 115ms 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/05/2026-09-23T05.parquet sha256sum 2026-09-23T05.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.