Hour audit: 2026-09-26T20
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-26T20 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-26T20:00:00.003187094+00:00 · last event 2026-09-26T20:59:59.999995857+00:00
VOLUME 134,691,723 rows · 1,527,445,289 bytes (1.42 GiB) · 7 products, all holding rows
WITNESSES chik — 4 machines contributed rows
captured i: 121,029,406 · h: 120,711,584 · k: 99,421,605 · c: 67,590,643 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 14,695,802 (10.91%) · h: 15,599,195 (11.58%) · k: 44,154,734 (32.78%) · c: 60,241,992 (44.73%) (rows of the merged file that came from it; these partition it)
5 expected (cghik), 1 contributed nothing: g
INTEGRITY sha256 4bc94952d787e6a3a3e875deb8258d5d34c1d10c4a264880d91e05eb73eef943
the corpus checksum ledger names this file with the same digest
joined 134,723,453 to merged 134,691,723, minus 31,730 (minus 0.0236%)
boundary drops 31,730 · 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-27T02:19:05Z 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,024,235 152,267,805 0-49 7b4fbcfde546a33b67bf2ababea8a3b33c588d1c76c19bf15463bf5bf26e40ba book 5,743,742 147,343,090 50-71 6127c67ff8af7cc29946f55d45eb6a166e50b804e88ab719926132e02dfec721 last_trade_price 56,164 3,277,656 72-72 4347810b83791f5be18e212f4ca230056c81b842ed5692ca2250a0b64032f503 market_resolved 53,230 1,556,892 73-73 6c86426680c082732df8f5562ff5c33156596b735640906fc535fff698d71cbe new_market 59,776 1,728,332 74-74 5e7f36b763a393f40df432973c031502f4779dacc93ec58a8e18b32848a8ac8e price_change 115,746,024 1,219,428,884 75-516 914f5b15fb1d5837113354de3eed8d763ace8e5ac4fbe6b8581f1dbaa31fcd4e tick_size_change 8,552 315,124 517-517 13ece141e9d8c889f7cf6f5c5b2755ec50b666dba617c2bfe807975af811dd01 EVENT MIX count share price_change 115,746,024 85.93% best_bid_ask 13,024,235 9.67% book 5,743,742 4.26% new_market 59,776 0.04% last_trade_price 56,164 0.04% market_resolved 53,230 0.04% tick_size_change 8,552 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,026,313 13,024,235 2,078 67,844 PARTIAL book 5,754,313 5,743,742 10,571 217,448 PARTIAL last_trade_price 56,174 56,164 10 3,774 PARTIAL market_resolved 53,278 53,230 48 7,921 PARTIAL new_market 59,917 59,776 141 8,793 PARTIAL price_change 115,764,906 115,746,024 18,882 104,276 PARTIAL tick_size_change 8,552 8,552 0 2,138 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 6,383,492 5,679,478 6ms 22ms 366ms 16.3s 0 transport_latency_assumed best_bid_ask h 12,082,044 1,519,006 20ms 85ms 3.2s 2.0min 0 transport_latency_assumed best_bid_ask i 12,122,990 1,425,407 21ms 38ms 263ms 11.6s 0 transport_latency_assumed best_bid_ask k 9,831,041 4,400,344 13ms 22ms 224ms 22.7s 0 transport_latency_assumed book c 5,068,115 4,801,604 1.2h 5.6d 45.2d 119.9d 0 book_staleness book h 967,595 161,285 35.6min 5.0d 42.3d 119.9d 0 book_staleness book i 960,159 232,817 32.3min 5.0d 42.3d 119.9d 0 book_staleness book k 2,626,436 548,036 1.1h 5.0d 45.1d 119.9d 0 book_staleness last_trade_price c 25,079 21,680 7ms 43ms 445ms 5.6s 0 transport_latency_assumed last_trade_price h 51,794 7,136 27ms 248ms 10.8s 1.2min 0 transport_latency_assumed last_trade_price i 51,807 7,072 23ms 106ms 3.1s 11.7s 0 transport_latency_assumed last_trade_price k 41,647 20,276 14ms 40ms 335ms 4.4s 0 transport_latency_assumed market_resolved c 50,481 48,078 32.0min 1.3h 2.2h 2.4h 0 transport_latency_assumed market_resolved h 5,017 890 26ms 3.8min 6.6min 7.1min 0 transport_latency_assumed market_resolved i 5,495 1,895 23ms 5.9min 12.5min 13.0min 0 transport_latency_assumed market_resolved k 6,113 2,367 37ms 9.3min 13.3min 14.7min 0 transport_latency_assumed new_market c 58,468 51,687 36.8min 1.5h 2.1h 2.6h 0 transport_latency_assumed new_market h 5,608 1,827 254ms 2.0min 4.7min 38.3min 0 transport_latency_assumed new_market i 6,232 2,094 244ms 4.7min 8.5min 9.0min 0 transport_latency_assumed new_market k 10,204 4,168 3.8min 8.5min 9.5min 9.8min 0 transport_latency_assumed price_change c 56,000,472 49,635,775 6ms 24ms 372ms 16.3s 0 transport_latency_assumed price_change h 107,592,314 13,908,256 20ms 94ms 4.3s 2.0min 0 transport_latency_assumed price_change i 107,875,371 13,025,790 21ms 45ms 323ms 11.7s 0 transport_latency_assumed price_change k 86,899,148 39,176,203 13ms 24ms 231ms 23.1s 0 transport_latency_assumed tick_size_change c 4,536 3,690 6ms 117ms 407ms 2.4s 0 transport_latency_assumed tick_size_change h 7,212 795 19ms 61ms 632ms 43.0s 0 transport_latency_assumed tick_size_change i 7,352 727 21ms 26ms 208ms 759ms 0 transport_latency_assumed tick_size_change k 7,016 3,340 13ms 25ms 375ms 1.5s 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/20/2026-09-26T20.parquet sha256sum 2026-09-26T20.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.