Hour audit: 2026-09-25T00
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-25T00 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-25T00:00:00.000026918+00:00 · last event 2026-09-25T00:59:59.999836115+00:00
VOLUME 132,499,539 rows · 1,444,913,856 bytes (1.35 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured i: 130,674,449 · h: 130,670,892 · c: 125,487,475 · g: 124,678,233 · k: 109,776,947 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 3,419,341 (2.58%) · h: 4,822,624 (3.64%) · c: 114,497,385 (86.41%) · g: 101,156 (0.08%) · k: 9,659,033 (7.29%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 a717a80f76140d0b275424c19b618ac49efc8b978ccdfe6e969564f61544e43d
the corpus checksum ledger names this file with the same digest
joined 132,502,458 to merged 132,499,539, minus 2,919 (minus 0.0022%)
boundary drops 2,919 · 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-25T03:13:20Z 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 14,448,498 166,176,904 0-55 3479ff1d910bfae383d69214c021b785917cbd40b123d4091d7b1ff1c504a919 book 1,915,875 85,262,245 56-63 9b76b107520a242fa3182c219037b077aa17ba6fb4f740e8c664af61a2b4deb4 last_trade_price 54,257 3,075,725 64-64 7aa06a28c4529dc5c552ec04362912a62e7a4a012d14a97d140e21fc048102fb market_resolved 662 79,458 65-65 0a34d6dcf0a4f35c4631179a87f93d2b4b1c7800deefe2d9dce9fb0fe2c32e99 new_market 621 68,039 66-66 416ff1fc3e4ae194410ba4c19ce6607e337c0b97aa0c0c18e9fbed3380629bf7 price_change 116,077,122 1,188,650,824 67-509 6cbb18836fdf2d835b49febbc3886ca2dc6ae13b99ebdbeff45e6631cf925b94 tick_size_change 2,504 93,203 510-510 c84218f527cadeae797abeccd251a31be61559693face939bfcbc45d28d41bb8 EVENT MIX count share price_change 116,077,122 87.61% best_bid_ask 14,448,498 10.90% book 1,915,875 1.45% last_trade_price 54,257 0.04% tick_size_change 2,504 <0.01% market_resolved 662 <0.01% new_market 621 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 14,448,839 14,448,498 341 1,985 FULL book 1,915,893 1,915,875 18 203,556 FULL last_trade_price 54,259 54,257 2 337 FULL market_resolved 662 662 0 1 FULL new_market 621 621 0 0 FULL price_change 116,079,680 116,077,122 2,558 977 FULL tick_size_change 2,504 2,504 0 108 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 13,815,061 12,717,212 5ms 14ms 93ms 4.9s 0 transport_latency_assumed best_bid_ask g 13,722,687 676 82ms 103ms 252ms 11.7s 0 transport_latency_assumed best_bid_ask h 14,447,469 515,200 18ms 43ms 111ms 6.7s 0 transport_latency_assumed best_bid_ask i 14,446,992 370,169 21ms 30ms 102ms 4.1s 0 transport_latency_assumed best_bid_ask k 11,992,224 845,241 12ms 20ms 85ms 5.4s 0 transport_latency_assumed book c 529,026 172,388 5.2min 3.2d 33.4d 118.1d 0 book_staleness book g 520,753 91,084 5.6min 3.2d 33.4d 118.1d 0 book_staleness book h 114,009 6,996 22ms 91ms 5.5h 99.6d 0 book_staleness book i 126,255 9,566 24ms 1.8min 8.3d 118.1d 0 book_staleness book k 1,735,411 1,635,841 11.4min 4.4d 43.3d 118.1d 0 book_staleness last_trade_price c 51,807 45,693 6ms 28ms 258ms 2.1s 0 transport_latency_assumed last_trade_price g 51,304 17 87ms 253ms 2.5s 11.7s 0 transport_latency_assumed last_trade_price h 54,129 2,685 20ms 60ms 260ms 5.4s 0 transport_latency_assumed last_trade_price i 54,121 1,519 22ms 70ms 382ms 1.7s 0 transport_latency_assumed last_trade_price k 44,680 4,343 13ms 40ms 281ms 1.3s 0 transport_latency_assumed market_resolved c 475 411 5ms 40ms 5.7min 5.7min 0 transport_latency_assumed market_resolved g 469 11 88ms 343ms 5.6min 6.3min 0 transport_latency_assumed market_resolved h 466 21 21ms 65ms 55.7s 55.7s 0 transport_latency_assumed market_resolved i 466 16 22ms 71ms 58.3s 58.3s 0 transport_latency_assumed market_resolved k 548 203 19ms 8.9min 11.2min 11.2min 0 transport_latency_assumed new_market c 431 235 49ms 25.2s 1.1min 1.5min 0 transport_latency_assumed new_market g 431 36 111ms 11.1s 56.9s 1.9min 0 transport_latency_assumed new_market h 431 118 69ms 23.2s 1.1min 1.7min 0 transport_latency_assumed new_market i 431 74 67ms 14.5s 51.6s 1.1min 0 transport_latency_assumed new_market k 451 158 51ms 12.3s 2.2min 4.9min 0 transport_latency_assumed price_change c 111,088,239 101,559,197 5ms 16ms 106ms 5.0s 0 transport_latency_assumed price_change g 110,380,197 9,328 83ms 110ms 331ms 11.8s 0 transport_latency_assumed price_change h 116,051,884 4,297,534 18ms 45ms 128ms 6.7s 0 transport_latency_assumed price_change i 116,043,680 3,037,928 21ms 33ms 126ms 4.1s 0 transport_latency_assumed price_change k 96,001,473 7,173,135 12ms 22ms 97ms 5.6s 0 transport_latency_assumed tick_size_change c 2,436 2,249 5ms 13ms 65ms 174ms 0 transport_latency_assumed tick_size_change g 2,392 4 83ms 104ms 257ms 643ms 0 transport_latency_assumed tick_size_change h 2,504 70 18ms 42ms 101ms 410ms 0 transport_latency_assumed tick_size_change i 2,504 69 21ms 33ms 79ms 427ms 0 transport_latency_assumed tick_size_change k 2,160 112 12ms 18ms 98ms 240ms 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/00/2026-09-25T00.parquet sha256sum 2026-09-25T00.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.