Hour audit: 2026-10-09T02
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-09T02 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-10-09T02:00:00.000004302+00:00 · last event 2026-10-09T02:59:59.999888681+00:00
VOLUME 131,320,740 rows · 1,503,306,048 bytes (1.40 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured m: 131,233,349 · o: 131,207,822 · h: 131,201,373 · n: 131,181,153 · i: 131,135,046 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 65,468,299 (49.85%) · o: 63,247,762 (48.16%) · h: 1,583,764 (1.21%) · n: 94,368 (0.07%) · i: 926,547 (0.71%) (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 131,320,740 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 275819eb7e6f86bcbdb12f67d618c250c1dd3df203c3a48182baf23ca67468f5
no line in the corpus checksum ledger names this file
joined 131,322,717 to merged 131,320,740, minus 1,977 (minus 0.0015%)
boundary drops 1,977 · 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-09T21:52:25Z 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 13,589,506 169,317,920 0-51 ef2295099a508bbea5fd1ac9d876ece22637cea0f21ffdc8b9995a382ff0193e book 153,845 17,271,835 52-52 33a6c38f022ac4ed111c7b235f38d1c5dbc975829911e06fa4a1c7deb3025ce4 last_trade_price 52,577 2,992,644 53-53 bbbf654644660c1a24a808ed1dd5f86a841bc3ddd1afa3ee62d52969ae3bc34f market_resolved 1,287 194,270 54-54 296433c27d25d9efe33d6587f84c64505c677c17a2f0d490fcd403c461bb40f3 new_market 445 48,870 55-55 31df68e4c3df7c1b395913bc2f08a9579e3012bbbcb7b83d56d4f3c30518322a price_change 117,518,996 1,311,835,112 56-504 aa0c3bb636c8eda5bf0a9dd39bc4cbd18b4d18f5b90627ac2f325562e47e0057 tick_size_change 4,084 150,771 505-505 411fea06e272bf33956e153aecf461e5bfdc430a6d3692a73c95ca1461db4b1a EVENT MIX count share price_change 117,518,996 89.49% best_bid_ask 13,589,506 10.35% book 153,845 0.12% last_trade_price 52,577 0.04% tick_size_change 4,084 <0.01% market_resolved 1,287 <0.01% new_market 445 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,589,681 13,589,506 175 67 FULL book 153,859 153,845 14 19,889 FULL last_trade_price 52,577 52,577 0 1 FULL market_resolved 1,287 1,287 0 0 FULL new_market 445 445 0 0 FULL price_change 117,520,784 117,518,996 1,788 184 FULL tick_size_change 4,084 4,084 0 2 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 13,586,750 139,484 18ms 32ms 156ms 22.6s 0 transport_latency_assumed best_bid_ask i 13,585,933 79,944 21ms 34ms 143ms 4.4s 0 transport_latency_assumed best_bid_ask m 13,588,971 6,865,293 5ms 17ms 106ms 4.1s 0 transport_latency_assumed best_bid_ask n 13,587,929 6,104 45ms 63ms 214ms 9.4s 0 transport_latency_assumed best_bid_ask o 13,588,962 6,498,681 5ms 17ms 105ms 4.3s 0 transport_latency_assumed book h 133,316 29,886 25ms 27.6min 26.5d 113.7d 0 book_staleness book i 111,514 7,367 24ms 464ms 8.6h 113.6d 0 book_staleness book m 107,493 52,063 7ms 40ms 17.0min 113.6d 0 book_staleness book n 113,664 8,730 49ms 1.9s 22.2h 113.7d 0 book_staleness book o 108,466 55,799 7ms 40ms 1.7h 113.7d 0 book_staleness last_trade_price h 52,283 830 21ms 65ms 313ms 7.2s 0 transport_latency_assumed last_trade_price i 52,171 395 23ms 163ms 1.4s 2.8s 0 transport_latency_assumed last_trade_price m 52,477 24,314 6ms 30ms 174ms 1.4s 0 transport_latency_assumed last_trade_price n 52,326 23 48ms 295ms 3.6s 8.4s 0 transport_latency_assumed last_trade_price o 52,470 27,015 6ms 26ms 167ms 2.0s 0 transport_latency_assumed market_resolved h 1,199 67 19ms 106ms 50.4s 55.8s 0 transport_latency_assumed market_resolved i 1,199 160 22ms 28.7s 56.3s 58.0s 0 transport_latency_assumed market_resolved m 1,199 553 5ms 29.0s 53.2s 58.2s 0 transport_latency_assumed market_resolved n 1,199 3 46ms 198ms 51.2s 56.6s 0 transport_latency_assumed market_resolved o 1,199 504 5ms 15.1s 55.7s 55.8s 0 transport_latency_assumed new_market h 297 47 56ms 8.0s 1.5min 1.6min 0 transport_latency_assumed new_market i 297 59 41ms 8.6s 13.8s 1.7min 0 transport_latency_assumed new_market m 297 173 32ms 10.9s 1.4min 1.9min 0 transport_latency_assumed new_market n 297 36 84ms 8.2s 1.3min 1.5min 0 transport_latency_assumed new_market o 297 130 36ms 277ms 17.7s 1.4min 0 transport_latency_assumed price_change h 117,423,444 1,413,352 18ms 37ms 254ms 22.6s 0 transport_latency_assumed price_change i 117,379,856 838,562 21ms 40ms 370ms 7.1s 0 transport_latency_assumed price_change m 117,478,828 58,523,726 5ms 20ms 140ms 4.8s 0 transport_latency_assumed price_change n 117,421,654 79,472 45ms 74ms 808ms 9.5s 0 transport_latency_assumed price_change o 117,452,344 56,663,884 5ms 19ms 141ms 4.3s 0 transport_latency_assumed tick_size_change h 4,084 98 18ms 43ms 200ms 3.8s 0 transport_latency_assumed tick_size_change i 4,076 60 22ms 52ms 288ms 1.7s 0 transport_latency_assumed tick_size_change m 4,084 2,177 5ms 32ms 164ms 902ms 0 transport_latency_assumed tick_size_change n 4,084 not meas. 45ms 87ms 279ms 8.6s 0 transport_latency_assumed tick_size_change o 4,084 1,749 5ms 54ms 224ms 527ms 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/02/2026-10-09T02.parquet sha256sum 2026-10-09T02.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.