Hour audit: 2026-09-20T07
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-20T07 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-20T07:00:00.000056074+00:00 · last event 2026-09-20T07:59:59.999504100+00:00
VOLUME 110,109,328 rows · 1,107,127,545 bytes (1.03 GiB) · 7 products, all holding rows
WITNESSES cegh — 4 machines contributed rows
captured c: 110,045,998 · h: 110,020,075 · e: 110,011,833 · g: 109,957,368 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 105,079,227 (95.43%) · h: 4,593,267 (4.17%) · e: 385,773 (0.35%) · g: 51,061 (0.05%) (rows of the merged file that came from it; these partition it)
5 expected (cefgh), 1 contributed nothing: f
INTEGRITY sha256 19a557eaf006e0f2c93e11438d2cd43f544e6ebba9fe359fd59e51e6d48c41a3
the corpus checksum ledger names this file with the same digest
joined 110,112,888 to merged 110,109,328, minus 3,560 (minus 0.0032%)
boundary drops 3,560 · 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-20T09:57:29Z 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 13,114,162 145,405,504 0-50 f95de72e6813916562c2ca9385b48002fb45c8ff80b8c2695e3a2d81da06b8c7 book 144,437 15,683,319 51-51 f97d8e27aead66108d8d0f1b57994875ddcb4f006f1fbb1ac48e142101c2b0e3 last_trade_price 54,436 3,149,190 52-52 c8543ba43dd91b17a6fc15128d73f8e1ebe20b54e7877510976077836d214bea market_resolved 3,360 541,726 53-53 b0bd8cc90eb180e8af7e68f1c3e7558abb99c1c639d4d9a6964adedafb769df4 new_market 1,247 137,483 54-54 a3c7775ed670c1b7fff2fb717d2fc1bbb32b46954f660451a0dd9598a6b73fb4 price_change 96,787,426 940,800,429 55-424 52c74eaf12bd6463b32a7730c41cd60f8d14a1afd2f55c41d9b9dcdf9d4bf056 tick_size_change 4,260 156,153 425-425 816df99fed316717501d28a4658242b36825c1357df14b11c568563d8a966d1b EVENT MIX count share price_change 96,787,426 87.90% best_bid_ask 13,114,162 11.91% book 144,437 0.13% last_trade_price 54,436 0.05% tick_size_change 4,260 <0.01% market_resolved 3,360 <0.01% new_market 1,247 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,114,390 13,114,162 228 83,623 PARTIAL book 144,437 144,437 0 18,455 PARTIAL last_trade_price 54,436 54,436 0 3,906 PARTIAL market_resolved 3,360 3,360 0 3,333 PARTIAL new_market 1,247 1,247 0 908 PARTIAL price_change 96,790,758 96,787,426 3,332 137,256 PARTIAL tick_size_change 4,260 4,260 0 1,065 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 13,113,184 12,588,331 5ms 10ms 87ms 4.0s 0 transport_latency_assumed best_bid_ask e 13,112,406 37,340 42ms 48ms 167ms 12.7s 0 transport_latency_assumed best_bid_ask g 13,111,296 3,081 75ms 92ms 312ms 36.0s 0 transport_latency_assumed best_bid_ask h 13,112,529 485,410 16ms 26ms 126ms 19.1s 0 transport_latency_assumed book c 117,779 109,681 7ms 104ms 17.3h 94.9d 0 book_staleness book e 116,262 6,337 44ms 376ms 2.2h 94.9d 0 book_staleness book g 120,687 10,453 84ms 4.7s 1.7d 113.4d 0 book_staleness book h 121,967 17,966 20ms 2.4s 1.7d 94.9d 0 book_staleness last_trade_price c 54,138 50,760 6ms 21ms 212ms 963ms 0 transport_latency_assumed last_trade_price e 54,187 304 44ms 144ms 2.8s 12.8s 0 transport_latency_assumed last_trade_price g 53,889 78 81ms 315ms 6.4s 36.0s 0 transport_latency_assumed last_trade_price h 54,101 3,294 18ms 50ms 291ms 6.9s 0 transport_latency_assumed market_resolved c 3,333 3,229 5ms 11ms 232ms 55.7s 0 transport_latency_assumed market_resolved e 3,332 33 103ms 195ms 583ms 1.0min 0 transport_latency_assumed market_resolved g 3,332 25 147ms 284ms 604ms 1.2s 0 transport_latency_assumed market_resolved h 3,332 73 34ms 70ms 499ms 1.0min 0 transport_latency_assumed new_market c 908 597 73ms 20.7s 1.3min 3.4h 0 transport_latency_assumed new_market e 908 141 160ms 18.7s 1.4min 4.2h 0 transport_latency_assumed new_market g 908 78 243ms 24.8s 1.2min 2.6h 0 transport_latency_assumed new_market h 908 431 85ms 21.5s 1.4min 7.5h 0 transport_latency_assumed price_change c 96,752,396 92,322,480 5ms 12ms 116ms 4.6s 0 transport_latency_assumed price_change e 96,720,478 341,614 42ms 57ms 283ms 12.8s 0 transport_latency_assumed price_change g 96,662,996 37,342 75ms 105ms 590ms 36.6s 0 transport_latency_assumed price_change h 96,722,978 4,085,990 17ms 31ms 171ms 19.2s 0 transport_latency_assumed tick_size_change c 4,260 4,149 5ms 7ms 45ms 146ms 0 transport_latency_assumed tick_size_change e 4,260 4 42ms 46ms 128ms 226ms 0 transport_latency_assumed tick_size_change g 4,260 4 75ms 87ms 239ms 5.5s 0 transport_latency_assumed tick_size_change h 4,260 103 16ms 23ms 72ms 241ms 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-20/07/2026-09-20T07.parquet sha256sum 2026-09-20T07.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.