Hour audit: 2026-09-11T21
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: f. 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-11T21 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-11T21:00:00.000089400+00:00 · last event 2026-09-11T21:59:59.999029708+00:00
VOLUME 111,114,365 rows · 1,175,923,063 bytes (1.10 GiB) · 7 products, all holding rows
WITNESSES cegh — 4 machines contributed rows
captured e: 109,027,886 · h: 109,021,406 · g: 108,813,578 · c: 86,137,338 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 3,085,459 (2.78%) · h: 26,061,179 (23.45%) · g: 157,705 (0.14%) · c: 81,810,022 (73.63%) (rows of the merged file that came from it; these partition it)
5 expected (cefgh), 1 contributed nothing: f
INTEGRITY sha256 8dd952b46ead713c59a2286aef7f471e04e5b57fb3c2c19cbd5afca07c877e9e
the corpus checksum ledger names this file with the same digest
joined 111,144,836 to merged 111,114,365, minus 30,471 (minus 0.0274%)
boundary drops 30,471 · 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-12T02:13:40Z as cegh
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,221,421 116,775,964 0-38 059697ec0864b91e4f3f0e467010c4ac81afe8a4d639c6f27b7d8de8912f26e6 book 2,280,991 99,348,577 39-47 a511e08aadf132f230b342f54f045b009128fc989bb910f4c7f59b44864c9f5a last_trade_price 46,362 2,700,713 48-48 54045ed0f1d315d0ab132d8c46c76f3dde1666b021672a234085e0b20558f349 market_resolved 3,991 373,975 49-49 b17fe6c754f13d450d4875957f154d74631f78b5f1115ebfe478075b69a52bbc new_market 9,735 564,320 50-50 e07bcdf3620740c701dfcfb83c91088e6a9496d01f08b20bb8883ff5654a12ba price_change 98,549,165 954,797,638 51-426 2402c6a3d15c2d00a35706f356aba1e000ef0e2afe2cd5c6a0979c809ece90d6 tick_size_change 2,700 100,485 427-427 0d4ee2751ed411f2b21718570691dc1119f33d076ec92a7d72774072f514ff41 EVENT MIX count share price_change 98,549,165 88.69% best_bid_ask 10,221,421 9.20% book 2,280,991 2.05% last_trade_price 46,362 0.04% new_market 9,735 <0.01% market_resolved 3,991 <0.01% tick_size_change 2,700 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,222,235 10,221,421 814 84,666 PARTIAL book 2,303,446 2,280,991 22,455 216,285 PARTIAL last_trade_price 46,365 46,362 3 3,363 PARTIAL market_resolved 4,137 3,991 146 2,241 PARTIAL new_market 9,994 9,735 259 3,355 PARTIAL price_change 98,555,959 98,549,165 6,794 145,099 PARTIAL tick_size_change 2,700 2,700 0 675 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 7,899,548 7,502,767 5ms 12ms 222ms 8.9s 0 transport_latency_assumed best_bid_ask e 10,217,514 286,801 39ms 52ms 287ms 8.3s 0 transport_latency_assumed best_bid_ask g 10,216,342 13,376 82ms 140ms 581ms 26.2s 0 transport_latency_assumed best_bid_ask h 10,217,943 2,418,477 18ms 32ms 427ms 33.8s 0 transport_latency_assumed book c 2,158,758 2,063,591 7.8min 3.8h 31.1d 105.0d 0 book_staleness book e 266,221 91,841 41.5s 3.5h 20.3d 105.0d 0 book_staleness book g 122,542 11,548 114ms 7.0min 2.5d 86.5d 0 book_staleness book h 272,560 114,011 46.9s 3.6h 20.3d 105.0d 0 book_staleness last_trade_price c 34,616 32,878 10ms 49ms 268ms 5.0s 0 transport_latency_assumed last_trade_price e 46,147 1,339 55ms 333ms 3.4s 8.3s 0 transport_latency_assumed last_trade_price g 46,012 146 105ms 811ms 14.8s 26.4s 0 transport_latency_assumed last_trade_price h 46,095 11,999 24ms 106ms 664ms 7.4s 0 transport_latency_assumed market_resolved c 3,842 3,611 7.4min 20.6min 25.2min 25.9min 0 transport_latency_assumed market_resolved e 1,902 35 41ms 195ms 56.4s 1.0min 0 transport_latency_assumed market_resolved g 1,901 26 92ms 325ms 965ms 1.0min 0 transport_latency_assumed market_resolved h 1,902 319 20ms 91ms 58.7s 1.0min 0 transport_latency_assumed new_market c 9,119 7,377 9.1min 18.2min 25.0min 43.0min 0 transport_latency_assumed new_market e 2,763 676 167ms 1.1min 6.2min 7.1min 0 transport_latency_assumed new_market g 2,763 399 304ms 55.1s 6.0min 7.0min 0 transport_latency_assumed new_market h 2,752 1,283 128ms 54.0s 5.5min 6.9min 0 transport_latency_assumed price_change c 76,029,375 72,197,802 5ms 13ms 230ms 11.3s 0 transport_latency_assumed price_change e 98,490,639 2,704,662 39ms 65ms 472ms 8.3s 0 transport_latency_assumed price_change g 98,421,318 132,198 84ms 173ms 1.2s 26.3s 0 transport_latency_assumed price_change h 98,477,454 23,514,503 18ms 36ms 439ms 35.8s 0 transport_latency_assumed tick_size_change c 2,080 1,996 5ms 10ms 148ms 250ms 0 transport_latency_assumed tick_size_change e 2,700 105 39ms 68ms 270ms 485ms 0 transport_latency_assumed tick_size_change g 2,700 12 82ms 143ms 402ms 565ms 0 transport_latency_assumed tick_size_change h 2,700 587 18ms 36ms 267ms 1.1s 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-11/21/2026-09-11T21.parquet sha256sum 2026-09-11T21.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.