Hour audit: 2026-09-21T22
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-21T22 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-21T22:00:00.000008541+00:00 · last event 2026-09-21T22:59:59.999988630+00:00
VOLUME 107,504,776 rows · 1,120,186,024 bytes (1.04 GiB) · 7 products, all holding rows
WITNESSES cefh — 4 machines contributed rows
captured h: 105,946,750 · f: 105,845,910 · e: 105,445,485 · c: 91,353,145 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 20,313,902 (18.90%) · f: 433,562 (0.40%) · e: 1,023,271 (0.95%) · c: 85,734,041 (79.75%) (rows of the merged file that came from it; these partition it)
5 expected (cefgh), 1 contributed nothing: g
INTEGRITY sha256 67947c8c3432a0ba232b826c08e2ec7049087b70459fcc84fba13724ad6e434e
the corpus checksum ledger names this file with the same digest
joined 107,510,858 to merged 107,504,776, minus 6,082 (minus 0.0057%)
boundary drops 6,082 · 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-21T23:55:18Z 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,520,406 119,377,906 0-40 7d038601b2a417bc355b21ff4bff20f2c297396f351d8d1595846a2988d2d1d1 book 1,410,006 71,534,695 41-46 dbded3c0073cb39a61907d651412edc98c247757e1ed58c9a543e5689e91e843 last_trade_price 50,344 2,865,431 47-47 6366fc7f27d697bea5d5e1fc49b1a1ff421b89fb7cff996608d608124cf7e66b market_resolved 676 106,118 48-48 3b3ebb168dae55257cbe87c5d52271ba3a8371605da67ef2703cc6005c7fc889 new_market 1,040 109,369 49-49 dfc29a072dac0d64018a1829032d944ad068d98764fa78224493935093851053 price_change 95,518,472 924,826,105 50-414 9bf40f0db35cc57d7075efed299667cad4f5dddaf5a0b51fd533408be5d2082e tick_size_change 3,832 140,248 415-415 2947053a60417fdabc73ec270214c09022f09eba44faa68e3d07714d7ecb71b9 EVENT MIX count share price_change 95,518,472 88.85% best_bid_ask 10,520,406 9.79% book 1,410,006 1.31% last_trade_price 50,344 0.05% tick_size_change 3,832 <0.01% new_market 1,040 <0.01% market_resolved 676 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,520,566 10,520,406 160 77,902 PARTIAL book 1,410,052 1,410,006 46 177,286 PARTIAL last_trade_price 50,344 50,344 0 3,017 PARTIAL market_resolved 676 676 0 652 PARTIAL new_market 1,040 1,040 0 708 PARTIAL price_change 95,524,348 95,518,472 5,876 130,478 PARTIAL tick_size_change 3,832 3,832 0 958 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,934,302 8,421,059 5ms 16ms 139ms 9.4s 0 transport_latency_assumed best_bid_ask e 10,505,662 86,779 41ms 55ms 269ms 15.7s 0 transport_latency_assumed best_bid_ask f 10,518,030 31,381 48ms 62ms 223ms 14.4s 0 transport_latency_assumed best_bid_ask h 10,513,917 1,981,187 18ms 29ms 179ms 1.7min 0 transport_latency_assumed book c 1,347,988 1,312,832 8.4min 3.3d 43.3d 115.0d 0 book_staleness book e 132,250 31,031 52ms 14.7min 14.5d 115.0d 0 book_staleness book f 118,373 14,243 52ms 1.7min 12.6d 115.0d 0 book_staleness book h 143,262 51,900 26ms 22.9min 22.2d 96.5d 0 book_staleness last_trade_price c 41,274 38,149 6ms 32ms 236ms 3.5s 0 transport_latency_assumed last_trade_price e 48,980 638 43ms 334ms 3.5s 15.7s 0 transport_latency_assumed last_trade_price f 49,993 511 50ms 237ms 2.7s 6.1s 0 transport_latency_assumed last_trade_price h 49,637 11,046 19ms 66ms 402ms 49.1s 0 transport_latency_assumed market_resolved c 637 512 6ms 37.2s 4.8min 5.1min 0 transport_latency_assumed market_resolved e 651 109 42ms 25.8s 60.0s 1.0min 0 transport_latency_assumed market_resolved f 652 2 51ms 25.8s 1.0min 1.0min 0 transport_latency_assumed market_resolved h 652 53 19ms 27.2s 57.1s 1.0min 0 transport_latency_assumed new_market c 708 439 103ms 18.3s 21.2min 21.2min 0 transport_latency_assumed new_market e 708 172 212ms 13.7s 45.1s 1.7min 0 transport_latency_assumed new_market f 708 134 212ms 14.4s 38.7s 1.5min 0 transport_latency_assumed new_market h 708 295 163ms 16.8s 42.8s 1.7min 0 transport_latency_assumed price_change c 81,024,836 75,957,816 5ms 19ms 157ms 9.6s 0 transport_latency_assumed price_change e 94,753,402 904,530 41ms 74ms 1.2s 15.7s 0 transport_latency_assumed price_change f 95,154,322 387,287 48ms 77ms 611ms 14.4s 0 transport_latency_assumed price_change h 95,234,742 18,268,839 18ms 36ms 260ms 1.7min 0 transport_latency_assumed tick_size_change c 3,400 3,234 5ms 12ms 161ms 1.4s 0 transport_latency_assumed tick_size_change e 3,832 12 41ms 47ms 137ms 1.5s 0 transport_latency_assumed tick_size_change f 3,832 4 47ms 52ms 114ms 196ms 0 transport_latency_assumed tick_size_change h 3,832 582 18ms 23ms 53ms 84ms 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-21/22/2026-09-21T22.parquet sha256sum 2026-09-21T22.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.