Hour audit: 2026-10-05T21
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-05T21 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-05T21:00:00.000144736+00:00 · last event 2026-10-05T21:59:59.999985704+00:00
VOLUME 102,725,109 rows · 1,117,740,144 bytes (1.04 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured m: 102,607,332 · o: 102,605,772 · h: 102,567,614 · i: 102,550,381 · n: 101,983,729 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 53,035,155 (51.63%) · o: 48,837,365 (47.54%) · h: 400,664 (0.39%) · i: 370,307 (0.36%) · n: 81,618 (0.08%) (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,725,109 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 74c09ea11050dee28e7bc3329d4be27beb9e79ef510e2158e764319cc2844256
the corpus checksum ledger names this file with the same digest
joined 102,726,151 to merged 102,725,109, minus 1,042 (minus 0.0010%)
boundary drops 1,042 · 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-05T22:59:03Z 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 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,008,770 123,958,818 0-38 8df34eff38b5dce0c4982498f5db1852fefbe2c13418b0ff43f1c223a8c79f5a book 118,950 12,550,714 39-39 0afa462ea2449ebaa47567687d1994139f7b428effe2cfdc96c2154eb006d1f6 last_trade_price 43,241 2,539,067 40-40 8175b2599affcb7a3db1ab5af9724c02426cb44e38e154cb049dc275a728eed1 market_resolved 2,949 440,095 41-41 0421e19f17498d028683e802c202789aeb09cb91e2d204c9f6f219488e7c28f5 new_market 1,245 122,328 42-42 6b941480cae6e4efb85c4e43a59a9001a0200b56298f6d3225bccd6ebe2d5afe price_change 92,547,006 976,844,663 43-396 82db0ebd1f4f185747fa5c472d2d6271f55ba3f0393b4c7c93bb436c41a3de6f tick_size_change 2,948 108,476 397-397 1af3a141e97156ccee9700ebb9b161072b3b4af043548bd0a3338e972ca90c8b EVENT MIX count share price_change 92,547,006 90.09% best_bid_ask 10,008,770 9.74% book 118,950 0.12% last_trade_price 43,241 0.04% market_resolved 2,949 <0.01% tick_size_change 2,948 <0.01% new_market 1,245 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,008,864 10,008,770 94 145 FULL book 118,952 118,950 2 11,998 FULL last_trade_price 43,241 43,241 0 0 FULL market_resolved 2,949 2,949 0 0 FULL new_market 1,245 1,245 0 0 FULL price_change 92,547,952 92,547,006 946 1,684 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,007,354 28,388 19ms 24ms 167ms 46.3s 0 transport_latency_assumed best_bid_ask i 10,007,226 27,557 21ms 26ms 86ms 2.3s 0 transport_latency_assumed best_bid_ask m 10,008,214 5,210,211 4ms 10ms 56ms 3.7s 0 transport_latency_assumed best_bid_ask n 9,989,564 2,210 44ms 56ms 228ms 14.3s 0 transport_latency_assumed best_bid_ask o 10,008,036 4,740,404 4ms 10ms 64ms 9.0s 0 transport_latency_assumed book h 93,782 6,868 22ms 277ms 17.4h 110.4d 0 book_staleness book i 92,036 5,143 23ms 241ms 8.9h 110.5d 0 book_staleness book m 93,481 51,302 6ms 65ms 9.5h 129.0d 0 book_staleness book n 94,466 10,425 48ms 6.2s 11.9h 110.5d 0 book_staleness book o 92,482 45,212 6ms 40ms 6.4h 110.4d 0 book_staleness last_trade_price h 43,103 203 20ms 60ms 567ms 9.4s 0 transport_latency_assumed last_trade_price i 43,029 175 23ms 80ms 894ms 2.3s 0 transport_latency_assumed last_trade_price m 43,173 22,692 5ms 16ms 200ms 1.2s 0 transport_latency_assumed last_trade_price n 41,489 25 47ms 222ms 6.9s 14.4s 0 transport_latency_assumed last_trade_price o 43,207 20,146 6ms 15ms 154ms 1.8s 0 transport_latency_assumed market_resolved h 2,728 105 20ms 101ms 52.3s 57.2s 0 transport_latency_assumed market_resolved i 2,728 424 23ms 23.6s 52.2s 54.0s 0 transport_latency_assumed market_resolved m 2,728 1,182 5ms 19.8s 48.3s 56.5s 0 transport_latency_assumed market_resolved n 2,728 22 45ms 209ms 49.2s 56.4s 0 transport_latency_assumed market_resolved o 2,728 1,216 5ms 25.1s 52.5s 57.2s 0 transport_latency_assumed new_market h 758 116 136ms 24.3s 58.3s 1.3min 0 transport_latency_assumed new_market i 758 176 99ms 24.6s 1.0min 1.4min 0 transport_latency_assumed new_market m 758 471 40ms 22.0s 31.9s 1.6min 0 transport_latency_assumed new_market n 758 99 182ms 21.0s 37.8s 1.6min 0 transport_latency_assumed new_market o 758 383 53ms 23.2s 58.1s 1.6min 0 transport_latency_assumed price_change h 92,416,941 364,984 19ms 27ms 299ms 46.5s 0 transport_latency_assumed price_change i 92,401,656 336,832 21ms 30ms 270ms 2.3s 0 transport_latency_assumed price_change m 92,456,030 47,747,696 4ms 11ms 93ms 6.2s 0 transport_latency_assumed price_change n 91,851,776 68,837 44ms 70ms 1.3s 14.5s 0 transport_latency_assumed price_change o 92,455,613 44,028,657 4ms 11ms 103ms 13.6s 0 transport_latency_assumed tick_size_change h 2,948 not meas. 19ms 25ms 496ms 3.9s 0 transport_latency_assumed tick_size_change i 2,948 not meas. 21ms 28ms 259ms 508ms 0 transport_latency_assumed tick_size_change m 2,948 1,601 4ms 8ms 35ms 148ms 0 transport_latency_assumed tick_size_change n 2,948 not meas. 44ms 64ms 972ms 994ms 0 transport_latency_assumed tick_size_change o 2,948 1,347 5ms 10ms 247ms 675ms 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-05/21/2026-10-05T21.parquet sha256sum 2026-10-05T21.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.