Hour audit: 2026-10-02T08
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-02T08 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-02T08:00:00.000068294+00:00 · last event 2026-10-02T08:59:59.999991203+00:00
VOLUME 112,748,279 rows · 1,175,799,705 bytes (1.10 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured g: 112,483,203 · h: 112,410,402 · k: 112,396,925 · m: 112,395,340 · i: 112,319,185 (each machine's own feed; these overlap and do not sum to the file)
supplied g: 201,757 (0.18%) · h: 598,158 (0.53%) · k: 3,854,240 (3.42%) · m: 94,532,499 (83.84%) · i: 13,561,625 (12.03%) (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 112,748,279 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 b4ec43519573e43bf03cbdb23fc94aadd82ffb2d8b8b9ebed35a0a3d4d92983e
the corpus checksum ledger names this file with the same digest
joined 112,753,993 to merged 112,748,279, minus 5,714 (minus 0.0051%)
boundary drops 5,714 · 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-02T10:45:33Z 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 10,469,770 121,184,045 0-39 f08686531a2c00b43154f3afdc9e2226f8d877262bfbd86b87f48939023c6360 book 431,354 43,902,201 40-41 3178cbe64f60ff43e1383a10a5c41947993cf92b94daa1568059c2b3ad17d5a5 last_trade_price 48,833 2,841,243 42-42 dd2327ebe5cbe2ac4c50ac8aac9574105ec6b683cc073b7584d5e42039c3e13e market_resolved 506 84,347 43-43 41a48be07b1ee87b5924c99628d4297c76c515c55ceb94dcde39417822c96fe5 new_market 641 65,510 44-44 51d864ae31770e3966b3ccbe086d2da8fb86045129da2f25fe7e0ee215a996ab price_change 101,794,691 1,006,344,323 45-433 653d3efdf3543656aee78d9f5a7792db972f9bdd53879d4eaff8df856097085e tick_size_change 2,484 92,571 434-434 9444f75e2e4feec54954a5ec60846a4e3fe88bba8df1c796c940d45c9745d14a EVENT MIX count share price_change 101,794,691 90.28% best_bid_ask 10,469,770 9.29% book 431,354 0.38% last_trade_price 48,833 0.04% tick_size_change 2,484 <0.01% new_market 641 <0.01% market_resolved 506 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,469,917 10,469,770 147 143 FULL book 431,362 431,354 8 142,275 FULL last_trade_price 48,834 48,833 1 1 FULL market_resolved 506 506 0 0 FULL new_market 641 641 0 0 FULL price_change 101,800,249 101,794,691 5,558 114 FULL tick_size_change 2,484 2,484 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 10,465,852 1,797 73ms 90ms 244ms 25.9s 0 transport_latency_assumed best_bid_ask h 10,468,756 50,147 19ms 32ms 128ms 34.8s 0 transport_latency_assumed best_bid_ask i 10,449,779 1,315,864 22ms 42ms 150ms 33.5s 0 transport_latency_assumed best_bid_ask k 10,469,035 303,128 13ms 22ms 120ms 30.8s 0 transport_latency_assumed best_bid_ask m 10,469,604 8,798,834 5ms 9ms 55ms 2.8s 0 transport_latency_assumed book g 311,819 177,490 3.4min 12.9h 40.8d 125.4d 0 book_staleness book h 106,049 6,583 23ms 255ms 8.4h 106.9d 0 book_staleness book i 248,060 159,599 44.6s 7.6h 40.8d 125.4d 0 book_staleness book k 99,004 3,686 15ms 43ms 1.1s 55.0d 0 book_staleness book m 98,758 83,996 6ms 12ms 254ms 7.2h 0 book_staleness last_trade_price g 48,629 8 78ms 317ms 4.6s 25.9s 0 transport_latency_assumed last_trade_price h 48,824 242 20ms 53ms 619ms 16.5s 0 transport_latency_assumed last_trade_price i 48,685 5,517 26ms 55ms 725ms 17.3s 0 transport_latency_assumed last_trade_price k 48,823 1,477 14ms 33ms 237ms 2.0s 0 transport_latency_assumed last_trade_price m 48,819 41,589 6ms 11ms 109ms 2.2s 0 transport_latency_assumed market_resolved g 499 not meas. 78ms 310ms 50.2s 55.4s 0 transport_latency_assumed market_resolved h 499 2 21ms 70ms 48.7s 53.1s 0 transport_latency_assumed market_resolved i 499 73 39ms 130ms 44.5s 1.7min 0 transport_latency_assumed market_resolved k 499 13 15ms 91ms 52.2s 55.8s 0 transport_latency_assumed market_resolved m 499 418 5ms 14ms 35.9s 40.3s 0 transport_latency_assumed new_market g 429 46 228ms 9.6s 30.0s 1.4min 0 transport_latency_assumed new_market h 429 72 117ms 447ms 14.3s 1.4min 0 transport_latency_assumed new_market i 429 78 135ms 10.3s 30.0s 1.7min 0 transport_latency_assumed new_market k 429 72 123ms 15.1s 29.1s 1.5min 0 transport_latency_assumed new_market m 429 373 24ms 26.1s 28.1s 1.3min 0 transport_latency_assumed price_change g 101,653,491 22,416 73ms 99ms 962ms 26.0s 0 transport_latency_assumed price_change h 101,783,361 541,084 19ms 33ms 259ms 35.4s 0 transport_latency_assumed price_change i 101,569,249 12,080,290 22ms 43ms 386ms 34.7s 0 transport_latency_assumed price_change k 101,776,651 3,545,820 13ms 24ms 132ms 32.4s 0 transport_latency_assumed price_change m 101,774,747 85,605,081 5ms 10ms 80ms 3.6s 0 transport_latency_assumed tick_size_change g 2,484 not meas. 73ms 89ms 337ms 807ms 0 transport_latency_assumed tick_size_change h 2,484 28 19ms 32ms 214ms 415ms 0 transport_latency_assumed tick_size_change i 2,484 204 23ms 43ms 186ms 319ms 0 transport_latency_assumed tick_size_change k 2,484 44 13ms 22ms 133ms 4.7s 0 transport_latency_assumed tick_size_change m 2,484 2,208 5ms 9ms 42ms 659ms 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/08/2026-10-02T08.parquet sha256sum 2026-10-02T08.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.