Hour audit: 2026-09-26T16
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-26T16 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-26T16:00:00.000711291+00:00 · last event 2026-09-26T16:59:59.999984079+00:00
VOLUME 136,003,628 rows · 1,523,412,743 bytes (1.42 GiB) · 7 products, all holding rows
WITNESSES chik — 4 machines contributed rows
captured i: 125,429,131 · h: 119,925,493 · k: 115,008,984 · c: 69,862,369 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 11,104,094 (8.16%) · h: 10,664,464 (7.84%) · k: 51,136,801 (37.60%) · c: 63,098,269 (46.39%) (rows of the merged file that came from it; these partition it)
5 expected (cghik), 1 contributed nothing: g
INTEGRITY sha256 6f04bbbf865410c80787c491cd07d8f1461f865d0425ba5cd736f1897ae76555
the corpus checksum ledger names this file with the same digest
joined 136,004,182 to merged 136,003,628, minus 554 (minus 0.0004%)
boundary drops 554 · 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-27T00:38:37Z as chik
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 13,694,986 157,220,764 0-52 59ba0b97a47022c6781f956cd68f72ae115bab982be2bd4e8fc2b8424015a1d4 book 5,071,295 133,979,351 53-72 6dbd419be220e44059258e1e5ec13ea77bca09072dcd72983809ade312599142 last_trade_price 63,114 3,635,211 73-73 84c4e7e74fa900ee4349bc752623b3b946873f03c912d651fd748d0a28807312 market_resolved 11,073 671,426 74-74 7a25a1764578b58abbfafbe311f34498757737de42e5ddc5db27b426712ad6d1 new_market 9,379 416,591 75-75 56b3741eb651bd8edce8265c28b6301146b354c526b58786ce8125ed041e6c6e price_change 117,149,141 1,225,773,810 76-522 9a16b53e8ba11b60528643a2fe5595b1cc84301a48032ec9a2a05b8efaacccde tick_size_change 4,640 169,779 523-523 a10a752792a24bb466db3f5e03102b364b95402cf11201ba7e1b0e3127a1adc9 EVENT MIX count share price_change 117,149,141 86.14% best_bid_ask 13,694,986 10.07% book 5,071,295 3.73% last_trade_price 63,114 0.05% market_resolved 11,073 <0.01% new_market 9,379 <0.01% tick_size_change 4,640 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,695,032 13,694,986 46 70,269 PARTIAL book 5,071,347 5,071,295 52 215,994 PARTIAL last_trade_price 63,114 63,114 0 4,339 PARTIAL market_resolved 11,073 11,073 0 3,676 PARTIAL new_market 9,379 9,379 0 2,409 PARTIAL price_change 117,149,597 117,149,141 456 107,491 PARTIAL tick_size_change 4,640 4,640 0 1,160 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 6,832,652 6,180,949 5ms 17ms 178ms 3.7s 0 transport_latency_assumed best_bid_ask h 12,393,751 1,044,296 19ms 60ms 400ms 1.2min 0 transport_latency_assumed best_bid_ask i 13,096,628 1,157,716 21ms 32ms 179ms 7.9s 0 transport_latency_assumed best_bid_ask k 11,893,037 5,312,025 13ms 23ms 196ms 39.9s 0 transport_latency_assumed book c 4,666,827 4,343,527 52.1min 5.1d 44.9d 119.8d 0 book_staleness book h 976,314 288,155 26.7min 4.8d 40.9d 119.8d 0 book_staleness book i 554,405 46,088 6.4min 4.8d 35.1d 119.7d 0 book_staleness book k 1,393,623 393,525 32.2min 4.8d 42.1d 119.7d 0 book_staleness last_trade_price c 28,658 25,182 6ms 31ms 330ms 1.8s 0 transport_latency_assumed last_trade_price h 57,346 6,453 22ms 83ms 672ms 38.5s 0 transport_latency_assumed last_trade_price i 59,324 6,774 23ms 75ms 898ms 3.6s 0 transport_latency_assumed last_trade_price k 52,361 24,705 14ms 40ms 348ms 17.7s 0 transport_latency_assumed market_resolved c 9,017 7,069 9.5min 20.8min 25.6min 27.9min 0 transport_latency_assumed market_resolved h 3,646 794 26ms 4.3min 6.6min 6.8min 0 transport_latency_assumed market_resolved i 3,698 688 22ms 35.8s 5.6min 5.9min 0 transport_latency_assumed market_resolved k 4,992 2,522 23ms 11.1min 15.7min 16.5min 0 transport_latency_assumed new_market c 8,654 6,807 8.8min 22.0min 24.4min 27.4min 0 transport_latency_assumed new_market h 2,411 674 157ms 48.6s 4.1min 5.3min 0 transport_latency_assumed new_market i 2,441 750 130ms 36.2s 4.7min 5.1min 0 transport_latency_assumed new_market k 2,763 1,148 169ms 3.6min 11.9min 20.5h 0 transport_latency_assumed price_change c 58,314,389 52,532,939 5ms 18ms 196ms 6.4s 0 transport_latency_assumed price_change h 106,487,665 9,323,667 19ms 63ms 452ms 1.8min 0 transport_latency_assumed price_change i 111,708,119 9,891,583 21ms 36ms 226ms 8.0s 0 transport_latency_assumed price_change k 101,657,988 45,400,952 13ms 26ms 220ms 40.3s 0 transport_latency_assumed tick_size_change c 2,172 1,796 6ms 47ms 497ms 661ms 0 transport_latency_assumed tick_size_change h 4,360 425 19ms 93ms 633ms 1.0s 0 transport_latency_assumed tick_size_change i 4,516 495 21ms 58ms 245ms 969ms 0 transport_latency_assumed tick_size_change k 4,220 1,924 13ms 62ms 314ms 702ms 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/16/2026-09-26T16.parquet sha256sum 2026-09-26T16.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.