Hour audit: 2026-09-21T23
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-21T23 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-21T23:00:00.000439718+00:00 · last event 2026-09-21T23:59:59.999583437+00:00
VOLUME 114,934,552 rows · 1,183,222,281 bytes (1.10 GiB) · 7 products, all holding rows
WITNESSES cefh — 4 machines contributed rows
captured h: 113,286,965 · f: 113,051,451 · e: 112,792,540 · c: 100,470,597 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 18,479,104 (16.08%) · f: 459,228 (0.40%) · e: 1,230,716 (1.07%) · c: 94,765,504 (82.45%) (rows of the merged file that came from it; these partition it)
5 expected (cefgh), 1 contributed nothing: g
INTEGRITY sha256 ef46ff66056f0c9981a3bceb7942da85f84fee79475965c248bf45d5b4b2cb2b
the corpus checksum ledger names this file with the same digest
joined 114,951,483 to merged 114,934,552, minus 16,931 (minus 0.0147%)
boundary drops 16,931 · 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-22T00:56:30Z 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,651,352 119,604,975 0-40 38a2122f1048482cb7b058a3cd4fb4c72dd5ec2bd474a36fd28cfc4471ccd743 book 1,379,913 70,293,088 41-46 4a503166e4961c24d1b75b7e467e412844a750a9ae392719689346725293d614 last_trade_price 51,237 2,854,885 47-47 d93ea3b0047b0298f0bb7565020e749674a9bb32fbc7f6eb52cbde3aa1ecdb18 market_resolved 682 96,863 48-48 bcfe7c184b8d045530803c94ec0e60ded8cfbed3c3f2f96f806ff1343121d0e0 new_market 816 84,479 49-49 2e3a6b8c7cb42b4847d096ac6988fc47fb9aac6f5e614eb90fc4b58468e3a3ff price_change 102,848,340 988,898,541 50-442 ace5c94d1614837c842e9752fb4837b8c0bbadd9e998bb9a30ff1bc71644f3cb tick_size_change 2,212 80,947 443-443 258d40363d37f5d87957de446f0e4520f65daec5ac98cc8506eb54eeca0d128a EVENT MIX count share price_change 102,848,340 89.48% best_bid_ask 10,651,352 9.27% book 1,379,913 1.20% last_trade_price 51,237 0.04% tick_size_change 2,212 <0.01% new_market 816 <0.01% market_resolved 682 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,651,442 10,651,352 90 76,552 PARTIAL book 1,395,085 1,379,913 15,172 177,221 PARTIAL last_trade_price 51,237 51,237 0 2,804 PARTIAL market_resolved 683 682 1 592 PARTIAL new_market 816 816 0 525 PARTIAL price_change 102,850,008 102,848,340 1,668 129,919 PARTIAL tick_size_change 2,212 2,212 0 553 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,292,711 8,800,876 4ms 14ms 104ms 1.4s 0 transport_latency_assumed best_bid_ask e 10,635,964 107,041 41ms 54ms 189ms 15.1s 0 transport_latency_assumed best_bid_ask f 10,648,854 32,295 48ms 62ms 194ms 9.7s 0 transport_latency_assumed best_bid_ask h 10,642,864 1,711,140 17ms 31ms 121ms 42.5s 0 transport_latency_assumed book c 1,339,410 1,305,735 9.6min 3.3d 43.5d 115.1d 0 book_staleness book e 120,606 18,759 45ms 3.2min 14.4d 96.5d 0 book_staleness book f 110,793 5,358 51ms 691ms 2.3d 115.1d 0 book_staleness book h 154,562 50,061 29ms 27.8min 27.2d 115.0d 0 book_staleness last_trade_price c 43,524 40,018 5ms 29ms 225ms 1.2s 0 transport_latency_assumed last_trade_price e 49,747 932 43ms 184ms 2.8s 15.1s 0 transport_latency_assumed last_trade_price f 50,937 438 51ms 203ms 1.7s 3.7s 0 transport_latency_assumed last_trade_price h 50,374 9,849 18ms 58ms 361ms 5.5s 0 transport_latency_assumed market_resolved c 579 474 6ms 3.9min 4.8min 5.1min 0 transport_latency_assumed market_resolved e 586 102 43ms 19.1s 36.3s 47.5s 0 transport_latency_assumed market_resolved f 586 2 51ms 19.1s 36.3s 47.5s 0 transport_latency_assumed market_resolved h 586 104 18ms 19.3s 36.5s 48.6s 0 transport_latency_assumed new_market c 526 361 58ms 11.5s 8.3min 9.4min 0 transport_latency_assumed new_market e 525 146 183ms 17.3s 33.1s 5.6min 0 transport_latency_assumed new_market f 525 96 191ms 15.2s 4.7min 5.6min 0 transport_latency_assumed new_market h 525 213 112ms 19.9s 58.1s 5.6min 0 transport_latency_assumed price_change c 89,792,027 84,616,244 4ms 17ms 117ms 1.9s 0 transport_latency_assumed price_change e 101,982,900 1,103,663 42ms 66ms 497ms 15.2s 0 transport_latency_assumed price_change f 102,237,544 421,024 48ms 71ms 369ms 18.5s 0 transport_latency_assumed price_change h 102,435,842 16,707,409 17ms 36ms 173ms 44.2s 0 transport_latency_assumed tick_size_change c 1,820 1,796 4ms 7ms 21ms 258ms 0 transport_latency_assumed tick_size_change e 2,212 73 41ms 60ms 137ms 226ms 0 transport_latency_assumed tick_size_change f 2,212 15 48ms 63ms 207ms 314ms 0 transport_latency_assumed tick_size_change h 2,212 328 17ms 38ms 171ms 326ms 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/23/2026-09-21T23.parquet sha256sum 2026-09-21T23.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.