Hour audit: 2026-09-25T17
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-25T17 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-25T17:00:00.000008194+00:00 · last event 2026-09-25T17:59:59.999978521+00:00
VOLUME 121,460,839 rows · 1,289,704,724 bytes (1.20 GiB) · 7 products, all holding rows
WITNESSES hik — 3 machines contributed rows
captured i: 121,323,093 · k: 121,097,018 · h: 121,065,298 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 5,968,001 (4.91%) · k: 106,308,596 (87.52%) · h: 9,184,242 (7.56%) (rows of the merged file that came from it; these partition it)
5 expected (cghik), 2 contributed nothing: c, g
INTEGRITY sha256 c0cf1572d351d5edeec6fa9734290048fdea3bbe6392129d9e026d6d8a509b30
the corpus checksum ledger names this file with the same digest
joined 121,461,113 to merged 121,460,839, minus 274 (minus 0.0002%)
boundary drops 274 · 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-25T23:17:59Z 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 10,740,922 120,906,647 0-40 1e8d6035711e47a50da16b827825d1c072dd37f451d47306445b60ca82397974 book 540,902 50,439,812 41-43 7d0a0acc3ba3570d116e8e050eb69b3021723be7e9b144d4201f426c077a8068 last_trade_price 58,137 3,313,420 44-44 14f62c7b6ca71c7f75c6048baa4946af8ed5b2cdf477b98fd4b5bc1d99b507be market_resolved 558 91,151 45-45 1ffa230001a4f0140db2865662bd7e2e819a0039fbf50cfe04505b28909da407 new_market 2,034 218,207 46-46 658f74a8b622430a1be535a9b7b74b3de1ac858f444c2dac187ff80672e4ab21 price_change 110,115,150 1,113,240,618 47-467 448f0d3367ed90f8874485aa4fa5ec9aacf9a8a0549fa5720024fbf01382e336 tick_size_change 3,136 114,240 468-468 2c48664f2eaff3664c9763c7a53f5004b75cfd145fdc029c92c3e3d0460aaec4 EVENT MIX count share price_change 110,115,150 90.66% best_bid_ask 10,740,922 8.84% book 540,902 0.45% last_trade_price 58,137 0.05% tick_size_change 3,136 <0.01% new_market 2,034 <0.01% market_resolved 558 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,740,946 10,740,922 24 49,937 PARTIAL book 540,904 540,902 2 165,502 PARTIAL last_trade_price 58,137 58,137 0 3,585 PARTIAL market_resolved 558 558 0 556 PARTIAL new_market 2,034 2,034 0 1,481 PARTIAL price_change 110,115,398 110,115,150 248 86,427 PARTIAL tick_size_change 3,136 3,136 0 784 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,739,874 747,259 19ms 36ms 233ms 45.4s 0 transport_latency_assumed best_bid_ask i 10,737,929 464,947 21ms 31ms 134ms 2.9s 0 transport_latency_assumed best_bid_ask k 10,739,834 9,528,716 13ms 24ms 178ms 10.4s 0 transport_latency_assumed book h 177,763 55,891 43ms 7.1h 23.0d 118.8d 0 book_staleness book i 460,071 317,517 7.8min 3.9d 34.2d 118.8d 0 book_staleness book k 210,764 167,494 57ms 19.9h 30.1d 118.8d 0 book_staleness last_trade_price h 58,074 5,216 21ms 84ms 525ms 24.0s 0 transport_latency_assumed last_trade_price i 57,975 3,202 24ms 101ms 609ms 2.0s 0 transport_latency_assumed last_trade_price k 58,007 49,719 14ms 50ms 302ms 5.3s 0 transport_latency_assumed market_resolved h 556 48 20ms 74ms 32.1s 56.9s 0 transport_latency_assumed market_resolved i 556 32 22ms 83ms 31.5s 56.9s 0 transport_latency_assumed market_resolved k 556 478 14ms 47ms 33.0s 33.1s 0 transport_latency_assumed new_market h 1,481 556 117ms 18.5s 3.1min 4.0d 0 transport_latency_assumed new_market i 1,480 715 84ms 20.2s 3.0min 4.0min 0 transport_latency_assumed new_market k 1,481 763 93ms 33.8s 2.9min 3.6min 0 transport_latency_assumed price_change h 110,084,414 8,375,054 19ms 42ms 281ms 45.5s 0 transport_latency_assumed price_change i 110,061,950 5,181,484 21ms 39ms 224ms 3.8s 0 transport_latency_assumed price_change k 110,083,240 96,558,612 13ms 28ms 190ms 10.4s 0 transport_latency_assumed tick_size_change h 3,136 218 19ms 29ms 278ms 1.3s 0 transport_latency_assumed tick_size_change i 3,132 104 21ms 31ms 184ms 383ms 0 transport_latency_assumed tick_size_change k 3,136 2,814 13ms 20ms 225ms 720ms 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-25/17/2026-09-25T17.parquet sha256sum 2026-09-25T17.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.