Hour audit: 2026-10-06T21
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.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-10-06T21 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-10-06T21:00:00.000189720+00:00 · last event 2026-10-06T21:59:59.999436278+00:00
VOLUME 99,250,728 rows · 1,079,645,533 bytes (1.01 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured m: 99,217,084 · o: 99,209,740 · h: 99,193,635 · i: 99,189,980 · n: 99,105,597 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 50,484,639 (50.87%) · o: 48,109,029 (48.47%) · h: 370,997 (0.37%) · i: 268,048 (0.27%) · n: 18,015 (0.02%) (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 99,250,728 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 ccfc373197f8a69e93dea1f3d2f051a966903c87809598710324434b812e308c
no line in the corpus checksum ledger names this file
joined 99,251,702 to merged 99,250,728, minus 974 (minus 0.0010%)
boundary drops 974 · 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-06T22:59:07Z 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 7/8 pass, 1 finding
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
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,203,990 125,909,605 0-38 37c09386574bec4b7a7bb7508df577042126879747fabb9bea04b3ae9e571336 book 121,379 12,089,309 39-39 ae2c35e28faff4e59e2f18f0ee6b8878edb6886d704f7597b975574c7a433867 last_trade_price 52,365 2,977,118 40-40 e4644f79ff8616fed22575938ab298b423da91567c78af802adc4a22a0b135f7 market_resolved 1,994 306,025 41-41 bf7bf9c31df1751fcc6ff65dde9e26dc340d0ee182a1b05f324d9e735886d20c new_market 612 63,261 42-42 6202abad0d944f8cb38cb966be1cf772ff51c3ff8e5065ebdbdd3974d629794b price_change 88,867,440 937,056,662 43-382 f152bf3fdf8025fdabadd7b1c9252f25a9096c2463469d1cebf2f4855b15b95b tick_size_change 2,948 109,016 383-383 346740feb9588ee9207347f05425bfda9248f41481785b57f6206c50cd5eff37 EVENT MIX count share price_change 88,867,440 89.54% best_bid_ask 10,203,990 10.28% book 121,379 0.12% last_trade_price 52,365 0.05% tick_size_change 2,948 <0.01% market_resolved 1,994 <0.01% new_market 612 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,204,118 10,203,990 128 48 FULL book 121,379 121,379 0 6,142 FULL last_trade_price 52,365 52,365 0 0 FULL market_resolved 1,994 1,994 0 0 FULL new_market 612 612 0 0 FULL price_change 88,868,286 88,867,440 846 50 FULL tick_size_change 2,948 2,948 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,203,154 32,871 17ms 23ms 110ms 39.8s 0 transport_latency_assumed best_bid_ask i 10,203,134 25,293 21ms 26ms 91ms 4.0s 0 transport_latency_assumed best_bid_ask m 10,203,444 5,195,767 4ms 9ms 54ms 5.5s 0 transport_latency_assumed best_bid_ask n 10,200,912 1,104 44ms 52ms 179ms 11.5s 0 transport_latency_assumed best_bid_ask o 10,203,426 4,948,955 4ms 10ms 55ms 7.7s 0 transport_latency_assumed book h 108,878 4,561 22ms 100ms 4.3h 111.4d 0 book_staleness book i 107,232 2,630 24ms 412ms 12.7min 111.4d 0 book_staleness book m 107,221 57,462 6ms 22ms 18.6min 111.4d 0 book_staleness book n 109,879 5,826 48ms 1.9s 3.7h 111.4d 0 book_staleness book o 107,538 50,900 7ms 22ms 56.5min 111.4d 0 book_staleness last_trade_price h 52,187 349 19ms 60ms 684ms 6.4s 0 transport_latency_assumed last_trade_price i 52,214 196 24ms 284ms 2.1s 2.7s 0 transport_latency_assumed last_trade_price m 52,189 27,045 6ms 16ms 215ms 1.3s 0 transport_latency_assumed last_trade_price n 51,652 12 48ms 595ms 7.0s 11.5s 0 transport_latency_assumed last_trade_price o 52,218 24,763 6ms 17ms 190ms 4.0s 0 transport_latency_assumed market_resolved h 1,926 5 19ms 43ms 47.8s 54.9s 0 transport_latency_assumed market_resolved i 1,926 137 22ms 69ms 51.6s 54.5s 0 transport_latency_assumed market_resolved m 1,926 924 5ms 16ms 52.7s 55.7s 0 transport_latency_assumed market_resolved n 1,926 41 45ms 111ms 53.9s 54.7s 0 transport_latency_assumed market_resolved o 1,926 887 5ms 13ms 48.1s 54.2s 0 transport_latency_assumed new_market h 396 71 83ms 11.1s 27.8s 1.5min 0 transport_latency_assumed new_market i 396 112 59ms 9.8s 28.7s 1.7min 0 transport_latency_assumed new_market m 396 234 35ms 10.1s 26.4s 1.7min 0 transport_latency_assumed new_market n 396 38 167ms 10.1s 25.9s 1.6min 0 transport_latency_assumed new_market o 396 157 63ms 11.4s 28.5s 1.7min 0 transport_latency_assumed price_change h 88,824,146 333,132 18ms 25ms 217ms 40.0s 0 transport_latency_assumed price_change i 88,822,130 239,676 21ms 29ms 341ms 4.0s 0 transport_latency_assumed price_change m 88,848,960 45,201,726 4ms 10ms 69ms 5.5s 0 transport_latency_assumed price_change n 88,737,884 10,994 44ms 58ms 646ms 11.5s 0 transport_latency_assumed price_change o 88,841,288 43,081,912 4ms 11ms 68ms 7.7s 0 transport_latency_assumed tick_size_change h 2,948 8 18ms 23ms 88ms 2.3s 0 transport_latency_assumed tick_size_change i 2,948 4 22ms 29ms 59ms 273ms 0 transport_latency_assumed tick_size_change m 2,948 1,481 4ms 9ms 40ms 214ms 0 transport_latency_assumed tick_size_change n 2,948 not meas. 44ms 52ms 112ms 206ms 0 transport_latency_assumed tick_size_change o 2,948 1,455 4ms 9ms 48ms 978ms 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-06/21/2026-10-06T21.parquet sha256sum 2026-10-06T21.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.