Hour audit: 2026-09-26T21
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-26T21 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-26T21:00:00.000001483+00:00 · last event 2026-09-26T21:59:59.999982667+00:00
VOLUME 140,652,387 rows · 1,573,721,664 bytes (1.47 GiB) · 7 products, all holding rows
WITNESSES chik — 4 machines contributed rows
captured i: 130,265,692 · h: 129,493,065 · k: 119,364,638 · c: 74,841,727 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 7,005,856 (4.98%) · h: 8,692,440 (6.18%) · k: 55,783,851 (39.66%) · c: 69,170,240 (49.18%) (rows of the merged file that came from it; these partition it)
5 expected (cghik), 1 contributed nothing: g
INTEGRITY sha256 77de4b9975427cc79164f7916cb5ff8b18b5339c4c9e256a0df04708589ca95a
the corpus checksum ledger names this file with the same digest
joined 140,660,879 to merged 140,652,387, minus 8,492 (minus 0.0060%)
boundary drops 8,492 · 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-27T02:47:45Z 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 13,594,442 155,393,994 0-51 7c84024fef5162fbb975edc676ef10135f8c71d90ae5227bc08c5b8e91c973f6 book 5,122,292 131,604,353 52-71 79ff1da4122292be266a1fce94d0283a5fee1b19ffc04daf4d9b976a70b50e21 last_trade_price 47,193 2,750,757 72-72 394330793b24950936e60070c256d0cbe466a784b6f5eafee8c7ad29754bbe11 market_resolved 82,556 1,994,612 73-73 fe5bd1f12b0c4036329608d383b43791d74e6273331dfce0dbf04b23acefa543 new_market 94,328 2,071,833 74-74 13b75b73fc245354c5a5945900f5e5a6b7051dc7f61fb071637a3d5cf1ae717d price_change 121,704,416 1,278,051,523 75-539 87580e2983139b2f24b31277e46fbd1040636c2f4b93544b8d1c175354395078 tick_size_change 7,160 259,952 540-540 bdad0b0f5d56809e7c0bcef4669459a0db81adea3032a41c0282ab82cab30f31 EVENT MIX count share price_change 121,704,416 86.53% best_bid_ask 13,594,442 9.67% book 5,122,292 3.64% new_market 94,328 0.07% market_resolved 82,556 0.06% last_trade_price 47,193 0.03% tick_size_change 7,160 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,594,484 13,594,442 42 59,749 PARTIAL book 5,130,194 5,122,292 7,902 215,405 PARTIAL last_trade_price 47,193 47,193 0 3,487 PARTIAL market_resolved 82,558 82,556 2 10,306 PARTIAL new_market 94,452 94,328 124 10,843 PARTIAL price_change 121,704,838 121,704,416 422 98,009 PARTIAL tick_size_change 7,160 7,160 0 1,790 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 7,020,296 6,470,347 5ms 14ms 132ms 4.8s 0 transport_latency_assumed best_bid_ask h 12,948,937 861,292 19ms 57ms 323ms 1.2min 0 transport_latency_assumed best_bid_ask i 13,016,281 686,982 21ms 30ms 157ms 2.9s 0 transport_latency_assumed best_bid_ask k 11,818,090 5,575,821 13ms 21ms 152ms 10.1s 0 transport_latency_assumed book c 4,666,736 4,569,372 1.4h 5.4d 45.3d 120.0d 0 book_staleness book h 520,594 129,379 26.8min 5.0d 35.3d 120.0d 0 book_staleness book i 520,062 103,921 23.2min 5.0d 35.3d 120.0d 0 book_staleness book k 1,356,834 319,620 1.1h 5.0d 44.8d 120.0d 0 book_staleness last_trade_price c 21,260 19,125 6ms 24ms 217ms 2.0s 0 transport_latency_assumed last_trade_price h 44,414 4,429 21ms 71ms 495ms 1.1min 0 transport_latency_assumed last_trade_price i 44,443 3,507 22ms 62ms 513ms 2.0s 0 transport_latency_assumed last_trade_price k 39,493 20,132 14ms 36ms 288ms 2.0s 0 transport_latency_assumed market_resolved c 81,290 80,442 1.2h 2.3h 3.1h 3.4h 0 transport_latency_assumed market_resolved h 2,491 200 22ms 50.1s 7.7min 7.9min 0 transport_latency_assumed market_resolved i 2,447 388 22ms 24.1s 3.4min 5.1min 0 transport_latency_assumed market_resolved k 3,183 1,526 15ms 9.2min 14.2min 16.1min 0 transport_latency_assumed new_market c 94,052 92,317 1.0h 2.4h 3.0h 3.5h 0 transport_latency_assumed new_market h 2,618 582 245ms 6.2min 6.6min 7.7min 0 transport_latency_assumed new_market i 2,112 568 128ms 34.8s 1.5min 2.7min 0 transport_latency_assumed new_market k 2,536 861 163ms 2.4min 10.9min 12.2min 0 transport_latency_assumed price_change c 62,954,493 57,935,205 5ms 15ms 138ms 5.2s 0 transport_latency_assumed price_change h 115,966,967 7,696,311 19ms 59ms 350ms 1.5min 0 transport_latency_assumed price_change i 116,673,567 6,210,322 21ms 33ms 192ms 3.0s 0 transport_latency_assumed price_change k 106,137,954 49,862,578 13ms 23ms 161ms 10.1s 0 transport_latency_assumed tick_size_change c 3,600 3,432 5ms 9ms 31ms 53ms 0 transport_latency_assumed tick_size_change h 7,044 247 19ms 53ms 120ms 4.4s 0 transport_latency_assumed tick_size_change i 6,780 168 21ms 25ms 69ms 227ms 0 transport_latency_assumed tick_size_change k 6,548 3,313 13ms 17ms 43ms 145ms 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/21/2026-09-26T21.parquet sha256sum 2026-09-26T21.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.