Hour audit: 2026-09-26T01
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-26T01 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-26T01:00:00.000311535+00:00 · last event 2026-09-26T01:59:59.999962184+00:00
VOLUME 122,562,724 rows · 1,307,439,977 bytes (1.22 GiB) · 7 products, all holding rows
WITNESSES hik — 3 machines contributed rows
captured h: 120,749,387 · i: 118,792,034 · k: 100,684,392 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 18,944,168 (15.46%) · i: 13,032,031 (10.63%) · k: 90,586,525 (73.91%) (rows of the merged file that came from it; these partition it)
5 expected (cghik), 2 contributed nothing: c, g
INTEGRITY sha256 f469986566b7fbf95e6f145dacf22d661223f5ec8a7240438ef466043d7bc2d7
the corpus checksum ledger names this file with the same digest
joined 122,565,302 to merged 122,562,724, minus 2,578 (minus 0.0021%)
boundary drops 2,578 · 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-26T03:00:11Z 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 12,010,920 133,175,877 0-45 587ab0c9306ac5e2498a182643e37de6c4f858d999c76c755685082c7bd1c29d book 1,846,597 79,268,744 46-53 c592763f0420155fdc7648e630c5d7785fd66e92c124010461062c8cf227b3d4 last_trade_price 45,509 2,646,523 54-54 83af6454a1b19593d9b37003f9d7c8b9e777845801096a495a94d0e15491b5d2 market_resolved 2,286 267,615 55-55 62453cc25d37ff54bb16f52f12a93668a5d9e44d230e9e3409833faf344c5e9c new_market 1,110 102,776 56-56 4526744e0f4a74851802c12929cee836f0f9f3fd562a2bdce508c9ba78dc1eb2 price_change 108,646,822 1,090,244,865 57-471 a78dfe5365af41b2a578ddfa7717f07cba7bc05e9e9c93c4841de25ffde34299 tick_size_change 9,480 341,146 472-472 6ad093019058ca5b5043a4bf8a40520ac15890a653c56e4ad0605013937feded EVENT MIX count share price_change 108,646,822 88.65% best_bid_ask 12,010,920 9.80% book 1,846,597 1.51% last_trade_price 45,509 0.04% tick_size_change 9,480 <0.01% market_resolved 2,286 <0.01% new_market 1,110 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,011,252 12,010,920 332 50,121 PARTIAL book 1,846,623 1,846,597 26 217,155 PARTIAL last_trade_price 45,509 45,509 0 3,239 PARTIAL market_resolved 2,286 2,286 0 1,654 PARTIAL new_market 1,110 1,110 0 655 PARTIAL price_change 108,649,042 108,646,822 2,220 88,516 PARTIAL tick_size_change 9,480 9,480 0 2,370 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 12,009,390 1,870,352 18ms 42ms 136ms 43.3s 0 transport_latency_assumed best_bid_ask i 11,831,117 1,224,475 20ms 25ms 89ms 4.0s 0 transport_latency_assumed best_bid_ask k 9,847,113 8,916,093 13ms 20ms 97ms 22.3s 0 transport_latency_assumed book h 94,304 13,591 22ms 87ms 11.4h 100.6d 0 book_staleness book i 99,989 22,303 22ms 387ms 4.2d 119.1d 0 book_staleness book k 1,825,315 1,810,703 2.3h 4.2d 44.2d 119.1d 0 book_staleness last_trade_price h 45,290 7,607 19ms 64ms 420ms 6.9s 0 transport_latency_assumed last_trade_price i 44,896 6,598 21ms 40ms 235ms 1.6s 0 transport_latency_assumed last_trade_price k 36,609 31,304 13ms 35ms 249ms 2.4s 0 transport_latency_assumed market_resolved h 1,654 135 18ms 20.7s 50.8s 55.4s 0 transport_latency_assumed market_resolved i 1,645 337 20ms 21.4s 54.8s 2.2min 0 transport_latency_assumed market_resolved k 2,082 1,814 15ms 12.2min 17.4min 18.8min 0 transport_latency_assumed new_market h 655 246 126ms 16.7s 50.6s 1.5min 0 transport_latency_assumed new_market i 655 322 76ms 17.1s 51.0s 1.7min 0 transport_latency_assumed new_market k 903 542 187ms 9.2min 10.4min 13.7min 0 transport_latency_assumed price_change h 108,588,614 17,050,760 18ms 45ms 170ms 48.9s 0 transport_latency_assumed price_change i 106,804,436 11,776,538 20ms 27ms 116ms 4.0s 0 transport_latency_assumed price_change k 88,964,750 79,819,524 13ms 22ms 111ms 23.0s 0 transport_latency_assumed tick_size_change h 9,480 1,477 18ms 52ms 486ms 13.3s 0 transport_latency_assumed tick_size_change i 9,296 1,458 20ms 27ms 112ms 330ms 0 transport_latency_assumed tick_size_change k 7,620 6,545 13ms 29ms 280ms 1.9s 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/01/2026-09-26T01.parquet sha256sum 2026-09-26T01.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.