Hour audit: 2026-10-10T02
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-10T02 · corpus v3 · verdict AUDIT PENDING
COVERAGE not measured (this hour is not in the corpus attestation, so we have not looked at it)
VOLUME 133,475,315 rows · 1,553,942,820 bytes (1.45 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured h: 132,678,487 · m: 132,672,402 · n: 132,577,654 · i: 132,501,822 · o: 126,945,989 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 852,647 (0.64%) · m: 66,713,826 (49.98%) · n: 119,789 (0.09%) · i: 514,208 (0.39%) · o: 65,274,845 (48.90%) (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 133,475,315 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 216039641d671476665f5563f08420f6ee9b25c2bff717025849469f5de64427
no line in the corpus checksum ledger names this file
joined 133,492,744 to merged 133,475,315, minus 17,429 (minus 0.0131%)
boundary drops 17,429 · 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-10T10:48:01Z 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,556,206 157,309,148 0-47 bcfbde404fae3f53e083b359fc24340191472d2d52f6ab4c7323be20d68f4da5 book 1,047,547 88,273,745 48-51 abebfe05c94e516531c36bb33e1e50df90a30b38163c12a39501fadb933db6a1 last_trade_price 46,418 2,697,471 52-52 364c7a2e8a5772d608f4d485b6f499c7ea98c33e0a1299f07d5680d85f7ecb50 market_resolved 705 104,065 53-53 9aa8fc119f76de59b821eadfeed9d6f37a1636d6886ba3c9dc68b38dcc42812c new_market 1,101 102,745 54-54 1f8babe2e420a983188ea63733127f315b650f585bc72eeae69b84dc8d7c5a81 price_change 119,818,438 1,303,756,788 55-512 ffb53b59de87f97093903fc7d8c0315c6c9b8ae83f9d35e83e213e0f8a53f8af tick_size_change 4,900 181,170 513-513 a112825360438b4ac8aabde9dd24b90ae4c9a8e4e23ed1c3bf955eb00ee98ace EVENT MIX count share price_change 119,818,438 89.77% best_bid_ask 12,556,206 9.41% book 1,047,547 0.78% last_trade_price 46,418 0.03% tick_size_change 4,900 <0.01% new_market 1,101 <0.01% market_resolved 705 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,557,487 12,556,206 1,281 678 FULL book 1,048,705 1,047,547 1,158 269,772 FULL last_trade_price 46,420 46,418 2 73 FULL market_resolved 705 705 0 5 FULL new_market 1,101 1,101 0 0 FULL price_change 119,833,426 119,818,438 14,988 1,156 FULL tick_size_change 4,900 4,900 0 30 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 12,555,538 62,880 17ms 25ms 178ms 57.7s 0 transport_latency_assumed best_bid_ask i 12,554,738 40,316 20ms 34ms 82ms 2.3s 0 transport_latency_assumed best_bid_ask m 12,554,800 6,240,908 4ms 11ms 63ms 14.8s 0 transport_latency_assumed best_bid_ask n 12,554,604 4,348 44ms 54ms 148ms 5.3s 0 transport_latency_assumed best_bid_ask o 11,957,346 6,207,754 4ms 10ms 66ms 6.3s 0 transport_latency_assumed book h 295,244 110,284 1.8min 1.2d 48.5d 133.2d 0 book_staleness book i 192,959 52,009 3.0s 14.7h 39.4d 133.2d 0 book_staleness book m 321,200 171,662 2.3min 1.3d 48.5d 133.2d 0 book_staleness book n 229,239 73,136 35.1s 18.7h 45.3d 133.2d 0 book_staleness book o 740,602 640,456 8.8min 1.9d 48.5d 133.2d 0 book_staleness last_trade_price h 46,370 476 19ms 32ms 266ms 53.7s 0 transport_latency_assumed last_trade_price i 46,274 258 23ms 41ms 194ms 2.0s 0 transport_latency_assumed last_trade_price m 46,317 23,915 5ms 13ms 124ms 4.2s 0 transport_latency_assumed last_trade_price n 46,372 13 46ms 101ms 569ms 5.3s 0 transport_latency_assumed last_trade_price o 44,674 21,756 5ms 14ms 123ms 1.5s 0 transport_latency_assumed market_resolved h 635 7 28ms 88ms 45.8s 45.9s 0 transport_latency_assumed market_resolved i 635 95 40ms 35.5s 56.5s 56.8s 0 transport_latency_assumed market_resolved m 635 296 5ms 36.0s 57.0s 57.0s 0 transport_latency_assumed market_resolved n 635 2 77ms 235ms 47.0s 1.6min 0 transport_latency_assumed market_resolved o 636 305 5ms 37.5s 5.8min 6.3min 0 transport_latency_assumed new_market h 666 144 185ms 54.5s 1.9min 2.2min 0 transport_latency_assumed new_market i 666 268 82ms 57.2s 1.8min 1.9min 0 transport_latency_assumed new_market m 666 308 91ms 1.0min 2.0min 2.2min 0 transport_latency_assumed new_market n 666 74 135ms 58.7s 2.0min 2.2min 0 transport_latency_assumed new_market o 685 307 80ms 1.3min 6.2min 7.4min 0 transport_latency_assumed price_change h 119,775,134 678,842 18ms 26ms 219ms 1.7min 0 transport_latency_assumed price_change i 119,701,650 421,258 21ms 38ms 113ms 2.4s 0 transport_latency_assumed price_change m 119,743,884 60,274,382 5ms 11ms 71ms 14.8s 0 transport_latency_assumed price_change n 119,741,238 42,216 44ms 58ms 224ms 5.7s 0 transport_latency_assumed price_change o 114,197,266 58,401,740 4ms 11ms 74ms 6.7s 0 transport_latency_assumed tick_size_change h 4,900 14 17ms 22ms 46ms 3.2s 0 transport_latency_assumed tick_size_change i 4,900 4 20ms 31ms 50ms 79ms 0 transport_latency_assumed tick_size_change m 4,900 2,355 4ms 9ms 30ms 137ms 0 transport_latency_assumed tick_size_change n 4,900 not meas. 44ms 52ms 333ms 694ms 0 transport_latency_assumed tick_size_change o 4,780 2,527 4ms 8ms 29ms 129ms 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-10/02/2026-10-10T02.parquet sha256sum 2026-10-10T02.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.