Hour audit: 2026-09-26T23
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-26T23 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-26T23:00:00.000064414+00:00 · last event 2026-09-26T23:59:59.999973742+00:00
VOLUME 145,747,608 rows · 1,620,064,031 bytes (1.51 GiB) · 7 products, all holding rows
WITNESSES chik — 4 machines contributed rows
captured i: 130,930,138 · h: 130,868,774 · k: 125,525,328 · c: 97,893,484 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 4,618,150 (3.17%) · h: 10,260,967 (7.04%) · k: 40,791,829 (27.99%) · c: 90,076,662 (61.80%) (rows of the merged file that came from it; these partition it)
5 expected (cghik), 1 contributed nothing: g
INTEGRITY sha256 7911668f49e368ff37d675a151af273af1bf09b3e7cd213e9bc0539976b328d5
the corpus checksum ledger names this file with the same digest
joined 145,752,609 to merged 145,747,608, minus 5,001 (minus 0.0034%)
boundary drops 5,001 · 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-27T03:46:10Z 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 15,495,729 176,276,277 0-59 3d508ba33c9c371dba68d7539327013c77873662335684b67f164fb2cc308839 book 3,695,365 117,144,592 60-74 666a67afbe79bf3688bea58592208f5446614c3f6230a7ffc502553ade2fb06f last_trade_price 56,131 3,199,541 75-75 5a275fb4cc4d90a78f784c639399b0b9af82c50188966db3c90b46c606952868 market_resolved 50,248 3,075,700 76-76 fb57057fe27ac46a5911af3834d6dca7e312ae3eccd5cb9ab959eb67697dbb41 new_market 45,325 2,383,473 77-77 dbae0cb105f2b1e60b11382387bc50be1daa54f92caf2a21547b86bc5d23c607 price_change 126,397,738 1,316,069,218 78-560 6ce1b7321e5db7f6b15eb52c0408dbee0194ad0d4d8da152e5c8da386cc47f5e tick_size_change 7,072 258,466 561-561 379a52874a457948cf57230b6042030cdb1d7a025882344afdd601cf2f4cfd7e EVENT MIX count share price_change 126,397,738 86.72% best_bid_ask 15,495,729 10.63% book 3,695,365 2.54% last_trade_price 56,131 0.04% market_resolved 50,248 0.03% new_market 45,325 0.03% tick_size_change 7,072 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 15,495,779 15,495,729 50 59,967 PARTIAL book 3,700,030 3,695,365 4,665 213,196 PARTIAL last_trade_price 56,131 56,131 0 3,385 PARTIAL market_resolved 50,272 50,248 24 17,816 PARTIAL new_market 45,337 45,325 12 14,175 PARTIAL price_change 126,397,988 126,397,738 250 98,357 PARTIAL tick_size_change 7,072 7,072 0 1,768 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,287,677 9,462,853 5ms 14ms 99ms 8.2s 0 transport_latency_assumed best_bid_ask h 14,247,346 1,100,344 18ms 56ms 255ms 55.0s 0 transport_latency_assumed best_bid_ask i 14,176,891 487,999 21ms 33ms 139ms 3.9s 0 transport_latency_assumed best_bid_ask k 13,550,042 4,444,533 12ms 22ms 126ms 25.4s 0 transport_latency_assumed book c 3,176,699 2,968,393 1.5h 5.8d 45.4d 120.1d 0 book_staleness book h 938,435 194,380 47.5min 5.1d 42.4d 120.0d 0 book_staleness book i 945,833 147,577 44.5min 5.1d 42.4d 120.0d 0 book_staleness book k 1,360,318 385,015 1.1h 5.1d 44.9d 120.0d 0 book_staleness last_trade_price c 36,259 32,786 6ms 24ms 231ms 2.0s 0 transport_latency_assumed last_trade_price h 51,196 4,230 20ms 71ms 402ms 46.9s 0 transport_latency_assumed last_trade_price i 52,041 2,444 22ms 66ms 446ms 2.0s 0 transport_latency_assumed last_trade_price k 49,122 16,671 13ms 39ms 269ms 10.7s 0 transport_latency_assumed market_resolved c 48,383 46,472 2.2h 3.8h 4.7h 4.9h 0 transport_latency_assumed market_resolved h 4,472 305 25ms 9.4min 13.4min 13.7min 0 transport_latency_assumed market_resolved i 4,739 808 23ms 8.1min 12.6min 13.0min 0 transport_latency_assumed market_resolved k 5,277 2,663 16ms 10.5min 15.6min 16.1min 0 transport_latency_assumed new_market c 44,906 43,973 2.3h 4.0h 4.6h 5.1h 0 transport_latency_assumed new_market h 1,394 354 212ms 52.5s 5.6min 7.8min 0 transport_latency_assumed new_market i 1,533 434 151ms 4.9min 8.3min 8.6min 0 transport_latency_assumed new_market k 1,672 564 205ms 5.7min 11.2min 11.6min 0 transport_latency_assumed price_change c 84,294,800 77,517,689 5ms 15ms 103ms 8.3s 0 transport_latency_assumed price_change h 115,619,243 8,961,024 19ms 58ms 278ms 55.2s 0 transport_latency_assumed price_change i 115,742,365 3,978,703 21ms 35ms 169ms 4.0s 0 transport_latency_assumed price_change k 110,552,253 35,940,322 13ms 23ms 136ms 27.8s 0 transport_latency_assumed tick_size_change c 4,760 4,496 5ms 9ms 48ms 148ms 0 transport_latency_assumed tick_size_change h 6,688 330 18ms 50ms 96ms 459ms 0 transport_latency_assumed tick_size_change i 6,736 185 21ms 26ms 75ms 178ms 0 transport_latency_assumed tick_size_change k 6,644 2,061 12ms 22ms 66ms 141ms 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/23/2026-09-26T23.parquet sha256sum 2026-09-26T23.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.