Hour audit: 2026-10-09T11
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-09T11 · corpus v3 · verdict AUDIT PENDING
COVERAGE not measured (this hour is not in the corpus attestation, so we have not looked at it)
VOLUME 121,590,650 rows · 1,428,705,719 bytes (1.33 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured i: 121,459,243 · m: 121,239,012 · o: 121,170,732 · h: 121,165,860 · n: 121,111,322 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 955,495 (0.79%) · m: 59,599,995 (49.02%) · o: 59,692,789 (49.09%) · h: 1,275,455 (1.05%) · n: 66,916 (0.06%) (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 121,590,650 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 895e23e2bf67b60bdbe3713824770309cf31ac7b108051a6ce4b27731c3f2ece
no line in the corpus checksum ledger names this file
joined 121,592,188 to merged 121,590,650, minus 1,538 (minus 0.0013%)
boundary drops 1,538 · 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-10T02:30:47Z 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,360,076 158,078,734 0-47 fe2d57d20eb8a513250a3c9db78468a3055b04ea331f997e140cfadbc3192aab book 429,461 44,982,150 48-49 edb11ef7d03bf72f477fb326144ebeb9b9a8a1165d8001e813ba1587c89d8b19 last_trade_price 56,274 3,319,856 50-50 71779ab72a783f1d53293da8e27076089158671edf00e09b7e517a63339e2f82 market_resolved 1,119 175,905 51-51 1854e3f63dab8ff4aa0009d37b27d24568ad0d8460aaf3775b256a369924aa58 new_market 912 93,643 52-52 08def91c8f8c749ebbe3af768d349e2a50b5d034f061527dbea882b7e4ce0f3a price_change 108,739,196 1,220,537,844 53-467 9c7e931f661fdc1de161729bb91d0d330f866e0edc6837be674b1a895a46e34c tick_size_change 3,612 132,072 468-468 8d8f868c71d88288fbff2393c036f0d1699755c5dbd4b24bc04d76d60851fff5 EVENT MIX count share price_change 108,739,196 89.43% best_bid_ask 12,360,076 10.17% book 429,461 0.35% last_trade_price 56,274 0.05% tick_size_change 3,612 <0.01% market_resolved 1,119 <0.01% new_market 912 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,360,172 12,360,076 96 63 FULL book 429,863 429,461 402 140,729 FULL last_trade_price 56,274 56,274 0 0 FULL market_resolved 1,119 1,119 0 0 FULL new_market 912 912 0 0 FULL price_change 108,740,236 108,739,196 1,040 336 FULL tick_size_change 3,612 3,612 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 12,358,317 116,188 18ms 33ms 186ms 48.0s 0 transport_latency_assumed best_bid_ask i 12,357,367 64,349 22ms 35ms 147ms 8.5s 0 transport_latency_assumed best_bid_ask m 12,359,546 6,089,470 5ms 17ms 94ms 3.5s 0 transport_latency_assumed best_bid_ask n 12,358,137 3,415 44ms 63ms 252ms 14.0s 0 transport_latency_assumed best_bid_ask o 12,358,027 6,086,654 5ms 17ms 97ms 5.4s 0 transport_latency_assumed book h 118,332 5,959 23ms 171ms 9.1h 114.0d 0 book_staleness book i 395,716 277,371 3.4min 1.3d 47.9d 132.5d 0 book_staleness book m 119,436 60,037 7ms 58ms 15.9h 114.0d 0 book_staleness book n 138,491 22,243 61ms 14.9min 18.8d 132.5d 0 book_staleness book o 120,414 63,851 7ms 71ms 21.0h 114.0d 0 book_staleness last_trade_price h 55,998 689 21ms 84ms 463ms 24.8s 0 transport_latency_assumed last_trade_price i 56,045 270 26ms 282ms 2.9s 7.2s 0 transport_latency_assumed last_trade_price m 56,197 27,130 7ms 27ms 171ms 1.6s 0 transport_latency_assumed last_trade_price n 55,999 22 52ms 1.0s 7.8s 14.0s 0 transport_latency_assumed last_trade_price o 56,010 28,163 7ms 26ms 172ms 2.0s 0 transport_latency_assumed market_resolved h 1,081 8 21ms 22.0s 52.0s 52.2s 0 transport_latency_assumed market_resolved i 1,081 150 25ms 21.2s 52.1s 57.5s 0 transport_latency_assumed market_resolved m 1,081 476 5ms 10.6s 40.7s 54.5s 0 transport_latency_assumed market_resolved n 1,081 16 47ms 427ms 53.4s 55.3s 0 transport_latency_assumed market_resolved o 1,081 469 6ms 16.0s 46.1s 46.2s 0 transport_latency_assumed new_market h 606 75 149ms 35.2s 1.2min 1.5min 0 transport_latency_assumed new_market i 606 117 104ms 34.9s 1.2min 1.5min 0 transport_latency_assumed new_market m 606 295 65ms 28.8s 1.2min 1.6min 0 transport_latency_assumed new_market n 606 40 173ms 35.3s 1.2min 1.4min 0 transport_latency_assumed new_market o 606 385 53ms 30.0s 1.3min 1.7min 0 transport_latency_assumed price_change h 108,627,914 1,152,508 19ms 41ms 271ms 50.5s 0 transport_latency_assumed price_change i 108,644,816 613,210 22ms 49ms 743ms 8.5s 0 transport_latency_assumed price_change m 108,698,534 53,420,762 5ms 20ms 114ms 3.8s 0 transport_latency_assumed price_change n 108,553,396 41,180 45ms 95ms 2.7s 14.1s 0 transport_latency_assumed price_change o 108,630,982 53,511,536 5ms 20ms 118ms 5.7s 0 transport_latency_assumed tick_size_change h 3,612 28 19ms 38ms 151ms 30.4s 0 transport_latency_assumed tick_size_change i 3,612 28 22ms 48ms 129ms 1.5s 0 transport_latency_assumed tick_size_change m 3,612 1,825 6ms 29ms 126ms 257ms 0 transport_latency_assumed tick_size_change n 3,612 not meas. 45ms 69ms 201ms 2.6s 0 transport_latency_assumed tick_size_change o 3,612 1,731 6ms 22ms 112ms 237ms 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/11/2026-10-09T11.parquet sha256sum 2026-10-09T11.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.