Hour audit: 2026-10-09T17
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-09T17 · corpus v3 · verdict AUDIT PENDING
COVERAGE not measured (this hour is not in the corpus attestation, so we have not looked at it)
VOLUME 138,291,470 rows · 1,629,978,122 bytes (1.52 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured m: 137,605,086 · h: 137,308,705 · n: 137,307,102 · i: 137,005,076 · o: 131,732,423 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 69,959,231 (50.59%) · h: 1,443,957 (1.04%) · n: 259,260 (0.19%) · i: 1,469,105 (1.06%) · o: 65,159,917 (47.12%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 65ce2ef9a1f7318a018bc9068f8c8321fe4722745d78d001ccf230b73e535529
no line in the corpus checksum ledger names this file
joined 138,304,389 to merged 138,291,470, minus 12,919 (minus 0.0093%)
boundary drops 12,919 · 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-10T05:56:21Z 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,494,152 159,952,949 0-47 c210956162acd9e4a9717c80fd4c07b722c2f7aef428aa5cdc6cafde49221299 book 758,545 77,874,524 48-50 559ec75d8a52c39044bd8625a03f3728bf6c83ba78df1064e6a9fffaec734920 last_trade_price 68,353 3,986,847 51-51 57d717030f330d580a032492d6a5785af3ce3096b3284738b06fb3dd8704983d market_resolved 1,124 171,134 52-52 f4e4dbf56b1845b8ff1ac594cc2ac3b47a030d109f0a09d034721d4011107a9a new_market 4,154 370,173 53-53 0ef0ab3e52da2d3165079b3d41e8a295a974e8bf31f2a6c28c0d6255411dc179 price_change 124,959,890 1,385,857,329 54-530 cd77ecbfa09c3cf30ccbf5a99a6c2016a9447aef3a2e65e6e116acfc8125c12a tick_size_change 5,252 194,206 531-531 2f70f89abc08ec9c563fe9a104b6ede8e49105b97bdb1067c381524356bae726 EVENT MIX count share price_change 124,959,890 90.36% best_bid_ask 12,494,152 9.03% book 758,545 0.55% last_trade_price 68,353 0.05% tick_size_change 5,252 <0.01% new_market 4,154 <0.01% market_resolved 1,124 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,495,285 12,494,152 1,133 501 FULL book 758,756 758,545 211 277,060 FULL last_trade_price 68,370 68,353 17 103 FULL market_resolved 1,124 1,124 0 25 FULL new_market 4,154 4,154 0 0 FULL price_change 124,971,448 124,959,890 11,558 2,115 FULL tick_size_change 5,252 5,252 0 56 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 12,484,066 124,057 19ms 42ms 1.3s 2.5min 0 transport_latency_assumed best_bid_ask i 12,478,310 125,395 22ms 41ms 342ms 9.6s 0 transport_latency_assumed best_bid_ask m 12,493,690 6,446,804 6ms 19ms 242ms 14.4s 0 transport_latency_assumed best_bid_ask n 12,489,934 18,397 45ms 72ms 533ms 36.6s 0 transport_latency_assumed best_bid_ask o 11,927,402 5,779,499 6ms 20ms 268ms 24.8s 0 transport_latency_assumed book h 157,470 16,820 28ms 44.7s 1.6d 132.8d 0 book_staleness book i 152,728 16,771 33ms 5.1s 1.5d 114.3d 0 book_staleness book m 154,144 84,507 8ms 2.6s 1.6d 114.3d 0 book_staleness book n 157,701 17,927 56ms 1.1min 1.6d 114.3d 0 book_staleness book o 716,248 622,520 7.6min 1.6d 48.2d 132.8d 0 book_staleness last_trade_price h 67,473 587 21ms 340ms 3.9s 49.2s 0 transport_latency_assumed last_trade_price i 66,948 665 29ms 299ms 3.0s 9.6s 0 transport_latency_assumed last_trade_price m 68,322 35,322 7ms 25ms 221ms 6.6s 0 transport_latency_assumed last_trade_price n 67,317 132 50ms 959ms 10.2s 36.8s 0 transport_latency_assumed last_trade_price o 64,803 31,647 7ms 26ms 259ms 24.8s 0 transport_latency_assumed market_resolved h 1,052 8 22ms 382ms 51.8s 1.4min 0 transport_latency_assumed market_resolved i 1,053 129 26ms 21.9s 52.2s 57.0s 0 transport_latency_assumed market_resolved m 1,053 476 6ms 151ms 48.0s 51.8s 0 transport_latency_assumed market_resolved n 1,053 3 48ms 356ms 51.2s 56.5s 0 transport_latency_assumed market_resolved o 1,032 508 6ms 65ms 4.3min 7.2min 0 transport_latency_assumed new_market h 2,353 402 216ms 1.4min 1.1h 1.1h 0 transport_latency_assumed new_market i 2,353 699 148ms 1.4min 58.1min 1.1h 0 transport_latency_assumed new_market m 2,353 1,593 52ms 1.4min 2.3min 1.0h 0 transport_latency_assumed new_market n 2,353 545 258ms 1.4min 2.4min 58.6min 0 transport_latency_assumed new_market o 2,676 915 183ms 6.7min 7.5min 58.6min 0 transport_latency_assumed price_change h 124,591,039 1,302,067 19ms 67ms 2.1s 2.5min 0 transport_latency_assumed price_change i 124,298,432 1,325,418 22ms 57ms 1.4s 9.6s 0 transport_latency_assumed price_change m 124,880,272 63,387,849 6ms 21ms 292ms 14.6s 0 transport_latency_assumed price_change n 124,583,492 222,252 46ms 116ms 2.5s 36.8s 0 transport_latency_assumed price_change o 119,015,234 58,722,304 6ms 23ms 342ms 26.7s 0 transport_latency_assumed tick_size_change h 5,252 16 18ms 31ms 361ms 24.4s 0 transport_latency_assumed tick_size_change i 5,252 28 21ms 38ms 104ms 268ms 0 transport_latency_assumed tick_size_change m 5,252 2,680 5ms 12ms 147ms 5.1s 0 transport_latency_assumed tick_size_change n 5,252 4 45ms 58ms 268ms 561ms 0 transport_latency_assumed tick_size_change o 5,028 2,524 5ms 12ms 70ms 3.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/17/2026-10-09T17.parquet sha256sum 2026-10-09T17.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.