Hour audit: 2026-10-02T18
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-02T18 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-02T18:00:00.000171467+00:00 · last event 2026-10-02T18:59:59.999948001+00:00
VOLUME 115,999,967 rows · 1,286,925,409 bytes (1.20 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured k: 115,796,331 · m: 115,766,914 · h: 115,739,442 · i: 115,624,781 · g: 113,986,928 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 8,443,313 (7.28%) · m: 101,376,325 (87.39%) · h: 3,971,168 (3.42%) · i: 2,097,968 (1.81%) · g: 111,193 (0.10%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 115,999,967 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 cad73bbdd8708aeb9962f521dee5453502342c9b3931cdd7bf912606315954d2
the corpus checksum ledger names this file with the same digest
joined 116,001,984 to merged 115,999,967, minus 2,017 (minus 0.0017%)
boundary drops 2,017 · 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-02T20:46:14Z 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,614,052 120,213,235 0-36 91a533e63bea75971d3dfe18d30ee54707a3c258b504c701b9b3097e079501fd book 340,747 34,748,429 37-38 a763388ecca7c5ae594b98e0ce0ffc88884fce3f0b73f971107e3546b632ea11 last_trade_price 67,203 3,869,009 39-39 0c7cf9cd366517440a147500568b515d9d8aa2ee20fbe5175b331df42548e438 market_resolved 883 143,023 40-40 16a3e1c20f4791aaa516b43fd63afd9f0492e62507690c2a45b64b42a34e79d2 new_market 3,352 303,687 41-41 ea994ba4bd3ea5e0cab2892b3abed2b9acc48400ecb114d309a5c2f8a5fe9ad7 price_change 105,969,762 1,126,179,810 42-446 668d6b028401361731fe2feebda0389f5bcf0104a5d4354b5a7124d58641d99a tick_size_change 3,968 144,740 447-447 d00d524fddffc9d47bc07f843c5ea32071151d509b196340a569d5aa23a2b7d9 EVENT MIX count share price_change 105,969,762 91.35% best_bid_ask 9,614,052 8.29% book 340,747 0.29% last_trade_price 67,203 0.06% tick_size_change 3,968 <0.01% new_market 3,352 <0.01% market_resolved 883 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,614,164 9,614,052 112 269 FULL book 340,774 340,747 27 86,371 FULL last_trade_price 67,208 67,203 5 0 FULL market_resolved 888 883 5 5 FULL new_market 3,352 3,352 0 0 FULL price_change 105,971,630 105,969,762 1,868 186 FULL tick_size_change 3,968 3,968 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,581,037 3,182 81ms 170ms 1.6s 50.9s 0 transport_latency_assumed best_bid_ask h 9,609,277 287,734 19ms 45ms 574ms 1.1min 0 transport_latency_assumed best_bid_ask i 9,609,523 158,645 22ms 46ms 335ms 58.2s 0 transport_latency_assumed best_bid_ask k 9,610,818 641,135 15ms 42ms 411ms 52.9s 0 transport_latency_assumed best_bid_ask m 9,612,452 8,523,356 6ms 24ms 239ms 13.5s 0 transport_latency_assumed book g 190,789 59,647 322ms 8.0h 27.2d 125.8d 0 book_staleness book h 186,779 49,388 37ms 3.2h 25.3d 107.4d 0 book_staleness book i 172,861 36,203 39ms 52.4min 23.4d 125.8d 0 book_staleness book k 176,964 43,382 28ms 1.3h 25.3d 107.3d 0 book_staleness book m 176,341 152,127 10ms 1.0h 25.3d 107.3d 0 book_staleness last_trade_price g 61,298 65 96ms 3.4s 19.1s 50.9s 0 transport_latency_assumed last_trade_price h 67,026 2,787 22ms 173ms 4.1s 1.1min 0 transport_latency_assumed last_trade_price i 66,559 946 27ms 325ms 4.9s 17.8s 0 transport_latency_assumed last_trade_price k 67,168 5,325 18ms 124ms 871ms 24.7s 0 transport_latency_assumed last_trade_price m 67,183 58,080 7ms 59ms 513ms 1.9s 0 transport_latency_assumed market_resolved g 862 not meas. 89ms 1.2s 32.5s 48.4s 0 transport_latency_assumed market_resolved h 862 16 21ms 362ms 36.2s 52.2s 0 transport_latency_assumed market_resolved i 862 9 25ms 13.2s 56.6s 57.5s 0 transport_latency_assumed market_resolved k 867 50 18ms 9.4s 44.1s 57.3s 0 transport_latency_assumed market_resolved m 862 808 6ms 11.8s 55.8s 56.1s 0 transport_latency_assumed new_market g 1,948 353 396ms 26.5s 1.1min 1.7min 0 transport_latency_assumed new_market h 1,948 535 217ms 35.1s 1.1min 1.4min 0 transport_latency_assumed new_market i 1,948 782 127ms 30.7s 1.0min 1.8min 0 transport_latency_assumed new_market k 1,948 339 248ms 31.1s 1.0min 1.6min 0 transport_latency_assumed new_market m 1,948 1,343 71ms 28.5s 1.0min 1.4min 0 transport_latency_assumed price_change g 104,147,026 47,946 83ms 328ms 9.9s 51.1s 0 transport_latency_assumed price_change h 105,869,582 3,630,596 19ms 65ms 1.0s 1.1min 0 transport_latency_assumed price_change i 105,769,060 1,901,332 23ms 72ms 953ms 58.4s 0 transport_latency_assumed price_change k 105,934,598 7,752,848 16ms 58ms 524ms 57.6s 0 transport_latency_assumed price_change m 105,904,160 92,637,040 6ms 32ms 300ms 13.6s 0 transport_latency_assumed tick_size_change g 3,968 not meas. 80ms 126ms 597ms 13.1s 0 transport_latency_assumed tick_size_change h 3,968 112 20ms 39ms 260ms 27.9s 0 transport_latency_assumed tick_size_change i 3,968 51 22ms 46ms 211ms 1.1s 0 transport_latency_assumed tick_size_change k 3,968 234 15ms 35ms 242ms 1.8s 0 transport_latency_assumed tick_size_change m 3,968 3,571 6ms 19ms 139ms 300ms 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/18/2026-10-02T18.parquet sha256sum 2026-10-02T18.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.