Hour audit: 2026-09-26T12
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-26T12 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-26T12:00:00.000032937+00:00 · last event 2026-09-26T12:59:59.999893417+00:00
VOLUME 104,251,692 rows · 1,063,563,563 bytes (1014.29 MiB) · 7 products, all holding rows
WITNESSES chik — 4 machines contributed rows
captured i: 104,121,562 · h: 102,287,456 · k: 101,817,078 · c: 369,997 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 3,197,595 (3.07%) · h: 5,029,088 (4.82%) · k: 95,658,879 (91.76%) · c: 366,130 (0.35%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 104,251,692 rows exactly, so those pairs supplied none
5 expected (cghik), 1 contributed nothing: g
INTEGRITY sha256 5203397086c7c70421894b9fced61a90701f84183d41d3f0206e9cca2f67472d
the corpus checksum ledger names this file with the same digest
joined 104,253,206 to merged 104,251,692, minus 1,514 (minus 0.0015%)
boundary drops 1,514 · 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-26T23:07:50Z 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,779,726 128,068,721 0-44 27368de3993569eda4ec1ecd25ac17a056e8aa6de5c655ffc9db03adbf793601 book 204,133 19,627,932 45-45 ddcb16075d6400f02d8067eb8cbe709d309f6cb72d9092814f675760fb42d85e last_trade_price 51,724 2,964,825 46-46 458db201207a9a686a14fb75f9a935b9ecd065a98a0f1416e724bba2b851ebb9 market_resolved 1,667 251,430 47-47 a727aefd7f7318a47b22fc1035b116095a9d1d5ee48b143263c6ed94da521f75 new_market 977 111,527 48-48 62ee84b077c98b94f7d2a40cd2178f5a687edfa19ed1231a0df0db2df7e2d29e price_change 92,211,241 911,271,804 49-400 037c7ddbaef30c9155e1aec5c723d94aa0eb236c2ac8824167d7d5caed13e026 tick_size_change 2,224 82,720 401-401 dd11b84c697313f0432edf3b8f9d208b2d7de826d57c2381ad6b4265c85114be EVENT MIX count share price_change 92,211,241 88.45% best_bid_ask 11,779,726 11.30% book 204,133 0.20% last_trade_price 51,724 0.05% tick_size_change 2,224 <0.01% market_resolved 1,667 <0.01% new_market 977 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,779,956 11,779,726 230 52,297 PARTIAL book 204,133 204,133 0 51,441 PARTIAL last_trade_price 51,724 51,724 0 3,398 PARTIAL market_resolved 1,667 1,667 0 1,585 PARTIAL new_market 977 977 0 761 PARTIAL price_change 92,212,525 92,211,241 1,284 91,811 PARTIAL tick_size_change 2,224 2,224 0 556 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 29,722 29,380 4ms 6ms 14ms 337ms 0 transport_latency_assumed best_bid_ask h 11,509,653 503,282 18ms 25ms 142ms 50.5s 0 transport_latency_assumed best_bid_ask i 11,778,858 315,586 20ms 24ms 76ms 4.0s 0 transport_latency_assumed best_bid_ask k 11,542,509 10,931,478 12ms 15ms 81ms 19.9s 0 transport_latency_assumed book c 96,622 95,970 3.6h 1.6d 1.7d 2.8d 0 book_staleness book h 105,286 9,442 22ms 50ms 3.5min 101.0d 0 book_staleness book i 105,347 10,429 22ms 51ms 2.1s 101.1d 0 book_staleness book k 102,677 88,292 15ms 30ms 52.4s 100.9d 0 book_staleness last_trade_price c 204 204 5ms 6ms 18ms 77ms 0 transport_latency_assumed last_trade_price h 51,233 3,697 19ms 39ms 267ms 15.9s 0 transport_latency_assumed last_trade_price i 51,624 1,931 21ms 36ms 243ms 3.4s 0 transport_latency_assumed last_trade_price k 50,050 45,892 13ms 21ms 214ms 6.8s 0 transport_latency_assumed market_resolved c 10 not meas. 22.0s 22.1s 22.1s 22.1s 0 transport_latency_assumed market_resolved h 1,568 137 19ms 35.4s 53.2s 2.5min 0 transport_latency_assumed market_resolved i 1,585 274 21ms 20.0s 44.7s 46.3s 0 transport_latency_assumed market_resolved k 1,572 1,256 13ms 21.8s 49.6s 2.2min 0 transport_latency_assumed new_market c 11 10 1.5min 1.6min 1.6min 1.6min 0 transport_latency_assumed new_market h 761 248 137ms 13.7s 37.5s 1.2min 0 transport_latency_assumed new_market i 761 488 68ms 16.2s 34.4s 1.5min 0 transport_latency_assumed new_market k 761 231 164ms 15.2s 32.3s 1.7min 0 transport_latency_assumed price_change c 243,388 240,526 4ms 6ms 15ms 337ms 0 transport_latency_assumed price_change h 90,616,771 4,512,158 19ms 28ms 198ms 50.5s 0 transport_latency_assumed price_change i 92,181,163 2,868,770 20ms 25ms 124ms 4.0s 0 transport_latency_assumed price_change k 90,117,337 84,589,787 12ms 16ms 110ms 19.9s 0 transport_latency_assumed tick_size_change c 40 40 4ms 6ms 6ms 6ms 0 transport_latency_assumed tick_size_change h 2,184 124 19ms 56ms 337ms 743ms 0 transport_latency_assumed tick_size_change i 2,224 117 20ms 31ms 110ms 328ms 0 transport_latency_assumed tick_size_change k 2,172 1,943 12ms 21ms 163ms 535ms 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/12/2026-09-26T12.parquet sha256sum 2026-09-26T12.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.