Hour audit: 2026-10-09T07
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-09T07 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-10-09T07:00:00.000142254+00:00 · last event 2026-10-09T07:59:59.999987114+00:00
VOLUME 112,278,871 rows · 1,267,380,032 bytes (1.18 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured m: 112,158,376 · o: 112,139,693 · h: 112,120,330 · i: 112,054,923 · n: 111,989,195 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 54,506,941 (48.55%) · o: 56,162,334 (50.02%) · h: 854,762 (0.76%) · i: 695,949 (0.62%) · n: 58,885 (0.05%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 112,278,871 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 62f1638fd25432e77c7573d3983ece8665cdcbdee5babcd0eb47554023556336
no line in the corpus checksum ledger names this file
joined 112,288,611 to merged 112,278,871, minus 9,740 (minus 0.0087%)
boundary drops 9,740 · 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-10T00:23:42Z 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 11,716,694 146,176,707 0-44 7884d845e26634d7a3a7ce9930126919092dcdbc4031f4aaef090ac40240ba5e book 189,166 20,615,024 45-45 fa6464e919af7601dd3d64dc933b58f932b3beab7c6de1c652fbba1a8fa100af last_trade_price 50,345 2,944,544 46-46 01d3eb7ff17befb58f03a3d29363ab68e960374b3ae95d5cabe624b83eacb2d4 market_resolved 379 61,722 47-47 66e22e76af0b4766a9e056f843eaa782b861d915b24bcc0b73069f0f77a7c00f new_market 1,241 116,201 48-48 3083dd9a06df421424e836324ebfe0da6d88176a4e88113dab4a37af219bcbd2 price_change 100,318,206 1,096,081,378 49-431 abd59a732a4ba8dc3e8983b43077f17cc532bd933584cb1e34e594c727c7d273 tick_size_change 2,840 105,453 432-432 d8e3c7a3d0393a9fbdc144eca04ba8f19c6f904f4e49d1649f3896b9507ea887 EVENT MIX count share price_change 100,318,206 89.35% best_bid_ask 11,716,694 10.44% book 189,166 0.17% last_trade_price 50,345 0.04% tick_size_change 2,840 <0.01% new_market 1,241 <0.01% market_resolved 379 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,717,919 11,716,694 1,225 97 FULL book 189,297 189,166 131 36,031 FULL last_trade_price 50,357 50,345 12 2 FULL market_resolved 379 379 0 0 FULL new_market 1,241 1,241 0 0 FULL price_change 100,326,578 100,318,206 8,372 246 FULL tick_size_change 2,840 2,840 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 11,714,626 77,477 19ms 37ms 411ms 1.7min 0 transport_latency_assumed best_bid_ask i 11,711,902 63,852 21ms 31ms 145ms 4.4s 0 transport_latency_assumed best_bid_ask m 11,715,914 5,728,232 5ms 15ms 97ms 5.2s 0 transport_latency_assumed best_bid_ask n 11,713,666 4,124 44ms 61ms 268ms 23.8s 0 transport_latency_assumed best_bid_ask o 11,715,512 5,843,009 5ms 15ms 106ms 16.8s 0 transport_latency_assumed book h 127,750 27,015 31ms 33.6min 29.9d 113.9d 0 book_staleness book i 130,732 30,265 32ms 1.2h 29.9d 113.9d 0 book_staleness book m 113,618 59,661 7ms 6.0s 1.1d 132.4d 0 book_staleness book n 108,146 7,672 50ms 3.7s 1.1d 113.8d 0 book_staleness book o 114,370 64,553 7ms 24.1s 2.0d 113.9d 0 book_staleness last_trade_price h 50,072 426 22ms 131ms 729ms 54.2s 0 transport_latency_assumed last_trade_price i 49,883 267 25ms 278ms 1.6s 4.0s 0 transport_latency_assumed last_trade_price m 50,244 23,382 6ms 28ms 194ms 2.6s 0 transport_latency_assumed last_trade_price n 49,659 31 50ms 766ms 5.7s 22.7s 0 transport_latency_assumed last_trade_price o 50,115 26,239 6ms 27ms 245ms 5.6s 0 transport_latency_assumed market_resolved h 367 13 37ms 123ms 33.2s 38.4s 0 transport_latency_assumed market_resolved i 367 1 44ms 143ms 49.5s 51.9s 0 transport_latency_assumed market_resolved m 367 202 5ms 30ms 49.4s 51.8s 0 transport_latency_assumed market_resolved n 367 1 68ms 244ms 34.8s 39.6s 0 transport_latency_assumed market_resolved o 367 162 6ms 99ms 52.4s 54.9s 0 transport_latency_assumed new_market h 747 145 241ms 14.9s 42.1s 1.7min 0 transport_latency_assumed new_market i 747 242 133ms 33.9s 37.6s 1.6min 0 transport_latency_assumed new_market m 747 426 101ms 16.6s 44.5s 1.7min 0 transport_latency_assumed new_market n 747 127 231ms 18.4s 36.1s 1.3min 0 transport_latency_assumed new_market o 747 301 91ms 34.3s 37.9s 1.4min 0 transport_latency_assumed price_change h 100,223,928 749,674 19ms 45ms 583ms 1.8min 0 transport_latency_assumed price_change i 100,158,452 601,322 21ms 41ms 433ms 4.5s 0 transport_latency_assumed price_change m 100,274,646 48,693,708 5ms 17ms 119ms 5.7s 0 transport_latency_assumed price_change n 100,113,770 46,930 45ms 80ms 1.6s 24.2s 0 transport_latency_assumed price_change o 100,255,742 50,226,572 5ms 17ms 131ms 20.2s 0 transport_latency_assumed tick_size_change h 2,840 12 19ms 35ms 89ms 252ms 0 transport_latency_assumed tick_size_change i 2,840 not meas. 21ms 35ms 102ms 311ms 0 transport_latency_assumed tick_size_change m 2,840 1,330 5ms 16ms 69ms 158ms 0 transport_latency_assumed tick_size_change n 2,840 not meas. 44ms 62ms 154ms 562ms 0 transport_latency_assumed tick_size_change o 2,840 1,498 5ms 13ms 52ms 236ms 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/07/2026-10-09T07.parquet sha256sum 2026-10-09T07.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.