Hour audit: 2026-10-02T22
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-10-02T22 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-02T22:00:00.000006885+00:00 · last event 2026-10-02T22:59:59.999577540+00:00
VOLUME 98,066,649 rows · 1,019,188,750 bytes (971.97 MiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured i: 97,954,282 · k: 97,945,334 · m: 97,891,731 · h: 97,873,371 · g: 97,308,785 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 814,647 (0.83%) · k: 4,452,687 (4.54%) · m: 91,419,209 (93.22%) · h: 1,341,108 (1.37%) · g: 38,998 (0.04%) (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 98,066,649 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 1fc0264d1350a33c010d68316b102b27f383341abf6cba608891cef13049b488
the corpus checksum ledger names this file with the same digest
joined 98,070,154 to merged 98,066,649, minus 3,505 (minus 0.0036%)
boundary drops 3,505 · 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-10-03T00:43:10Z as ghikm
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 9,494,509 112,737,761 0-36 d26fc9c5c3c9c5b4eea0500d4cb5d169efe933f375465dfd531d19e8822b1624 book 163,324 15,764,263 37-37 72d6b34ea322cec20d816fc85d565ce9b6e291c7d121a1fdc32d2a0eecda112b last_trade_price 56,553 3,184,347 38-38 f5fe095ac5a07c6ad74e639369f2f6a0786f6a3c485f570aa2dcf9ae35ee2ecb market_resolved 2,861 442,152 39-39 1d327eb9e7e91f275bcdd535f3ff1f831a36864b17bd1de910afaa7b5a56dec5 new_market 3,074 301,618 40-40 b64cd30fda24e1124074c035b9b21f96a92db9d2e6e55fba052d8d1da343ca24 price_change 88,342,976 885,513,013 41-378 a768f694039198fa880d31b7328d84942fe9072e4b8062411a6551ffcf8a28b7 tick_size_change 3,352 123,078 379-379 be5c99555997c60a2b035f0467faae6bce6bcbcf4b2cf31e1aa451ab8df4db63 EVENT MIX count share price_change 88,342,976 90.08% best_bid_ask 9,494,509 9.68% book 163,324 0.17% last_trade_price 56,553 0.06% tick_size_change 3,352 <0.01% new_market 3,074 <0.01% market_resolved 2,861 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,494,744 9,494,509 235 91 FULL book 163,358 163,324 34 15,045 FULL last_trade_price 56,553 56,553 0 1 FULL market_resolved 2,861 2,861 0 1 FULL new_market 3,074 3,074 0 0 FULL price_change 88,346,212 88,342,976 3,236 195 FULL tick_size_change 3,352 3,352 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,482,296 2,185 81ms 117ms 1.1s 55.8s 0 transport_latency_assumed best_bid_ask h 9,490,927 115,811 18ms 29ms 482ms 1.4min 0 transport_latency_assumed best_bid_ask i 9,491,997 70,118 21ms 30ms 278ms 26.0s 0 transport_latency_assumed best_bid_ask k 9,492,278 395,509 13ms 25ms 383ms 1.4min 0 transport_latency_assumed best_bid_ask m 9,491,198 8,910,886 5ms 11ms 141ms 7.9s 0 transport_latency_assumed book g 131,830 19,280 97ms 3.4min 6.3d 107.5d 0 book_staleness book h 123,004 10,147 22ms 468ms 8.4h 126.0d 0 book_staleness book i 123,006 7,596 24ms 645ms 14.9h 107.5d 0 book_staleness book k 125,629 16,844 17ms 710ms 21.3h 107.5d 0 book_staleness book m 122,024 109,457 7ms 99ms 2.8h 13.3d 0 book_staleness last_trade_price g 54,420 20 94ms 1.8s 16.4s 56.1s 0 transport_latency_assumed last_trade_price h 56,064 1,120 20ms 86ms 729ms 58.1s 0 transport_latency_assumed last_trade_price i 56,243 429 23ms 157ms 1.2s 9.6s 0 transport_latency_assumed last_trade_price k 56,321 3,817 14ms 56ms 498ms 41.4s 0 transport_latency_assumed last_trade_price m 56,193 51,167 6ms 22ms 218ms 2.9s 0 transport_latency_assumed market_resolved g 2,757 5 81ms 424ms 47.2s 50.3s 0 transport_latency_assumed market_resolved h 2,758 122 18ms 136ms 45.2s 58.4s 0 transport_latency_assumed market_resolved i 2,758 251 22ms 17.7s 49.3s 54.8s 0 transport_latency_assumed market_resolved k 2,758 103 13ms 18.6s 50.1s 56.4s 0 transport_latency_assumed market_resolved m 2,758 2,380 5ms 17.7s 49.2s 56.3s 0 transport_latency_assumed new_market g 1,954 388 592ms 26.6s 1.7min 2.3min 0 transport_latency_assumed new_market h 1,954 654 326ms 26.5s 1.8min 2.5min 0 transport_latency_assumed new_market i 1,954 343 288ms 25.7s 1.7min 2.2min 0 transport_latency_assumed new_market k 1,954 532 351ms 26.1s 2.0min 2.2min 0 transport_latency_assumed new_market m 1,954 1,157 92ms 25.0s 1.8min 2.3min 0 transport_latency_assumed price_change g 87,632,176 17,120 82ms 194ms 6.1s 56.1s 0 transport_latency_assumed price_change h 88,195,312 1,213,228 18ms 36ms 610ms 1.4min 0 transport_latency_assumed price_change i 88,274,972 735,886 21ms 41ms 523ms 26.6s 0 transport_latency_assumed price_change k 88,263,042 4,035,712 13ms 30ms 415ms 1.4min 0 transport_latency_assumed price_change m 88,214,252 82,341,030 5ms 13ms 158ms 8.1s 0 transport_latency_assumed tick_size_change g 3,352 not meas. 80ms 97ms 226ms 573ms 0 transport_latency_assumed tick_size_change h 3,352 26 17ms 24ms 65ms 6.6s 0 transport_latency_assumed tick_size_change i 3,352 24 21ms 28ms 57ms 110ms 0 transport_latency_assumed tick_size_change k 3,352 170 13ms 22ms 137ms 15.5s 0 transport_latency_assumed tick_size_change m 3,352 3,132 5ms 10ms 65ms 221ms 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-10-02/22/2026-10-02T22.parquet sha256sum 2026-10-02T22.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.