Hour audit: 2026-10-09T19
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-09T19 · corpus v3 · verdict AUDIT PENDING
COVERAGE not measured (this hour is not in the corpus attestation, so we have not looked at it)
VOLUME 135,983,590 rows · 1,563,408,001 bytes (1.46 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 135,890,709 · m: 135,789,528 · h: 135,773,259 · n: 135,604,002 · i: 135,584,099 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 65,797,322 (48.39%) · m: 68,231,410 (50.18%) · h: 917,596 (0.67%) · n: 164,288 (0.12%) · i: 872,974 (0.64%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 e3ee1e616b8fa60c0d4c62043a4760eeea518194905ebeee594c520ff5bdb0fe
no line in the corpus checksum ledger names this file
joined 135,984,804 to merged 135,983,590, minus 1,214 (minus 0.0009%)
boundary drops 1,214 · 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-10T07:08:33Z 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,795,516 160,451,509 0-48 d0eae87581c95c6e6ef93aa0efd6ec25daf7604ce7c0d000ef1fd34df1f9d658 book 217,088 24,516,525 49-49 35dd54ba3da6eb1f544297b70929b42b8dc91833353d02154911621bc229b02d last_trade_price 60,101 3,615,348 50-50 2a7cefb665435ec20410ccd85b8b64b47db090106f6dbe1c2d725c0e7f34ed17 market_resolved 1,237 202,156 51-51 3c68684698116617e8df99703734b4b5f2e11d0b67090e520a90afbd0a2b166c new_market 2,398 230,442 52-52 936900c2e2847310f50f910129590c7d968b68a5806d159b969365f161ff72eb price_change 122,898,978 1,372,541,951 53-521 958adabfb87e551babe35d18ab47f54f6951fa3e045a9e11a4aeae6ca31af3c1 tick_size_change 8,272 304,997 522-522 95c6dea3f87f1a89aa3e7aa52b44754d9c495a5e5160464112fa40bf97670198 EVENT MIX count share price_change 122,898,978 90.38% best_bid_ask 12,795,516 9.41% book 217,088 0.16% last_trade_price 60,101 0.04% tick_size_change 8,272 <0.01% new_market 2,398 <0.01% market_resolved 1,237 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,795,663 12,795,516 147 91 FULL book 217,092 217,088 4 43,020 FULL last_trade_price 60,102 60,101 1 28 FULL market_resolved 1,237 1,237 0 5 FULL new_market 2,398 2,398 0 5 FULL price_change 122,900,040 122,898,978 1,062 1,209 FULL tick_size_change 8,272 8,272 0 1 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 12,791,731 78,839 19ms 34ms 594ms 1.5min 0 transport_latency_assumed best_bid_ask i 12,788,194 76,364 21ms 39ms 190ms 11.1s 0 transport_latency_assumed best_bid_ask m 12,794,506 6,456,097 6ms 15ms 151ms 22.6s 0 transport_latency_assumed best_bid_ask n 12,791,150 13,683 44ms 64ms 358ms 21.5s 0 transport_latency_assumed best_bid_ask o 12,794,508 6,170,533 6ms 16ms 180ms 23.8s 0 transport_latency_assumed book h 142,927 22,036 26ms 3.6min 13.8d 114.4d 0 book_staleness book i 147,676 26,889 30ms 18.9min 13.2d 114.4d 0 book_staleness book m 144,294 82,985 8ms 6.4min 8.4d 114.4d 0 book_staleness book n 129,869 9,385 49ms 2.9s 1.1d 114.4d 0 book_staleness book o 140,582 75,793 8ms 1.6min 6.2d 132.9d 0 book_staleness last_trade_price h 59,915 410 21ms 93ms 1.1s 51.7s 0 transport_latency_assumed last_trade_price i 59,275 365 25ms 187ms 2.0s 11.1s 0 transport_latency_assumed last_trade_price m 59,991 30,229 7ms 22ms 237ms 7.0s 0 transport_latency_assumed last_trade_price n 59,393 129 48ms 372ms 6.6s 21.6s 0 transport_latency_assumed last_trade_price o 60,065 28,968 7ms 20ms 260ms 11.0s 0 transport_latency_assumed market_resolved h 1,206 5 21ms 92ms 51.2s 56.3s 0 transport_latency_assumed market_resolved i 1,209 78 23ms 129ms 44.7s 50.7s 0 transport_latency_assumed market_resolved m 1,210 574 6ms 32ms 50.1s 56.2s 0 transport_latency_assumed market_resolved n 1,207 3 47ms 210ms 50.4s 1.0min 0 transport_latency_assumed market_resolved o 1,210 577 6ms 19ms 55.8s 56.1s 0 transport_latency_assumed new_market h 1,424 207 213ms 11.5s 38.2s 1.9min 0 transport_latency_assumed new_market i 1,424 326 136ms 10.7s 40.3s 1.6min 0 transport_latency_assumed new_market m 1,421 1,118 50ms 16.9s 39.3s 1.5min 0 transport_latency_assumed new_market n 1,419 242 243ms 12.6s 39.3s 1.1min 0 transport_latency_assumed new_market o 1,424 505 127ms 12.3s 37.8s 1.7min 0 transport_latency_assumed price_change h 122,767,784 816,066 19ms 41ms 768ms 1.6min 0 transport_latency_assumed price_change i 122,578,049 768,920 21ms 43ms 534ms 11.2s 0 transport_latency_assumed price_change m 122,779,834 61,656,168 6ms 17ms 183ms 22.6s 0 transport_latency_assumed price_change n 122,612,696 140,838 45ms 81ms 1.1s 21.6s 0 transport_latency_assumed price_change o 122,884,648 59,516,986 6ms 17ms 213ms 25.0s 0 transport_latency_assumed tick_size_change h 8,272 33 19ms 30ms 455ms 32.0s 0 transport_latency_assumed tick_size_change i 8,272 32 21ms 41ms 108ms 629ms 0 transport_latency_assumed tick_size_change m 8,272 4,239 5ms 13ms 55ms 370ms 0 transport_latency_assumed tick_size_change n 8,268 8 44ms 61ms 176ms 644ms 0 transport_latency_assumed tick_size_change o 8,272 3,960 5ms 14ms 82ms 1.0s 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/19/2026-10-09T19.parquet sha256sum 2026-10-09T19.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.