Hour audit: 2026-09-21T14
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-21T14 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-21T14:00:00.000061142+00:00 · last event 2026-09-21T14:59:59.999875994+00:00
VOLUME 123,866,135 rows · 1,350,600,649 bytes (1.26 GiB) · 7 products, all holding rows
WITNESSES cefh — 4 machines contributed rows
captured h: 122,435,883 · e: 121,758,425 · f: 113,730,582 · c: 108,976,545 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 17,454,169 (14.09%) · e: 3,834,066 (3.10%) · f: 989,629 (0.80%) · c: 101,588,271 (82.01%) (rows of the merged file that came from it; these partition it)
5 expected (cefgh), 1 contributed nothing: g
INTEGRITY sha256 456825a84b0f3d47812736b433b134bcff21d1d84de2dd0e95acc61d5fa5c6dc
the corpus checksum ledger names this file with the same digest
joined 123,883,111 to merged 123,866,135, minus 16,976 (minus 0.0137%)
boundary drops 16,976 · 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-21T15:57:59Z 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 11,122,168 132,372,629 0-42 9d04cae0ab0f928dad1a302e2c9207a7a706ac040b0c5d32401ec92e8b5190c8 book 1,398,931 77,733,957 43-48 cdf4c56bab5a5c3f09d22563296210b87ce1b2b2b2bbab8dddfe1fd8fb7a757d last_trade_price 69,094 3,881,827 49-49 4f8db692471ad28e59dd7c71e0fc16c62438f92ad01f2f95b626cc1d027c8142 market_resolved 1,157 146,972 50-50 ee672158ef153b218d5810f77d24d45d550b4ed4b4a3fdce650231edd437a10d new_market 2,433 239,902 51-51 13139d91673ca86944bb3709af07329199b0acc0faeae979ae393ad7f8d03185 price_change 111,267,036 1,134,622,082 52-476 f8da4a0d020700268e60bbe3f06b0d1e30f7b108f7a8c8481ae2359d7e3a38a8 tick_size_change 5,316 194,885 477-477 be6939e540b71667f7e9547f949a71c1032a62fbd63c48df01cb0cc75706eeb1 EVENT MIX count share price_change 111,267,036 89.83% best_bid_ask 11,122,168 8.98% book 1,398,931 1.13% last_trade_price 69,094 0.06% tick_size_change 5,316 <0.01% new_market 2,433 <0.01% market_resolved 1,157 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,122,292 11,122,168 124 75,235 PARTIAL book 1,414,625 1,398,931 15,694 155,710 PARTIAL last_trade_price 69,094 69,094 0 3,632 PARTIAL market_resolved 1,157 1,157 0 884 PARTIAL new_market 2,433 2,433 0 1,527 PARTIAL price_change 111,268,194 111,267,036 1,158 121,428 PARTIAL tick_size_change 5,316 5,316 0 1,329 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,776,725 9,149,985 6ms 19ms 150ms 4.5s 0 transport_latency_assumed best_bid_ask e 11,109,913 353,410 42ms 62ms 372ms 28.9s 0 transport_latency_assumed best_bid_ask f 10,285,353 53,125 49ms 77ms 401ms 22.3s 0 transport_latency_assumed best_bid_ask h 11,118,598 1,565,648 19ms 51ms 217ms 43.9s 0 transport_latency_assumed book c 1,068,405 985,191 5.3min 2.9d 44.0d 114.7d 0 book_staleness book e 231,671 62,900 806ms 30.7min 30.0d 114.7d 0 book_staleness book f 782,791 254,996 3.4min 2.9d 43.8d 114.7d 0 book_staleness book h 275,376 95,844 366ms 2.2h 30.0d 114.7d 0 book_staleness last_trade_price c 60,549 56,429 7ms 29ms 228ms 1.9s 0 transport_latency_assumed last_trade_price e 66,144 1,837 50ms 1.9s 14.4s 28.9s 0 transport_latency_assumed last_trade_price f 63,604 677 59ms 2.1s 12.4s 21.9s 0 transport_latency_assumed last_trade_price h 68,802 10,151 21ms 89ms 417ms 40.2s 0 transport_latency_assumed market_resolved c 891 761 7ms 2.3min 8.1min 9.6min 0 transport_latency_assumed market_resolved e 884 172 45ms 42.4s 59.1s 1.0min 0 transport_latency_assumed market_resolved f 863 138 52ms 3.4min 4.2min 4.3min 0 transport_latency_assumed market_resolved h 884 86 24ms 43.5s 60.0s 1.0min 0 transport_latency_assumed new_market c 1,545 970 149ms 38.1s 6.7min 7.9min 0 transport_latency_assumed new_market e 1,527 372 282ms 29.4s 1.3min 1.5min 0 transport_latency_assumed new_market f 1,591 343 298ms 1.0min 5.2min 13.8min 0 transport_latency_assumed new_market h 1,527 748 192ms 32.1s 1.3min 1.9min 0 transport_latency_assumed price_change c 98,063,558 91,390,235 7ms 22ms 175ms 4.8s 0 transport_latency_assumed price_change e 110,342,974 3,415,253 43ms 98ms 4.6s 28.9s 0 transport_latency_assumed price_change f 102,591,160 680,318 49ms 120ms 4.2s 22.8s 0 transport_latency_assumed price_change h 110,965,380 15,781,230 19ms 57ms 289ms 44.1s 0 transport_latency_assumed tick_size_change c 4,872 4,700 6ms 12ms 50ms 160ms 0 transport_latency_assumed tick_size_change e 5,312 122 42ms 52ms 213ms 709ms 0 transport_latency_assumed tick_size_change f 5,220 32 48ms 65ms 211ms 457ms 0 transport_latency_assumed tick_size_change h 5,316 462 19ms 42ms 297ms 4.4s 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/14/2026-09-21T14.parquet sha256sum 2026-09-21T14.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.