Hour audit: 2026-09-26T15
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-26T15 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-26T15:00:00.000439502+00:00 · last event 2026-09-26T15:59:59.999906706+00:00
VOLUME 109,048,138 rows · 1,191,038,632 bytes (1.11 GiB) · 7 products, all holding rows
WITNESSES chik — 4 machines contributed rows
captured i: 108,032,663 · k: 107,059,097 · h: 102,602,891 · c: 98,922,957 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 2,148,352 (1.97%) · k: 14,282,179 (13.10%) · h: 1,476,095 (1.35%) · c: 91,141,512 (83.58%) (rows of the merged file that came from it; these partition it)
5 expected (cghik), 1 contributed nothing: g
INTEGRITY sha256 5c5c4bb0c721956283590e65395b5e6e6a44f70fb4b7d0a1230f3edc43e26778
the corpus checksum ledger names this file with the same digest
joined 109,048,548 to merged 109,048,138, minus 410 (minus 0.0004%)
boundary drops 410 · 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:14:00Z 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 11,776,528 133,853,909 0-44 cd215dd9b73536bee47a42cc9377b49d39688014f848311cc144aaf746f43011 book 1,111,536 72,439,627 45-49 d2e540ba4f38598b19a793e3576edd1e9b421209d66985847d94485bb71adf8e last_trade_price 62,632 3,636,467 50-50 e37e74b3bc1f661dc789740c61074bb966a5f6962ab8dfcaf0103c5e8a25507b market_resolved 850 120,323 51-51 4f5ecfe17fae3035a275808060dd06003f0fbf46e882a7f2801f53b0c78b37ad new_market 2,360 263,084 52-52 89cc3ff3995509a6b4fcfb5092cc75a153a9ab2cd6e3f1e798732a6d2cd82388 price_change 96,086,404 979,200,931 53-419 684699bfe19b95281ca9869b6dabda658af39423d3c6f6aaaa367d445dfcdf71 tick_size_change 7,828 283,412 420-420 16c0c206ede410fb5e014fb3002fd366ccfb4bb529763fa3853d21ba3234fca8 EVENT MIX count share price_change 96,086,404 88.11% best_bid_ask 11,776,528 10.80% book 1,111,536 1.02% last_trade_price 62,632 0.06% tick_size_change 7,828 <0.01% new_market 2,360 <0.01% market_resolved 850 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,776,581 11,776,528 53 59,677 PARTIAL book 1,111,540 1,111,536 4 214,142 PARTIAL last_trade_price 62,633 62,632 1 4,515 PARTIAL market_resolved 850 850 0 739 PARTIAL new_market 2,360 2,360 0 1,757 PARTIAL price_change 96,086,756 96,086,404 352 106,613 PARTIAL tick_size_change 7,828 7,828 0 1,957 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,682,663 9,869,627 5ms 12ms 158ms 8.1s 0 transport_latency_assumed best_bid_ask h 11,146,235 138,043 19ms 56ms 337ms 39.5s 0 transport_latency_assumed best_bid_ask i 11,775,292 225,598 20ms 27ms 113ms 4.2s 0 transport_latency_assumed best_bid_ask k 11,641,864 1,543,260 12ms 19ms 139ms 8.7s 0 transport_latency_assumed book c 964,482 913,847 38.0min 4.8d 42.0d 119.7d 0 book_staleness book h 556,661 167,344 13.7min 4.8d 35.1d 119.7d 0 book_staleness book i 129,416 6,583 22ms 67ms 3.4s 101.1d 0 book_staleness book k 134,922 23,762 16ms 122ms 3.8d 101.2d 0 book_staleness last_trade_price c 54,559 49,104 6ms 21ms 227ms 1.1s 0 transport_latency_assumed last_trade_price h 59,293 1,018 21ms 75ms 762ms 11.9s 0 transport_latency_assumed last_trade_price i 62,479 1,811 22ms 47ms 397ms 3.9s 0 transport_latency_assumed last_trade_price k 62,243 10,699 13ms 30ms 230ms 6.5s 0 transport_latency_assumed market_resolved c 732 690 5ms 13ms 4.3min 5.5min 0 transport_latency_assumed market_resolved h 751 55 21ms 108ms 6.6min 10.9min 0 transport_latency_assumed market_resolved i 739 49 21ms 84ms 56.3s 56.4s 0 transport_latency_assumed market_resolved k 733 56 13ms 37ms 120ms 1.5min 0 transport_latency_assumed new_market c 1,757 836 85ms 21.7s 5.9min 6.1min 0 transport_latency_assumed new_market h 1,795 392 149ms 33.3s 2.6min 4.1min 0 transport_latency_assumed new_market i 1,757 565 102ms 28.4s 2.6min 4.6min 0 transport_latency_assumed new_market k 1,757 567 118ms 20.2s 2.8min 4.6min 0 transport_latency_assumed price_change c 87,211,348 80,300,520 5ms 13ms 164ms 8.1s 0 transport_latency_assumed price_change h 90,830,608 1,169,156 19ms 58ms 358ms 39.8s 0 transport_latency_assumed price_change i 96,055,152 1,913,710 20ms 28ms 142ms 4.3s 0 transport_latency_assumed price_change k 95,209,782 12,703,018 13ms 20ms 149ms 9.4s 0 transport_latency_assumed tick_size_change c 7,416 6,888 5ms 11ms 88ms 326ms 0 transport_latency_assumed tick_size_change h 7,548 87 19ms 44ms 176ms 6.3s 0 transport_latency_assumed tick_size_change i 7,828 36 20ms 26ms 101ms 320ms 0 transport_latency_assumed tick_size_change k 7,796 817 12ms 18ms 79ms 511ms 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/15/2026-09-26T15.parquet sha256sum 2026-09-26T15.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.