Hour audit: 2026-10-09T12
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-09T12 · corpus v3 · verdict AUDIT PENDING
COVERAGE not measured (this hour is not in the corpus attestation, so we have not looked at it)
VOLUME 128,509,955 rows · 1,556,129,444 bytes (1.45 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured h: 127,699,432 · i: 127,696,852 · o: 127,639,700 · m: 127,629,977 · n: 127,099,924 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 1,956,430 (1.52%) · i: 1,361,720 (1.06%) · o: 60,156,968 (46.81%) · m: 64,751,592 (50.39%) · n: 283,245 (0.22%) (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 128,509,955 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 a1e1b0a5aca2a481b12cc81f5c6e02e6d86a89da4f2f9bab4c8a269924ae522e
no line in the corpus checksum ledger names this file
joined 128,511,725 to merged 128,509,955, minus 1,770 (minus 0.0014%)
boundary drops 1,770 · 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-10T03:06:29Z 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,652,218 162,158,812 0-48 bd2c16a9b07a2ef5ec39f6eb579e28b450565f331041e69e72d5cae262a0dc27 book 1,282,447 96,718,276 49-53 9ab3ff6ee27727cffd198fa037f7d67a7d4581e2feebad6f94384886ae0a963f last_trade_price 54,571 3,271,183 54-54 186a86eeba4e003eabba52066386d164ac2fe39a56d951190552cbacadf480a6 market_resolved 1,232 201,120 55-55 aa913b67371d3609b75fc614a09a410e5a044a549885722f443f7a9d4abc3611 new_market 931 94,594 56-56 d35859346c3aca082d4b668a1ec6b3ca12b08cd08ec1908b004e6692ecf43730 price_change 114,514,584 1,292,079,312 57-493 59457e5540b9d56f086b1d874581ced196e044f1cebd9e3adb6691aa95a1e0c2 tick_size_change 3,972 143,949 494-494 7e1a52e8f099dc98d5086c7eff1fcbfc96f1f2526db65d17b552e9bb16a51426 EVENT MIX count share price_change 114,514,584 89.11% best_bid_ask 12,652,218 9.85% book 1,282,447 1.00% last_trade_price 54,571 0.04% tick_size_change 3,972 <0.01% market_resolved 1,232 <0.01% new_market 931 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,652,384 12,652,218 166 63 FULL book 1,282,453 1,282,447 6 219,965 FULL last_trade_price 54,571 54,571 0 1 FULL market_resolved 1,232 1,232 0 1 FULL new_market 931 931 0 0 FULL price_change 114,516,182 114,514,584 1,598 297 FULL tick_size_change 3,972 3,972 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 12,647,055 151,892 19ms 38ms 268ms 1.0min 0 transport_latency_assumed best_bid_ask i 12,648,203 101,685 21ms 39ms 183ms 15.8s 0 transport_latency_assumed best_bid_ask m 12,649,685 6,398,039 6ms 21ms 124ms 4.6s 0 transport_latency_assumed best_bid_ask n 12,643,849 5,121 45ms 71ms 361ms 20.0s 0 transport_latency_assumed best_bid_ask o 12,648,806 5,995,481 6ms 21ms 130ms 10.0s 0 transport_latency_assumed book h 591,949 267,272 8.5min 1.4d 47.9d 132.6d 0 book_staleness book i 618,438 291,663 8.5min 1.4d 48.0d 132.6d 0 book_staleness book m 497,409 240,274 6.3min 1.4d 47.9d 132.6d 0 book_staleness book n 507,258 216,423 6.8min 1.4d 47.9d 132.6d 0 book_staleness book o 533,592 266,815 6.8min 1.4d 47.9d 132.6d 0 book_staleness last_trade_price h 54,367 731 22ms 164ms 956ms 23.1s 0 transport_latency_assumed last_trade_price i 54,305 325 28ms 413ms 2.8s 7.7s 0 transport_latency_assumed last_trade_price m 54,417 27,755 7ms 35ms 217ms 1.8s 0 transport_latency_assumed last_trade_price n 52,883 49 59ms 1.7s 13.4s 20.0s 0 transport_latency_assumed last_trade_price o 54,352 25,711 7ms 39ms 241ms 4.4s 0 transport_latency_assumed market_resolved h 1,201 24 22ms 87ms 32.2s 57.0s 0 transport_latency_assumed market_resolved i 1,202 74 25ms 126ms 42.5s 53.1s 0 transport_latency_assumed market_resolved m 1,202 617 6ms 40ms 45.0s 55.7s 0 transport_latency_assumed market_resolved n 1,202 13 49ms 210ms 42.7s 1.9min 0 transport_latency_assumed market_resolved o 1,202 504 6ms 54ms 49.5s 54.7s 0 transport_latency_assumed new_market h 600 83 190ms 17.2s 36.8s 1.3min 0 transport_latency_assumed new_market i 600 124 120ms 17.7s 37.7s 1.7min 0 transport_latency_assumed new_market m 600 339 61ms 11.7s 19.4s 1.5min 0 transport_latency_assumed new_market n 600 67 217ms 17.1s 39.0s 1.7min 0 transport_latency_assumed new_market o 600 318 58ms 11.1s 37.9s 1.5min 0 transport_latency_assumed price_change h 114,400,288 1,536,424 19ms 51ms 473ms 1.0min 0 transport_latency_assumed price_change i 114,370,132 967,826 22ms 60ms 834ms 17.1s 0 transport_latency_assumed price_change m 114,422,692 58,082,448 6ms 25ms 154ms 4.8s 0 transport_latency_assumed price_change n 113,890,160 61,572 46ms 126ms 4.2s 20.0s 0 transport_latency_assumed price_change o 114,397,176 53,866,314 6ms 25ms 160ms 10.0s 0 transport_latency_assumed tick_size_change h 3,972 4 19ms 35ms 95ms 2.2s 0 transport_latency_assumed tick_size_change i 3,972 23 21ms 34ms 110ms 209ms 0 transport_latency_assumed tick_size_change m 3,972 2,120 6ms 16ms 68ms 236ms 0 transport_latency_assumed tick_size_change n 3,972 not meas. 45ms 73ms 711ms 927ms 0 transport_latency_assumed tick_size_change o 3,972 1,825 6ms 16ms 47ms 114ms 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/12/2026-10-09T12.parquet sha256sum 2026-10-09T12.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.