Hour audit: 2026-09-21T03
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-21T03 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-21T03:00:00.000033404+00:00 · last event 2026-09-21T03:59:59.999907502+00:00
VOLUME 102,223,424 rows · 1,015,673,998 bytes (968.62 MiB) · 7 products, all holding rows
WITNESSES cefh — 4 machines contributed rows
captured f: 102,108,514 · h: 102,093,049 · c: 102,086,315 · e: 102,039,159 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 153,735 (0.15%) · h: 3,637,826 (3.56%) · c: 98,268,118 (96.13%) · e: 163,745 (0.16%) (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 102,223,424 rows exactly, so those pairs supplied none
5 expected (cefgh), 1 contributed nothing: g
INTEGRITY sha256 64422b59f2aa83dab135ab8a794510bdf649bff6ee7bfd0494493c11aa8c07c1
the corpus checksum ledger names this file with the same digest
joined 102,224,738 to merged 102,223,424, minus 1,314 (minus 0.0013%)
boundary drops 1,314 · 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-21T06:22:33Z 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,241,530 112,579,134 0-39 fe6e0e073b3645f48fab6a254bed7106aefb707223b6c4c7fd0d33cea8779654 book 142,330 15,377,437 40-40 b892fc00ef2c279f71466bdda34cb299c7195aff8f8ccaed6a9edabcfbe1fb3f last_trade_price 43,293 2,438,376 41-41 b8839c0c52007f767e308edc3c387ba0aa48d7685e7b17235774bece352a1331 market_resolved 1,399 228,049 42-42 28320c924650a63d2ee1553097cd2af6aefa2537f2c0edf592099ed0335ddc2c new_market 670 78,230 43-43 aa1aafc283d614a4b0bfa701a7b0a538bb34c2ef1eda9cdd0e60a8f51f5b266e price_change 91,790,822 883,682,766 44-394 51f2c0ab047479f9b81efef482f10d4664b4536584f335b68aa876080e4ee84e tick_size_change 3,380 122,928 395-395 789bc5c240e6ba87e1e71ca0f786a5b6ea439ae52c0a002218c8f878f82edecf EVENT MIX count share price_change 91,790,822 89.79% best_bid_ask 10,241,530 10.02% book 142,330 0.14% last_trade_price 43,293 0.04% tick_size_change 3,380 <0.01% market_resolved 1,399 <0.01% new_market 670 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,241,684 10,241,530 154 65,754 PARTIAL book 142,336 142,330 6 27,166 PARTIAL last_trade_price 43,293 43,293 0 2,524 PARTIAL market_resolved 1,399 1,399 0 1,397 PARTIAL new_market 670 670 0 529 PARTIAL price_change 91,791,976 91,790,822 1,154 115,094 PARTIAL tick_size_change 3,380 3,380 0 845 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,240,774 9,910,205 4ms 8ms 60ms 1.4s 0 transport_latency_assumed best_bid_ask e 10,240,768 11,046 46ms 51ms 124ms 6.8s 0 transport_latency_assumed best_bid_ask f 10,240,849 9,461 46ms 52ms 126ms 3.3s 0 transport_latency_assumed best_bid_ask h 10,241,122 310,818 17ms 23ms 84ms 8.0s 0 transport_latency_assumed book c 101,469 95,393 6ms 1.9min 13.7d 114.2d 0 book_staleness book e 93,824 6,259 48ms 226ms 2.4d 95.7d 0 book_staleness book f 96,983 9,216 48ms 2.5s 6.9d 114.2d 0 book_staleness book h 115,165 31,462 21ms 16.6min 15.6d 114.2d 0 book_staleness last_trade_price c 43,098 40,728 5ms 15ms 128ms 627ms 0 transport_latency_assumed last_trade_price e 43,127 128 48ms 92ms 477ms 6.8s 0 transport_latency_assumed last_trade_price f 43,190 114 48ms 94ms 392ms 3.3s 0 transport_latency_assumed last_trade_price h 43,225 2,323 18ms 36ms 169ms 7.4s 0 transport_latency_assumed market_resolved c 1,397 1,306 4ms 16ms 53.6s 1.0min 0 transport_latency_assumed market_resolved e 1,397 2 48ms 130ms 51.9s 57.2s 0 transport_latency_assumed market_resolved f 1,397 1 47ms 130ms 51.9s 57.3s 0 transport_latency_assumed market_resolved h 1,397 90 18ms 61ms 52.7s 1.0min 0 transport_latency_assumed new_market c 529 298 93ms 13.0s 1.3min 1.4min 0 transport_latency_assumed new_market e 529 140 213ms 16.4s 1.3min 1.5min 0 transport_latency_assumed new_market f 529 107 171ms 16.9s 1.4min 1.5min 0 transport_latency_assumed new_market h 529 125 181ms 15.2s 1.4min 1.5min 0 transport_latency_assumed price_change c 91,695,668 88,216,888 4ms 10ms 72ms 1.9s 0 transport_latency_assumed price_change e 91,656,134 146,170 46ms 54ms 179ms 6.9s 0 transport_latency_assumed price_change f 91,722,186 134,832 46ms 56ms 176ms 5.4s 0 transport_latency_assumed price_change h 91,688,231 3,292,932 18ms 26ms 107ms 8.0s 0 transport_latency_assumed tick_size_change c 3,380 3,300 4ms 7ms 38ms 83ms 0 transport_latency_assumed tick_size_change e 3,380 not meas. 46ms 50ms 96ms 161ms 0 transport_latency_assumed tick_size_change f 3,380 4 46ms 50ms 94ms 155ms 0 transport_latency_assumed tick_size_change h 3,380 76 17ms 20ms 51ms 665ms 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/03/2026-09-21T03.parquet sha256sum 2026-09-21T03.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.