Hour audit: 2026-09-26T03
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-26T03 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-26T03:00:00.000196142+00:00 · last event 2026-09-26T03:59:59.999997840+00:00
VOLUME 115,075,352 rows · 1,178,257,906 bytes (1.10 GiB) · 7 products, all holding rows
WITNESSES hik — 3 machines contributed rows
captured k: 114,907,329 · h: 114,886,228 · i: 113,700,185 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 105,065,845 (91.30%) · h: 6,955,017 (6.04%) · i: 3,054,490 (2.65%) (rows of the merged file that came from it; these partition it)
5 expected (cghik), 2 contributed nothing: c, g
INTEGRITY sha256 8a58a64ef90231d263bcf1f1efd7441d24fb1f1415241e15afbea19162e2c604
the corpus checksum ledger names this file with the same digest
joined 115,075,648 to merged 115,075,352, minus 296 (minus 0.0003%)
boundary drops 296 · 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-26T05:01:31Z 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 11,849,054 129,399,303 0-45 e0f37fa93898567fb7535ac78de0bf249ebbd90c0ecfadcf3c7bce895ccd795b book 364,248 34,764,611 46-47 01a50550afa5ac377dc05ab2d051be46d0c65f7bd43a5317eb0ff3645ffca662 last_trade_price 46,655 2,655,080 48-48 c196743c217cc69812881fb6e7436927e31ab73df1413ab4d9f68a937d8c7a03 market_resolved 2,629 397,279 49-49 9d9ca8211237f2e22b2dcecc387f9c231fd7e4542c7e01adc066ea793bd07f68 new_market 1,028 110,559 50-50 be9c14bd7f4b176221e844be1fa7e609f3524e28c7205b0cfe3bd8e202521676 price_change 102,806,674 1,009,441,026 51-443 3cfcaa40054556036182128d38e9abf9d7ed3c7f66ac78643ad5178a75ee2893 tick_size_change 5,064 180,695 444-444 75a1ce7430b12f7b855e9cf49eef3eab197a78cb08019e3af545b3faaee0cb7d EVENT MIX count share price_change 102,806,674 89.34% best_bid_ask 11,849,054 10.30% book 364,248 0.32% last_trade_price 46,655 0.04% tick_size_change 5,064 <0.01% market_resolved 2,629 <0.01% new_market 1,028 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,849,076 11,849,054 22 56,989 PARTIAL book 364,312 364,248 64 119,146 PARTIAL last_trade_price 46,655 46,655 0 3,036 PARTIAL market_resolved 2,629 2,629 0 2,526 PARTIAL new_market 1,028 1,028 0 729 PARTIAL price_change 102,806,884 102,806,674 210 106,920 PARTIAL tick_size_change 5,064 5,064 0 1,266 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 11,847,033 654,587 18ms 25ms 142ms 16.2s 0 transport_latency_assumed best_bid_ask i 11,737,039 273,812 21ms 26ms 82ms 4.0s 0 transport_latency_assumed best_bid_ask k 11,847,414 10,920,655 12ms 18ms 92ms 7.6s 0 transport_latency_assumed book h 233,911 134,443 41.4s 3.3d 34.6d 119.2d 0 book_staleness book i 108,992 18,804 23ms 2.0min 7.5d 100.7d 0 book_staleness book k 243,401 211,001 54.8s 3.4d 34.6d 119.2d 0 book_staleness last_trade_price h 46,437 3,778 19ms 46ms 301ms 7.4s 0 transport_latency_assumed last_trade_price i 46,186 2,050 22ms 38ms 210ms 2.0s 0 transport_latency_assumed last_trade_price k 46,443 40,827 14ms 30ms 207ms 2.1s 0 transport_latency_assumed market_resolved h 2,526 295 19ms 26.4s 55.2s 56.4s 0 transport_latency_assumed market_resolved i 2,514 328 22ms 26.5s 54.7s 2.4min 0 transport_latency_assumed market_resolved k 2,526 2,006 13ms 26.4s 50.5s 56.6s 0 transport_latency_assumed new_market h 729 327 134ms 11.0s 38.1s 1.5min 0 transport_latency_assumed new_market i 720 379 97ms 13.5s 44.8s 1.4min 0 transport_latency_assumed new_market k 729 322 101ms 11.9s 44.4s 1.6min 0 transport_latency_assumed price_change h 102,750,528 6,161,218 18ms 29ms 201ms 16.8s 0 transport_latency_assumed price_change i 101,799,710 2,759,024 21ms 27ms 127ms 4.4s 0 transport_latency_assumed price_change k 102,761,752 93,886,432 13ms 19ms 121ms 8.4s 0 transport_latency_assumed tick_size_change h 5,064 369 18ms 29ms 81ms 198ms 0 transport_latency_assumed tick_size_change i 5,024 93 21ms 26ms 65ms 174ms 0 transport_latency_assumed tick_size_change k 5,064 4,602 12ms 19ms 79ms 194ms 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/03/2026-09-26T03.parquet sha256sum 2026-09-26T03.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.