Hour audit: 2026-09-25T19
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-25T19 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-25T19:00:00.000079995+00:00 · last event 2026-09-25T19:59:59.999970792+00:00
VOLUME 116,977,922 rows · 1,250,268,437 bytes (1.16 GiB) · 7 products, all holding rows
WITNESSES hik — 3 machines contributed rows
captured h: 116,283,682 · i: 111,892,378 · k: 111,659,610 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 12,955,034 (11.07%) · i: 6,354,538 (5.43%) · k: 97,668,350 (83.49%) (rows of the merged file that came from it; these partition it)
5 expected (cghik), 2 contributed nothing: c, g
INTEGRITY sha256 957068d3317dd192a5716c6e83457d619c39bc1460722ed9dde59292ce628c77
the corpus checksum ledger names this file with the same digest
joined 116,978,297 to merged 116,977,922, minus 375 (minus 0.0003%)
boundary drops 375 · 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-26T00:00:10Z 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 12,002,005 134,003,351 0-45 c2f62747d031d42a1469c14b4d676ad930660b04f8cd765f05aab27273484f11 book 717,244 60,872,008 46-48 a16f4c965655d446cb587e815638517e520f2a433691377023d0e4ebbb9462d8 last_trade_price 58,241 3,405,436 49-49 022ce79e7e0d139b91f38465a56995a23fb67ace41cb16b9664fcded91faa245 market_resolved 744 107,375 50-50 f5906742acb0b988abcece463ef85f959eb3ccf48e954927084d6b5b1fe2fcd7 new_market 4,710 505,806 51-51 33636d9645e4a779504dfe52e561d5f1920fe006ac55892e058638749c90fde6 price_change 104,191,494 1,049,918,637 52-449 033f59a4ef34aead83b61dac5fd5b0d5e6a965295f673c28e556ddd5de3410f2 tick_size_change 3,484 127,918 450-450 ae06fc7ff6f90875e0035944ec1185be2f33b81a9b35d5478b88faa30baf4cad EVENT MIX count share price_change 104,191,494 89.07% best_bid_ask 12,002,005 10.26% book 717,244 0.61% last_trade_price 58,241 0.05% new_market 4,710 <0.01% tick_size_change 3,484 <0.01% market_resolved 744 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,002,048 12,002,005 43 53,043 PARTIAL book 717,254 717,244 10 214,526 PARTIAL last_trade_price 58,241 58,241 0 4,255 PARTIAL market_resolved 744 744 0 670 PARTIAL new_market 4,710 4,710 0 3,361 PARTIAL price_change 104,191,816 104,191,494 322 87,119 PARTIAL tick_size_change 3,484 3,484 0 871 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 11,998,689 1,313,173 19ms 52ms 1.3s 1.2min 0 transport_latency_assumed best_bid_ask i 11,461,831 602,177 20ms 34ms 229ms 13.9s 0 transport_latency_assumed best_bid_ask k 11,437,546 10,086,655 13ms 27ms 284ms 1.1min 0 transport_latency_assumed book h 144,268 26,873 27ms 12.5min 9.8d 118.9d 0 book_staleness book i 630,547 140,442 35.7min 3.9d 34.2d 118.9d 0 book_staleness book k 576,608 549,929 26.5min 3.9d 34.2d 118.9d 0 book_staleness last_trade_price h 57,940 7,354 20ms 125ms 2.3s 58.0s 0 transport_latency_assumed last_trade_price i 55,528 3,217 22ms 128ms 1.1s 13.9s 0 transport_latency_assumed last_trade_price k 55,487 47,670 14ms 59ms 417ms 22.2s 0 transport_latency_assumed market_resolved h 670 103 20ms 611ms 56.9s 1.0min 0 transport_latency_assumed market_resolved i 670 77 21ms 94ms 4.3min 5.3min 0 transport_latency_assumed market_resolved k 670 564 14ms 21.6s 3.9min 5.0min 0 transport_latency_assumed new_market h 3,361 1,172 306ms 10.7min 17.5min 17.5min 0 transport_latency_assumed new_market i 3,428 1,188 232ms 10.6min 17.4min 17.5min 0 transport_latency_assumed new_market k 3,361 2,350 194ms 14.9min 39.6min 39.7min 0 transport_latency_assumed price_change h 104,075,270 11,605,926 19ms 63ms 1.4s 1.2min 0 transport_latency_assumed price_change i 99,737,042 5,607,234 21ms 45ms 379ms 14.0s 0 transport_latency_assumed price_change k 99,582,590 86,978,334 13ms 34ms 326ms 1.1min 0 transport_latency_assumed tick_size_change h 3,484 433 19ms 73ms 644ms 9.0s 0 transport_latency_assumed tick_size_change i 3,332 203 21ms 52ms 340ms 421ms 0 transport_latency_assumed tick_size_change k 3,348 2,848 13ms 38ms 394ms 2.3s 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/19/2026-09-25T19.parquet sha256sum 2026-09-25T19.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.