Hour audit: 2026-09-26T08
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-26T08 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-26T08:00:00.000237759+00:00 · last event 2026-09-26T08:59:59.999935212+00:00
VOLUME 98,040,663 rows · 966,115,256 bytes (921.36 MiB) · 7 products, all holding rows
WITNESSES hik — 3 machines contributed rows
captured h: 98,004,376 · i: 98,002,314 · k: 98,001,180 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 2,986,977 (3.05%) · i: 2,828,141 (2.88%) · k: 92,225,545 (94.07%) (rows of the merged file that came from it; these partition it)
5 expected (cghik), 2 contributed nothing: c, g
INTEGRITY sha256 8612d6ff7d52db0c85af03cd5985f34caa18f9ad4a1c5a5de3a09d668c340fab
the corpus checksum ledger names this file with the same digest
joined 98,040,831 to merged 98,040,663, minus 168 (minus 0.0002%)
boundary drops 168 · 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-26T09:50:13Z 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,173,792 118,400,046 0-42 b8c09c5fb86b44f995ba5cdac4910441675afe866e71ffb5468da3de2625c464 book 93,614 9,321,968 43-43 47467f7021474c715eb5d91d34a9ae9c44156cf9ec8c392a32d26a6b56dda268 last_trade_price 42,802 2,492,735 44-44 e74aa2871de39457ffdcce34aa5e2074ee16622aade4e9ea5126b7198f6557e0 market_resolved 801 130,356 45-45 75573e928207ffa0af816e1d6ff1f67ac8b16bd0099595a81b2d25d809d9bf3e new_market 924 106,696 46-46 76081d67722d911250685e7fc6df08868f72b5facbedf2264f3ac85ee768d1d7 price_change 86,725,974 834,447,458 47-377 6912f91445b4f1490ba52205606200f4b41485a5287f743085878b81f5256fb5 tick_size_change 2,756 100,350 378-378 19d4fd2063490789326e639b9f0565b613ec28bf67d2553eeb4df60e674b66a4 EVENT MIX count share price_change 86,725,974 88.46% best_bid_ask 11,173,792 11.40% book 93,614 0.10% last_trade_price 42,802 0.04% tick_size_change 2,756 <0.01% new_market 924 <0.01% market_resolved 801 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,173,816 11,173,792 24 45,202 PARTIAL book 93,616 93,614 2 6,778 PARTIAL last_trade_price 42,802 42,802 0 3,219 PARTIAL market_resolved 801 801 0 801 PARTIAL new_market 924 924 0 720 PARTIAL price_change 86,726,116 86,725,974 142 86,848 PARTIAL tick_size_change 2,756 2,756 0 689 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 11,173,192 293,117 18ms 22ms 101ms 20.4s 0 transport_latency_assumed best_bid_ask i 11,173,101 287,698 19ms 22ms 68ms 4.2s 0 transport_latency_assumed best_bid_ask k 11,173,308 10,592,977 12ms 15ms 68ms 7.5s 0 transport_latency_assumed book h 87,774 6,887 22ms 48ms 6.9s 100.9d 0 book_staleness book i 87,914 8,664 21ms 57ms 26.0s 54.9d 0 book_staleness book k 91,442 78,063 15ms 72ms 1.5d 100.9d 0 book_staleness last_trade_price h 42,703 2,478 19ms 36ms 262ms 7.7s 0 transport_latency_assumed last_trade_price i 42,738 1,537 21ms 39ms 319ms 2.0s 0 transport_latency_assumed last_trade_price k 42,691 38,787 13ms 23ms 225ms 1.3s 0 transport_latency_assumed market_resolved h 801 24 19ms 15.1s 43.3s 49.5s 0 transport_latency_assumed market_resolved i 801 137 21ms 14.4s 42.4s 48.7s 0 transport_latency_assumed market_resolved k 801 640 13ms 19.5s 47.8s 53.9s 0 transport_latency_assumed new_market h 720 312 107ms 27.4s 47.7s 1.9min 0 transport_latency_assumed new_market i 720 320 102ms 25.1s 57.3s 1.5min 0 transport_latency_assumed new_market k 720 292 90ms 27.0s 1.1min 1.6min 0 transport_latency_assumed price_change h 86,696,430 2,684,096 18ms 23ms 142ms 23.6s 0 transport_latency_assumed price_change i 86,694,284 2,529,736 19ms 23ms 113ms 4.2s 0 transport_latency_assumed price_change k 86,689,462 81,512,142 12ms 16ms 87ms 8.3s 0 transport_latency_assumed tick_size_change h 2,756 63 18ms 21ms 37ms 60ms 0 transport_latency_assumed tick_size_change i 2,756 49 19ms 22ms 46ms 68ms 0 transport_latency_assumed tick_size_change k 2,756 2,644 12ms 15ms 30ms 90ms 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/08/2026-09-26T08.parquet sha256sum 2026-09-26T08.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.