Hour audit: 2026-09-20T21
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-20T21 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-20T21:00:00.000108292+00:00 · last event 2026-09-20T21:59:59.999952979+00:00
VOLUME 122,444,737 rows · 1,349,904,426 bytes (1.26 GiB) · 7 products, all holding rows
WITNESSES cefh — 4 machines contributed rows
captured e: 121,188,641 · h: 118,275,335 · f: 116,659,067 · c: 107,687,964 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 2,304,720 (1.88%) · h: 16,910,224 (13.81%) · f: 877,942 (0.72%) · c: 102,351,851 (83.59%) (rows of the merged file that came from it; these partition it)
5 expected (cefgh), 1 contributed nothing: g
INTEGRITY sha256 7fe6385ace4b8db191a534065d69b045f37d3f5dea2523137184914ad10aecd6
the corpus checksum ledger names this file with the same digest
joined 122,454,294 to merged 122,444,737, minus 9,557 (minus 0.0078%)
boundary drops 9,557 · 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-21T03:56:13Z 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 13,567,276 154,299,483 0-51 b03a7f7402a67fed910288262e9649423ce2ed4a3d7dd717ffb2b7447b9cedac book 1,216,823 65,853,891 52-56 a83ff2b3ed55ec21a7acef3c3b18a358dde5f5fd04f5f63a73c8f603d37f0d28 last_trade_price 56,667 3,291,240 57-57 a81275606d098a00e1df5a17bfefef0f4058923274c57e5ba42851510b327aba market_resolved 5,865 868,563 58-58 9702b78b47e0c084138974f887dc5a436f9038fe5573cbaabbc8af4b15e98112 new_market 2,232 228,516 59-59 1c553759a12097ef55bb8d59ea7284ecbb7099c9d369f601f49d12c7b235b358 price_change 107,587,414 1,123,662,305 60-470 0087ca8547484ac7bb2e344c649cf3d7883d44ab8ab757b1331910c5b0b275bd tick_size_change 8,460 309,947 471-471 4cf35be26369e162df6db9f4b407339eb50888dd4b66a96de1128e7d83afc5a7 EVENT MIX count share price_change 107,587,414 87.87% best_bid_ask 13,567,276 11.08% book 1,216,823 0.99% last_trade_price 56,667 0.05% tick_size_change 8,460 <0.01% market_resolved 5,865 <0.01% new_market 2,232 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,568,125 13,567,276 849 80,100 PARTIAL book 1,217,563 1,216,823 740 167,362 PARTIAL last_trade_price 56,675 56,667 8 4,009 PARTIAL market_resolved 5,865 5,865 0 5,380 PARTIAL new_market 2,232 2,232 0 1,491 PARTIAL price_change 107,595,374 107,587,414 7,960 128,567 PARTIAL tick_size_change 8,460 8,460 0 2,115 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,936,368 11,376,983 5ms 12ms 157ms 4.5s 0 transport_latency_assumed best_bid_ask e 13,562,341 243,566 41ms 55ms 302ms 18.3s 0 transport_latency_assumed best_bid_ask f 13,018,039 80,978 45ms 61ms 301ms 19.6s 0 transport_latency_assumed best_bid_ask h 13,248,359 1,865,749 18ms 35ms 201ms 53.7s 0 transport_latency_assumed book c 1,134,611 1,121,617 6.5min 2.2d 43.2d 114.0d 0 book_staleness book e 118,801 5,552 45ms 1.6s 26.2min 114.0d 0 book_staleness book f 475,925 73,115 2.2min 1.9d 40.1d 114.0d 0 book_staleness book h 114,994 16,539 22ms 116ms 46.3s 95.4d 0 book_staleness last_trade_price c 50,434 47,535 6ms 25ms 258ms 1.9s 0 transport_latency_assumed last_trade_price e 55,830 1,149 46ms 498ms 9.5s 18.1s 0 transport_latency_assumed last_trade_price f 54,319 622 48ms 223ms 4.7s 19.6s 0 transport_latency_assumed last_trade_price h 55,407 7,361 19ms 75ms 607ms 22.7s 0 transport_latency_assumed market_resolved c 5,169 4,980 5ms 49ms 4.7min 4.9min 0 transport_latency_assumed market_resolved e 5,380 80 43ms 124ms 528ms 48.1s 0 transport_latency_assumed market_resolved f 5,291 65 46ms 132ms 4.2min 5.4min 0 transport_latency_assumed market_resolved h 5,284 740 19ms 63ms 38.6s 2.5min 0 transport_latency_assumed new_market c 1,491 988 94ms 20.8s 1.2min 13.3h 0 transport_latency_assumed new_market e 1,491 358 222ms 23.2s 1.3min 6.3h 0 transport_latency_assumed new_market f 1,479 261 184ms 18.5s 1.3min 13.3h 0 transport_latency_assumed new_market h 1,474 625 160ms 22.4s 1.3min 4.1h 0 transport_latency_assumed price_change c 94,552,503 89,792,639 5ms 14ms 177ms 11.1s 0 transport_latency_assumed price_change e 107,436,338 2,053,879 42ms 70ms 905ms 18.3s 0 transport_latency_assumed price_change f 103,095,706 722,849 46ms 73ms 594ms 19.7s 0 transport_latency_assumed price_change h 104,841,533 15,018,047 18ms 41ms 252ms 54.0s 0 transport_latency_assumed tick_size_change c 7,388 7,109 5ms 8ms 89ms 1.5s 0 transport_latency_assumed tick_size_change e 8,460 136 41ms 47ms 118ms 549ms 0 transport_latency_assumed tick_size_change f 8,308 52 45ms 52ms 214ms 539ms 0 transport_latency_assumed tick_size_change h 8,284 1,163 18ms 25ms 76ms 1.5s 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/21/2026-09-20T21.parquet sha256sum 2026-09-20T21.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.