Hour audit: 2026-10-09T13
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.
1 finding
- the checksum ledger does not name this file. No line in the corpus checksum ledger names this file, so the documented verification step passes over it in silence rather than checking it. The manifest below still carries the digest.
1 check could not be evaluated for this hour, listed with the reason in the block below. A check we could not run is recorded as exactly that, and never counted as a pass.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-10-09T13 · corpus v3 · verdict AUDIT PENDING
COVERAGE not measured (this hour is not in the corpus attestation, so we have not looked at it)
VOLUME 130,399,278 rows · 1,587,327,819 bytes (1.48 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured m: 129,306,958 · h: 129,231,518 · i: 129,180,856 · n: 128,424,089 · o: 122,922,036 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 68,446,222 (52.49%) · h: 2,400,618 (1.84%) · i: 1,551,130 (1.19%) · n: 244,743 (0.19%) · o: 57,756,565 (44.29%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 a383d2bfb793248d0ba5f1c613be425774acbac401f91f3c6b43cc34a8be3538
no line in the corpus checksum ledger names this file
joined 130,404,932 to merged 130,399,278, minus 5,654 (minus 0.0043%)
boundary drops 5,654 · 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-10T03:41:27Z as himno
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 6/8 pass, 1 finding, 1 not evaluated
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
FINDING the checksum ledger does not name this file
SKIPPED the hour's minutes have not been measured
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,490,872 161,969,274 0-47 d129e8e3196026fd132c45003f3483d2163d2bb6c8673c812e12491011e136f8 book 1,429,350 104,542,141 48-53 7ca56816e9b563b956daf6a15588573361410aa254368c7b27dacf3ad416dfa0 last_trade_price 65,158 3,834,628 54-54 26d201ac0e80943f90bd9412419d0783317ef8f032b8b68639d08858b916ea17 market_resolved 617 90,460 55-55 3ba1c1d1ad669c761018a4ff1d2a4059ec4aec82abb51afbe0426afd2bd4376b new_market 1,689 167,654 56-56 3a15440a56f3bdfcf349e668cd7153e8bec3ece84f4ee46eeb6efb91027be067 price_change 116,407,228 1,315,075,135 57-501 77b07111864d6f3a2d7607d128aa53cf270c95a495564370c3e6c30de87dd899 tick_size_change 4,364 163,337 502-502 cab278f021f87331388044893c6df1b9cfbd0fd7cba677ddd5706599c16975e8 EVENT MIX count share price_change 116,407,228 89.27% best_bid_ask 12,490,872 9.58% book 1,429,350 1.10% last_trade_price 65,158 0.05% tick_size_change 4,364 <0.01% new_market 1,689 <0.01% market_resolved 617 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,491,007 12,490,872 135 4,455 FULL book 1,432,124 1,429,350 2,774 258,913 FULL last_trade_price 65,159 65,158 1 140 FULL market_resolved 617 617 0 8 FULL new_market 1,689 1,689 0 0 FULL price_change 116,409,972 116,407,228 2,744 1,994 FULL tick_size_change 4,364 4,364 0 55 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 12,487,863 201,231 19ms 41ms 450ms 51.1s 0 transport_latency_assumed best_bid_ask i 12,484,238 121,517 22ms 44ms 293ms 9.1s 0 transport_latency_assumed best_bid_ask m 12,488,425 6,523,017 6ms 23ms 195ms 5.4s 0 transport_latency_assumed best_bid_ask n 12,479,662 6,348 46ms 79ms 556ms 22.9s 0 transport_latency_assumed best_bid_ask o 11,845,883 5,638,759 6ms 23ms 208ms 7.4s 0 transport_latency_assumed book h 388,390 147,966 1.8min 1.1d 48.0d 132.7d 0 book_staleness book i 526,724 289,105 3.9min 1.4d 48.0d 132.6d 0 book_staleness book m 435,625 263,194 2.6min 1.3d 48.0d 132.6d 0 book_staleness book n 374,787 159,080 1.9min 1.1d 48.0d 132.6d 0 book_staleness book o 903,116 570,005 5.3min 1.4d 48.0d 132.6d 0 book_staleness last_trade_price h 64,984 1,040 22ms 165ms 884ms 48.8s 0 transport_latency_assumed last_trade_price i 64,361 417 30ms 627ms 3.9s 9.1s 0 transport_latency_assumed last_trade_price m 65,011 35,267 8ms 33ms 204ms 3.5s 0 transport_latency_assumed last_trade_price n 62,573 61 62ms 1.3s 10.7s 21.7s 0 transport_latency_assumed last_trade_price o 62,138 28,373 8ms 42ms 266ms 5.8s 0 transport_latency_assumed market_resolved h 539 13 25ms 98ms 42.9s 55.2s 0 transport_latency_assumed market_resolved i 539 65 37ms 17.7s 57.0s 57.1s 0 transport_latency_assumed market_resolved m 539 277 7ms 71ms 57.6s 57.7s 0 transport_latency_assumed market_resolved n 539 2 54ms 320ms 51.4s 53.6s 0 transport_latency_assumed market_resolved o 531 260 7ms 34.6s 6.3min 6.3min 0 transport_latency_assumed new_market h 1,074 222 123ms 52.6s 1.8min 2.2min 0 transport_latency_assumed new_market i 1,074 225 98ms 47.3s 1.7min 2.1min 0 transport_latency_assumed new_market m 1,074 639 58ms 31.2s 1.8min 2.1min 0 transport_latency_assumed new_market n 1,074 178 186ms 26.5s 1.8min 2.0min 0 transport_latency_assumed new_market o 1,074 425 76ms 47.0s 1.7min 2.1min 0 transport_latency_assumed price_change h 116,284,304 2,050,046 20ms 56ms 929ms 51.8s 0 transport_latency_assumed price_change i 116,099,556 1,139,720 22ms 76ms 2.4s 9.1s 0 transport_latency_assumed price_change m 116,311,920 61,621,472 6ms 27ms 284ms 6.1s 0 transport_latency_assumed price_change n 115,501,098 79,070 47ms 152ms 4.0s 23.0s 0 transport_latency_assumed price_change o 110,105,142 51,516,920 7ms 29ms 353ms 8.5s 0 transport_latency_assumed tick_size_change h 4,364 100 20ms 49ms 344ms 7.9s 0 transport_latency_assumed tick_size_change i 4,364 81 23ms 55ms 181ms 507ms 0 transport_latency_assumed tick_size_change m 4,364 2,356 7ms 30ms 193ms 525ms 0 transport_latency_assumed tick_size_change n 4,356 4 47ms 97ms 424ms 1.2s 0 transport_latency_assumed tick_size_change o 4,152 1,823 7ms 36ms 242ms 737ms 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-09/13/2026-10-09T13.parquet sha256sum 2026-10-09T13.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.