Hour audit: 2026-09-21T01
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-21T01 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-21T01:00:00.000054989+00:00 · last event 2026-09-21T01:59:59.999949438+00:00
VOLUME 113,358,819 rows · 1,153,692,559 bytes (1.07 GiB) · 7 products, all holding rows
WITNESSES cefh — 4 machines contributed rows
captured c: 113,236,522 · f: 113,209,615 · e: 113,183,771 · h: 113,050,939 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 108,515,682 (95.73%) · f: 202,438 (0.18%) · e: 389,808 (0.34%) · h: 4,250,891 (3.75%) (rows of the merged file that came from it; these partition it)
5 expected (cefgh), 1 contributed nothing: g
INTEGRITY sha256 c449f0018f10cedb057d30c9d0aab0208b46b1586df4427628cee07d217b7d85
the corpus checksum ledger names this file with the same digest
joined 113,360,200 to merged 113,358,819, minus 1,381 (minus 0.0012%)
boundary drops 1,381 · 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-21T05:33:00Z 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,778,486 131,496,587 0-44 10996fb20e4cd118e80118e39545d1d166654225db1ceb0ca409ece02fe59c14 book 162,060 17,446,987 45-45 524695f6e17679abf7e7d153a8e3e29eacbeb79941872d4d1b5843dd0e625396 last_trade_price 53,047 3,044,535 46-46 cab75565684bc21a72219175689a57f245cf2c0befbd9a1e1f4be5fe302eb836 market_resolved 2,525 390,579 47-47 b9e6d3d1dc7157ad4b42e58109ff72e53c1607cada4a3e1569a1bf73ea7b96ad new_market 1,133 120,732 48-48 85781541ded5ef2c91cd8daa16f5d96129759891fabc28f4c9db79caa9cb7377 price_change 101,357,776 999,767,345 49-435 80ffe71624db9497a2c861dad2f920d6e24ca7cd2871f2431d58ee52d6846950 tick_size_change 3,792 138,319 436-436 0015f7c8980f21ed8945db07d4ee6a26bfb54101b487c2a466a4226c2f98a571 EVENT MIX count share price_change 101,357,776 89.41% best_bid_ask 11,778,486 10.39% book 162,060 0.14% last_trade_price 53,047 0.05% tick_size_change 3,792 <0.01% market_resolved 2,525 <0.01% new_market 1,133 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,778,628 11,778,486 142 69,076 PARTIAL book 162,096 162,060 36 28,734 PARTIAL last_trade_price 53,047 53,047 0 3,438 PARTIAL market_resolved 2,552 2,525 27 2,470 PARTIAL new_market 1,133 1,133 0 791 PARTIAL price_change 101,358,952 101,357,776 1,176 117,178 PARTIAL tick_size_change 3,792 3,792 0 948 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,777,212 11,328,569 4ms 10ms 83ms 1.7s 0 transport_latency_assumed best_bid_ask e 11,776,932 33,279 41ms 48ms 144ms 5.3s 0 transport_latency_assumed best_bid_ask f 11,776,808 15,518 46ms 55ms 155ms 3.6s 0 transport_latency_assumed best_bid_ask h 11,777,166 401,120 18ms 44ms 163ms 9.7s 0 transport_latency_assumed book c 120,485 113,299 6ms 9.4s 11.7d 95.6d 0 book_staleness book e 119,655 12,816 44ms 3.3s 2.4d 95.6d 0 book_staleness book f 123,287 15,974 49ms 47.0s 12.3d 114.1d 0 book_staleness book h 122,501 19,971 22ms 27.1s 10.7d 95.6d 0 book_staleness last_trade_price c 52,903 49,787 5ms 18ms 150ms 943ms 0 transport_latency_assumed last_trade_price e 52,913 302 43ms 114ms 917ms 5.3s 0 transport_latency_assumed last_trade_price f 52,931 202 48ms 108ms 870ms 3.7s 0 transport_latency_assumed last_trade_price h 52,976 2,756 19ms 67ms 352ms 9.5s 0 transport_latency_assumed market_resolved c 2,443 1,956 5ms 36.2s 1.0min 1.0min 0 transport_latency_assumed market_resolved e 2,470 44 42ms 35.0s 59.7s 1.0min 0 transport_latency_assumed market_resolved f 2,470 9 47ms 35.0s 1.0min 1.1min 0 transport_latency_assumed market_resolved h 2,443 516 19ms 40.7s 1.0min 1.1min 0 transport_latency_assumed new_market c 791 399 145ms 20.4s 30.8s 42.5s 0 transport_latency_assumed new_market e 791 157 255ms 19.7s 33.3s 41.2s 0 transport_latency_assumed new_market f 791 233 192ms 19.0s 33.0s 43.8s 0 transport_latency_assumed new_market h 791 344 169ms 20.3s 32.8s 36.3s 0 transport_latency_assumed price_change c 101,278,896 97,018,036 4ms 12ms 90ms 1.9s 0 transport_latency_assumed price_change e 101,227,218 343,198 42ms 53ms 228ms 9.2s 0 transport_latency_assumed price_change f 101,249,536 170,498 47ms 59ms 239ms 8.3s 0 transport_latency_assumed price_change h 101,091,270 3,826,044 18ms 48ms 177ms 9.7s 0 transport_latency_assumed tick_size_change c 3,792 3,636 4ms 10ms 73ms 143ms 0 transport_latency_assumed tick_size_change e 3,792 12 42ms 53ms 148ms 237ms 0 transport_latency_assumed tick_size_change f 3,792 4 47ms 58ms 124ms 1.5s 0 transport_latency_assumed tick_size_change h 3,792 140 18ms 48ms 112ms 166ms 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/01/2026-09-21T01.parquet sha256sum 2026-09-21T01.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.