Hour audit: 2026-09-25T05
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.
No findings
Every check that could be evaluated for this hour passed. That is not the same as the hour being perfect: it means the records this archive keeps about it agree with each other and with the corpus ledger.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-25T05 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-25T05:00:00.000005662+00:00 · last event 2026-09-25T05:59:59.999985730+00:00
VOLUME 111,042,958 rows · 1,119,262,869 bytes (1.04 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured c: 111,006,131 · k: 110,998,490 · i: 110,997,481 · h: 110,996,490 · g: 110,970,562 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 103,101,288 (92.85%) · k: 5,162,700 (4.65%) · i: 1,351,773 (1.22%) · h: 1,417,162 (1.28%) · g: 10,035 (0.01%) (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 111,042,958 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 5f66e7188c695c902068208c48061e32c89644e529b0cff44e2f4d8838238f30
the corpus checksum ledger names this file with the same digest
joined 111,044,599 to merged 111,042,958, minus 1,641 (minus 0.0015%)
boundary drops 1,641 · 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-25T08:05:50Z as cghik
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 8/8 pass
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
PASS every expected machine contributed
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,649,668 143,868,714 0-48 54364dac2c9c9c766b75aa4a38589056391b3815054875135dbe1dc11a7fa43c book 112,107 11,571,195 49-49 eddaa5c4e36236cf6d8f0c60b4291ca5dac7230236ca39793bfb43286f64bc78 last_trade_price 42,953 2,505,564 50-50 ba30b1bf1d7c6c89e66463d84f779773e3a58a3d7d677d1fd8bd6c2c114fc65b market_resolved 1,125 174,697 51-51 2cff113caad70e59f1683aeeb7ac347b08eefb5cfd6f88353bbbf52f7b25cd26 new_market 1,657 165,876 52-52 4ca2d546806cada5086cc8feb021153b6180ca02a9e1dc7396bf581310b39a00 price_change 98,232,560 959,605,029 53-427 293da3e75b832448c648b0d375c7e024a75b89bb08ebe074f56089647386b639 tick_size_change 2,888 106,638 428-428 65a14076635af0bb0aa7836194facb9c814a93749efd339c6bad92f549d6349c EVENT MIX count share price_change 98,232,560 88.46% best_bid_ask 12,649,668 11.39% book 112,107 0.10% last_trade_price 42,953 0.04% tick_size_change 2,888 <0.01% new_market 1,657 <0.01% market_resolved 1,125 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,649,858 12,649,668 190 151 FULL book 112,119 112,107 12 10,444 FULL last_trade_price 42,954 42,953 1 0 FULL market_resolved 1,125 1,125 0 0 FULL new_market 1,657 1,657 0 0 FULL price_change 98,233,998 98,232,560 1,438 285 FULL tick_size_change 2,888 2,888 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 12,649,084 11,829,763 4ms 10ms 119ms 8.5s 0 transport_latency_assumed best_bid_ask g 12,647,442 518 80ms 98ms 306ms 8.0s 0 transport_latency_assumed best_bid_ask h 12,648,530 142,574 18ms 25ms 156ms 38.3s 0 transport_latency_assumed best_bid_ask i 12,648,162 137,015 21ms 26ms 85ms 7.9s 0 transport_latency_assumed best_bid_ask k 12,648,442 539,798 12ms 18ms 111ms 20.3s 0 transport_latency_assumed book c 96,640 85,755 7ms 2.0s 4.5d 99.8d 0 book_staleness book g 91,614 3,668 86ms 320ms 2.3d 99.8d 0 book_staleness book h 89,164 3,161 21ms 69ms 1.6min 118.3d 0 book_staleness book i 91,316 6,166 24ms 83ms 7.9h 99.8d 0 book_staleness book k 95,614 13,357 15ms 460ms 3.6d 99.8d 0 book_staleness last_trade_price c 42,845 38,316 6ms 24ms 210ms 3.6s 0 transport_latency_assumed last_trade_price g 42,796 6 85ms 196ms 928ms 7.8s 0 transport_latency_assumed last_trade_price h 42,890 911 19ms 47ms 313ms 28.7s 0 transport_latency_assumed last_trade_price i 42,841 826 23ms 43ms 220ms 3.1s 0 transport_latency_assumed last_trade_price k 42,866 2,894 13ms 34ms 239ms 2.7s 0 transport_latency_assumed market_resolved c 1,079 947 5ms 42ms 43.6s 43.7s 0 transport_latency_assumed market_resolved g 1,079 107 85ms 970ms 49.6s 58.1s 0 transport_latency_assumed market_resolved h 1,079 18 19ms 180ms 47.8s 54.7s 0 transport_latency_assumed market_resolved i 1,079 18 23ms 116ms 48.2s 54.8s 0 transport_latency_assumed market_resolved k 1,079 35 13ms 70ms 54.8s 54.9s 0 transport_latency_assumed new_market c 1,089 526 93ms 53.2s 2.0min 2.4min 0 transport_latency_assumed new_market g 1,089 144 233ms 52.5s 2.0min 2.4min 0 transport_latency_assumed new_market h 1,089 302 122ms 51.3s 1.8min 2.3min 0 transport_latency_assumed new_market i 1,089 442 67ms 51.7s 1.9min 2.4min 0 transport_latency_assumed new_market k 1,089 243 139ms 46.7s 2.0min 2.4min 0 transport_latency_assumed price_change c 98,212,506 91,143,508 5ms 12ms 134ms 8.5s 0 transport_latency_assumed price_change g 98,183,654 5,592 80ms 104ms 403ms 8.6s 0 transport_latency_assumed price_change h 98,210,850 1,270,162 18ms 29ms 178ms 39.2s 0 transport_latency_assumed price_change i 98,210,106 1,207,226 21ms 28ms 104ms 7.9s 0 transport_latency_assumed price_change k 98,206,512 4,606,072 13ms 20ms 130ms 20.3s 0 transport_latency_assumed tick_size_change c 2,888 2,473 5ms 32ms 295ms 347ms 0 transport_latency_assumed tick_size_change g 2,888 not meas. 80ms 168ms 430ms 585ms 0 transport_latency_assumed tick_size_change h 2,888 34 18ms 40ms 352ms 940ms 0 transport_latency_assumed tick_size_change i 2,888 80 21ms 29ms 136ms 178ms 0 transport_latency_assumed tick_size_change k 2,888 301 12ms 23ms 140ms 776ms 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/05/2026-09-25T05.parquet sha256sum 2026-09-25T05.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.