Hour audit: 2026-10-06T22
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-06T22 · corpus v3 · verdict AUDIT PENDING
COVERAGE not measured (this hour is not in the corpus attestation, so we have not looked at it)
VOLUME 102,243,467 rows · 1,114,049,533 bytes (1.04 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured m: 102,190,710 · o: 102,188,296 · i: 102,155,943 · n: 102,111,175 · h: 101,255,600 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 50,233,261 (49.13%) · o: 51,165,008 (50.04%) · i: 389,956 (0.38%) · n: 25,885 (0.03%) · h: 429,357 (0.42%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 102,243,467 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 e79077992a6f8a374f3fb7b5dc39605e5925e2ebabeea5d6ea9799206f6f6e7e
no line in the corpus checksum ledger names this file
joined 102,244,217 to merged 102,243,467, minus 750 (minus 0.0007%)
boundary drops 750 · 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-06T23:59:55Z 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 10,487,640 128,716,201 0-40 73b0d974abe803c63e438552c7e6c0338c22b836a3e8f34030dbf245fead6287 book 143,886 13,792,569 41-41 6e2ff44ccd6043b11b9c95ebfb89c16c65a9fda5b4e362dac4b81bcf7d3c240b last_trade_price 58,539 3,277,595 42-42 2e626280f5774e2731adc130e7c2ab73e484a8bb07057931f962a5b95e2720b9 market_resolved 3,044 460,098 43-43 0d6bb1ebb690a9fd046f8b86c6810bc477a48e843aa402a9cc2e307cf547e59f new_market 700 72,758 44-44 39c251b97f72f7ba9284adad72be7641e84346ae161f0d0bf68e52d781b405e6 price_change 91,546,822 966,456,345 45-394 1a1cabaa08aab51bc701c19872cd202d2cae2927b17441ce0fbf1091fded9bf5 tick_size_change 2,836 104,181 395-395 a9d332c1f787076f01c260cd7a5d8df40024354be9d4f0dae5f14eaa7b127958 EVENT MIX count share price_change 91,546,822 89.54% best_bid_ask 10,487,640 10.26% book 143,886 0.14% last_trade_price 58,539 0.06% market_resolved 3,044 <0.01% tick_size_change 2,836 <0.01% new_market 700 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,487,742 10,487,640 102 66 FULL book 143,888 143,886 2 6,171 FULL last_trade_price 58,539 58,539 0 0 FULL market_resolved 3,044 3,044 0 0 FULL new_market 700 700 0 0 FULL price_change 91,547,468 91,546,822 646 57 FULL tick_size_change 2,836 2,836 0 2 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,457,486 43,354 17ms 24ms 179ms 39.1s 0 transport_latency_assumed best_bid_ask i 10,486,588 34,810 21ms 27ms 102ms 3.8s 0 transport_latency_assumed best_bid_ask m 10,486,944 5,155,875 4ms 10ms 64ms 9.0s 0 transport_latency_assumed best_bid_ask n 10,485,689 1,548 44ms 53ms 194ms 23.4s 0 transport_latency_assumed best_bid_ask o 10,486,780 5,252,053 4ms 11ms 61ms 5.9s 0 transport_latency_assumed book h 124,313 12,424 22ms 815ms 13.9h 45.4d 0 book_staleness book i 120,442 3,728 24ms 300ms 41.1min 130.0d 0 book_staleness book m 121,036 59,837 6ms 27ms 2.7h 130.0d 0 book_staleness book n 121,796 4,992 48ms 1.1s 3.7h 130.0d 0 book_staleness book o 120,371 62,905 6ms 26ms 1.0h 111.4d 0 book_staleness last_trade_price h 55,753 199 19ms 116ms 1.5s 5.7s 0 transport_latency_assumed last_trade_price i 58,349 301 24ms 180ms 1.7s 3.8s 0 transport_latency_assumed last_trade_price m 58,430 28,872 6ms 18ms 187ms 1.2s 0 transport_latency_assumed last_trade_price n 58,078 49 49ms 524ms 5.1s 23.4s 0 transport_latency_assumed last_trade_price o 58,343 29,118 6ms 18ms 154ms 2.8s 0 transport_latency_assumed market_resolved h 2,857 13 19ms 20.7s 49.9s 50.9s 0 transport_latency_assumed market_resolved i 2,857 449 22ms 23.5s 53.5s 56.1s 0 transport_latency_assumed market_resolved m 2,857 1,235 5ms 24.4s 54.0s 56.7s 0 transport_latency_assumed market_resolved n 2,857 138 45ms 316ms 49.0s 55.5s 0 transport_latency_assumed market_resolved o 2,857 1,209 5ms 23.9s 52.0s 54.2s 0 transport_latency_assumed new_market h 459 65 98ms 21.3s 36.0s 1.8min 0 transport_latency_assumed new_market i 459 150 52ms 10.2s 29.9s 1.7min 0 transport_latency_assumed new_market m 459 259 45ms 14.2s 37.5s 1.6min 0 transport_latency_assumed new_market n 459 40 178ms 26.3s 36.5s 1.3min 0 transport_latency_assumed new_market o 459 186 75ms 21.0s 34.5s 1.4min 0 transport_latency_assumed price_change h 90,611,904 373,302 18ms 28ms 550ms 39.1s 0 transport_latency_assumed price_change i 91,484,412 350,518 21ms 32ms 369ms 3.8s 0 transport_latency_assumed price_change m 91,518,148 44,985,684 4ms 11ms 79ms 9.0s 0 transport_latency_assumed price_change n 91,439,460 19,118 44ms 64ms 895ms 23.4s 0 transport_latency_assumed price_change o 91,516,650 45,818,200 4ms 12ms 75ms 12.5s 0 transport_latency_assumed tick_size_change h 2,828 not meas. 17ms 23ms 47ms 80ms 0 transport_latency_assumed tick_size_change i 2,836 not meas. 21ms 27ms 93ms 141ms 0 transport_latency_assumed tick_size_change m 2,836 1,499 4ms 8ms 27ms 39ms 0 transport_latency_assumed tick_size_change n 2,836 not meas. 43ms 49ms 81ms 231ms 0 transport_latency_assumed tick_size_change o 2,836 1,337 4ms 8ms 25ms 84ms 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/22/2026-10-06T22.parquet sha256sum 2026-10-06T22.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.