Hour audit: 2026-09-26T11
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, 2 contributed no rows: c, g. The hour is still whole on minutes; it simply rests on 3 machines rather than 5.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-26T11 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-26T11:00:00.000116926+00:00 · last event 2026-09-26T11:59:59.999976872+00:00
VOLUME 101,092,430 rows · 1,052,797,729 bytes (1004.03 MiB) · 7 products, all holding rows
WITNESSES hik — 3 machines contributed rows
captured k: 100,642,483 · i: 100,618,317 · h: 97,997,180 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 93,260,764 (92.25%) · i: 2,717,710 (2.69%) · h: 5,113,956 (5.06%) (rows of the merged file that came from it; these partition it)
5 expected (cghik), 2 contributed nothing: c, g
INTEGRITY sha256 219b596195ced9109fcc08b5426027c0bbc2a6a62142190126dcdd7c95cb4385
the corpus checksum ledger names this file with the same digest
joined 101,092,680 to merged 101,092,430, minus 250 (minus 0.0002%)
boundary drops 250 · 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-26T12:51:09Z as hik
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 status feed unobserved for this hour. Our incident register was last checked against the venue's feed at 2026-09-23T20:35Z, before this hour ended, so nothing has looked yet. This is a could-not-look and never an all-clear.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,745,390 116,262,602 0-40 72d5f357b3f256bcc7c599c503788e00f94bf98f2334e62ca674ea3b87ab7a39 book 521,371 53,341,535 41-42 59c082377a6f7634d4680197f6fc20bd94f5b5b0c8e63e245da70ca2e0136659 last_trade_price 46,340 2,661,743 43-43 a847291f6ab518ad3b00f1a78d5cb1b4b427561a892f4581077d55f010e1926c market_resolved 897 137,420 44-44 7e06cec7fc04b522aec8475a743912390e231b8e2d79243316d519e2e2bd77e6 new_market 918 104,969 45-45 c1582ab6bf0c23c267eabec5a603a4b019d02f8db1cf5cda20e48ca0e8d3f045 price_change 89,775,298 879,059,295 46-388 9efd2d8e271ee28584de86f5d68e26de9292c6062cd7d035dea283691e6d908f tick_size_change 2,216 81,837 389-389 eaeef3629d6a7114d51ec2782c59763343aae280bc384294867d941dc5c7606f EVENT MIX count share price_change 89,775,298 88.81% best_bid_ask 10,745,390 10.63% book 521,371 0.52% last_trade_price 46,340 0.05% tick_size_change 2,216 <0.01% new_market 918 <0.01% market_resolved 897 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,745,420 10,745,390 30 47,387 PARTIAL book 521,377 521,371 6 210,494 PARTIAL last_trade_price 46,340 46,340 0 3,227 PARTIAL market_resolved 897 897 0 850 PARTIAL new_market 918 918 0 694 PARTIAL price_change 89,775,512 89,775,298 214 88,106 PARTIAL tick_size_change 2,216 2,216 0 554 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,415,574 457,526 18ms 26ms 152ms 43.5s 0 transport_latency_assumed best_bid_ask i 10,744,430 242,151 20ms 24ms 77ms 3.8s 0 transport_latency_assumed best_bid_ask k 10,744,558 10,045,713 12ms 16ms 81ms 16.9s 0 transport_latency_assumed book h 516,767 431,896 37.3min 4.6d 34.9d 119.6d 0 book_staleness book i 95,397 9,685 22ms 57ms 1.8h 93.1d 0 book_staleness book k 95,897 79,790 15ms 42ms 4.5h 101.0d 0 book_staleness last_trade_price h 44,946 2,790 19ms 49ms 314ms 8.5s 0 transport_latency_assumed last_trade_price i 46,140 1,926 22ms 39ms 273ms 1.9s 0 transport_latency_assumed last_trade_price k 46,166 41,624 13ms 26ms 213ms 9.2s 0 transport_latency_assumed market_resolved h 847 75 19ms 227ms 52.7s 52.8s 0 transport_latency_assumed market_resolved i 850 145 21ms 29.7s 49.9s 50.3s 0 transport_latency_assumed market_resolved k 850 677 13ms 32.4s 52.7s 53.0s 0 transport_latency_assumed new_market h 694 214 152ms 12.6s 35.0s 1.6min 0 transport_latency_assumed new_market i 694 466 71ms 13.7s 1.0min 1.6min 0 transport_latency_assumed new_market k 694 238 131ms 11.2s 57.4s 1.6min 0 transport_latency_assumed price_change h 87,016,200 4,221,360 18ms 31ms 203ms 43.5s 0 transport_latency_assumed price_change i 89,728,590 2,463,306 21ms 26ms 123ms 3.9s 0 transport_latency_assumed price_change k 89,752,102 83,090,632 13ms 18ms 106ms 20.7s 0 transport_latency_assumed tick_size_change h 2,152 95 18ms 31ms 86ms 167ms 0 transport_latency_assumed tick_size_change i 2,216 31 21ms 24ms 62ms 178ms 0 transport_latency_assumed tick_size_change k 2,216 2,090 13ms 15ms 50ms 132ms 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-26/11/2026-09-26T11.parquet sha256sum 2026-09-26T11.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.