Hour audit: 2026-09-26T09
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-26T09 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-26T09:00:00.000270611+00:00 · last event 2026-09-26T09:59:59.999669631+00:00
VOLUME 104,746,699 rows · 1,046,459,716 bytes (997.98 MiB) · 7 products, all holding rows
WITNESSES hik — 3 machines contributed rows
captured k: 104,690,289 · h: 104,676,195 · i: 104,650,294 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 96,113,982 (91.76%) · h: 6,496,085 (6.20%) · i: 2,136,632 (2.04%) (rows of the merged file that came from it; these partition it)
5 expected (cghik), 2 contributed nothing: c, g
INTEGRITY sha256 1d32a2f5b3bdda37124c697b5bedcb2488800ff9a309b0268fa4d0580eeca51a
the corpus checksum ledger names this file with the same digest
joined 104,746,831 to merged 104,746,699, minus 132 (minus 0.0001%)
boundary drops 132 · 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-26T10:52:52Z 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,808,957 116,515,317 0-41 eb4be52317afb39840208ebafa9a5431e41728daa1562d7c14afe5038fb0d85f book 117,668 12,241,304 42-42 9fdaac1b4ec354ab68897e68fce9ad82d4d6686e9e019539bba7abd4516ca095 last_trade_price 51,301 2,877,543 43-43 1e870634c16becca5146017f6a47e9862689486336eec80370ef037b42e8a9ae market_resolved 710 110,253 44-44 b24f7d985a5f7d9d278092a5d256062b8f79a505bf053ee9ccee354257b98777 new_market 823 91,972 45-45 28cbf0f46fb6e7f4b663194837d642b718c86747da3fec0c42373c06d5772fe1 price_change 93,763,596 913,300,276 46-403 7eca0947f02b96a1f5ed7a072eb13a4be446ae76d5657bf58cde57a3624a944a tick_size_change 3,644 131,338 404-404 20ef096c4bb1e2aa94adba42da1bdfea0010db30dde485a682bbe5ca9c3264a8 EVENT MIX count share price_change 93,763,596 89.51% best_bid_ask 10,808,957 10.32% book 117,668 0.11% last_trade_price 51,301 0.05% tick_size_change 3,644 <0.01% new_market 823 <0.01% market_resolved 710 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,808,973 10,808,957 16 47,450 PARTIAL book 117,668 117,668 0 9,066 PARTIAL last_trade_price 51,301 51,301 0 3,096 PARTIAL market_resolved 710 710 0 683 PARTIAL new_market 823 823 0 605 PARTIAL price_change 93,763,712 93,763,596 116 87,836 PARTIAL tick_size_change 3,644 3,644 0 911 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,807,895 593,823 18ms 25ms 119ms 42.5s 0 transport_latency_assumed best_bid_ask i 10,807,930 185,634 23ms 28ms 94ms 4.2s 0 transport_latency_assumed best_bid_ask k 10,807,944 10,029,500 12ms 18ms 84ms 9.2s 0 transport_latency_assumed book h 109,075 16,576 22ms 110ms 2.6d 100.9d 0 book_staleness book i 105,388 7,583 25ms 88ms 2.3h 100.9d 0 book_staleness book k 110,632 93,509 16ms 122ms 3.7d 100.9d 0 book_staleness last_trade_price h 51,095 4,732 19ms 49ms 334ms 8.0s 0 transport_latency_assumed last_trade_price i 51,126 1,719 24ms 64ms 496ms 3.8s 0 transport_latency_assumed last_trade_price k 51,071 44,850 13ms 36ms 256ms 2.4s 0 transport_latency_assumed market_resolved h 683 35 19ms 11.8s 52.2s 58.6s 0 transport_latency_assumed market_resolved i 683 95 24ms 22.3s 57.5s 57.8s 0 transport_latency_assumed market_resolved k 683 580 13ms 66ms 41.4s 55.3s 0 transport_latency_assumed new_market h 605 260 125ms 32.1s 52.1s 1.4min 0 transport_latency_assumed new_market i 605 241 107ms 31.3s 44.6s 1.7min 0 transport_latency_assumed new_market k 605 322 82ms 31.4s 47.5s 1.6min 0 transport_latency_assumed price_change h 93,703,198 5,880,496 18ms 29ms 161ms 42.5s 0 transport_latency_assumed price_change i 93,680,918 1,941,318 23ms 31ms 156ms 4.2s 0 transport_latency_assumed price_change k 93,715,710 85,941,782 12ms 20ms 108ms 9.2s 0 transport_latency_assumed tick_size_change h 3,644 163 18ms 22ms 65ms 300ms 0 transport_latency_assumed tick_size_change i 3,644 42 23ms 27ms 84ms 334ms 0 transport_latency_assumed tick_size_change k 3,644 3,439 12ms 16ms 67ms 153ms 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/09/2026-09-26T09.parquet sha256sum 2026-09-26T09.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.