Hour audit: 2026-09-22T03
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.
1 finding
- a machine expected this hour contributed nothing. Of the 5 machines expected to be capturing this hour, 1 contributed no rows: g. The hour is still whole on minutes; it simply rests on 4 machines rather than 5.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-22T03 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-22T03:00:00.000017885+00:00 · last event 2026-09-22T03:59:59.999435698+00:00
VOLUME 114,747,354 rows · 1,158,250,032 bytes (1.08 GiB) · 7 products, all holding rows
WITNESSES cefh — 4 machines contributed rows
captured c: 114,394,210 · f: 114,365,766 · h: 114,312,328 · e: 113,715,546 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 108,385,719 (94.46%) · f: 229,455 (0.20%) · h: 5,741,649 (5.00%) · e: 390,531 (0.34%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 114,747,354 rows exactly, so those pairs supplied none
5 expected (cefgh), 1 contributed nothing: g
INTEGRITY sha256 cf187c85fb93f2362a062dcbae8dea7a8a654ba3fc8dfa77d1a141bec4566217
the corpus checksum ledger names this file with the same digest
joined 114,749,216 to merged 114,747,354, minus 1,862 (minus 0.0016%)
boundary drops 1,862 · 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-22T05:33:35Z as cefh
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 7/8 pass, 1 finding
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
FINDING a machine expected this hour contributed nothing
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,690,347 120,290,948 0-40 1d7e4672f646f9288945c000d921c2bd7b6eb974833253331b1e27bb926b208e book 423,994 39,699,308 41-42 342cac2ff7fa62de676ac6d01d7068f3731ff859da0393b8846abfb63a1ce71c last_trade_price 47,142 2,648,272 43-43 bf93f582466a4b274f14c98ad05a7169f0aa8200b6f2a7a1bdd9e3f07ce960eb market_resolved 905 139,655 44-44 dc95e87ebf729280ee60a461ea0abf8f07321492229764eb294f0c922a093757 new_market 1,196 124,155 45-45 0fd4314d84a6d8ad56f2dbdaff26b1cc37c37ca5b6a615785db1a97dd8dea6cc price_change 103,580,766 993,932,309 46-441 d65ac55d6471a15cd2ce88bd2c12ab265bc5c9f94bbc6a8024edd2874cc2f787 tick_size_change 3,004 110,129 442-442 9fc843db2301a45a1e4e1df91d7ac06149a9a4c3e7fafc472129ed9ed6bcbdf6 EVENT MIX count share price_change 103,580,766 90.27% best_bid_ask 10,690,347 9.32% book 423,994 0.37% last_trade_price 47,142 0.04% tick_size_change 3,004 <0.01% new_market 1,196 <0.01% market_resolved 905 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,690,517 10,690,347 170 71,168 PARTIAL book 424,074 423,994 80 125,316 PARTIAL last_trade_price 47,142 47,142 0 2,736 PARTIAL market_resolved 905 905 0 859 PARTIAL new_market 1,196 1,196 0 819 PARTIAL price_change 103,582,378 103,580,766 1,612 125,229 PARTIAL tick_size_change 3,004 3,004 0 751 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,689,702 10,179,768 4ms 12ms 92ms 3.6s 0 transport_latency_assumed best_bid_ask e 10,683,147 28,189 42ms 52ms 162ms 17.4s 0 transport_latency_assumed best_bid_ask f 10,688,303 13,600 48ms 59ms 165ms 5.7s 0 transport_latency_assumed best_bid_ask h 10,682,674 468,790 18ms 28ms 110ms 8.0s 0 transport_latency_assumed book c 129,531 115,068 8ms 25.5min 16.6d 115.2d 0 book_staleness book e 129,480 33,532 46ms 22.3min 19.4d 115.2d 0 book_staleness book f 143,501 38,661 56ms 38.8min 27.3d 115.2d 0 book_staleness book h 338,230 236,733 2.3min 1.4d 37.7d 115.2d 0 book_staleness last_trade_price c 46,995 43,375 5ms 24ms 214ms 951ms 0 transport_latency_assumed last_trade_price e 46,598 307 43ms 90ms 611ms 17.4s 0 transport_latency_assumed last_trade_price f 46,928 177 50ms 98ms 439ms 3.2s 0 transport_latency_assumed last_trade_price h 46,702 3,283 19ms 44ms 238ms 6.7s 0 transport_latency_assumed market_resolved c 859 772 5ms 27ms 1.0min 1.0min 0 transport_latency_assumed market_resolved e 859 5 43ms 22.8s 1.0min 1.0min 0 transport_latency_assumed market_resolved f 859 2 48ms 292ms 55.5s 57.5s 0 transport_latency_assumed market_resolved h 859 126 19ms 22.7s 1.0min 1.0min 0 transport_latency_assumed new_market c 819 520 81ms 54.6s 1.9min 2.5min 0 transport_latency_assumed new_market e 819 107 150ms 49.8s 1.8min 2.1min 0 transport_latency_assumed new_market f 819 166 139ms 55.7s 1.8min 2.2min 0 transport_latency_assumed new_market h 819 403 94ms 53.0s 1.9min 2.1min 0 transport_latency_assumed price_change c 103,523,300 98,043,322 5ms 15ms 104ms 3.8s 0 transport_latency_assumed price_change e 102,851,639 328,386 42ms 59ms 300ms 17.6s 0 transport_latency_assumed price_change f 103,482,356 176,849 48ms 65ms 251ms 6.3s 0 transport_latency_assumed price_change h 103,240,040 5,032,209 18ms 32ms 141ms 8.0s 0 transport_latency_assumed tick_size_change c 3,004 2,894 5ms 11ms 80ms 113ms 0 transport_latency_assumed tick_size_change e 3,004 5 42ms 51ms 117ms 378ms 0 transport_latency_assumed tick_size_change f 3,000 not meas. 48ms 62ms 118ms 273ms 0 transport_latency_assumed tick_size_change h 3,004 105 19ms 32ms 112ms 948ms 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/03/2026-09-22T03.parquet sha256sum 2026-09-22T03.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.