Hour audit: 2026-10-08T01
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 and the manifest disagree on this file's digest. The checksum ledger and this hour's manifest publish DIFFERENT digests for the same file. One of the two is wrong and the file should not be trusted until that is resolved.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-10-08T01 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-10-08T01:00:00.000037587+00:00 · last event 2026-10-08T01:59:59.999823241+00:00
VOLUME 136,567,749 rows · 1,543,000,865 bytes (1.44 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 136,490,492 · h: 136,468,382 · i: 136,381,061 · m: 136,376,888 · n: 136,346,395 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 65,841,407 (48.21%) · h: 1,548,931 (1.13%) · i: 1,058,531 (0.78%) · m: 68,066,908 (49.84%) · n: 51,972 (0.04%) (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 136,567,749 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 93d6b2e41724af046820d1fee48de6db504935d862333b6079f99a42d57225f6
the corpus checksum ledger names this file with a DIFFERENT digest
joined 136,569,059 to merged 136,567,749, minus 1,310 (minus 0.0010%)
boundary drops 1,310 · 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-09T11:08:18Z 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 and the manifest disagree on this file's digest
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 12,615,498 155,778,750 0-48 1a85a0927e54411f6a1702d0b6e9d97bfb045ff4e619154a0a665cd2fa33ee55 book 151,881 16,453,351 49-49 41078f79130d92d3263f998516ecddf22a39fb2d42835b69804818a0dc700246 last_trade_price 52,279 2,980,561 50-50 7251ad744c540a951b54d952bf82b6e5629f54e1fd9379dc0c4ba0743ffd4064 market_resolved 941 141,883 51-51 9fd52d88082feda69da543e54cc7c5969d4cc5b3c9a1194e23fff83c5e63c30b new_market 1,109 110,363 52-52 3f4ab9e82ee08fbf2ad9475e453dc9c61b0881c265a85d1e1522c4c0b0942fbf price_change 123,742,369 1,365,843,694 53-525 417cd30090490f788be63eed3da154b7f8a9f98d3f1fa464d2f1c8dcf58f5706 tick_size_change 3,672 135,669 526-526 0db6bd845eb64d01011d315201c42e749e328a4aae689d9bd491da0862be195a EVENT MIX count share price_change 123,742,369 90.61% best_bid_ask 12,615,498 9.24% book 151,881 0.11% last_trade_price 52,279 0.04% tick_size_change 3,672 <0.01% new_market 1,109 <0.01% market_resolved 941 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,615,617 12,615,498 119 125 FULL book 151,885 151,881 4 18,452 FULL last_trade_price 52,280 52,279 1 0 FULL market_resolved 941 941 0 0 FULL new_market 1,109 1,109 0 0 FULL price_change 123,743,555 123,742,369 1,186 104 FULL tick_size_change 3,672 3,672 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 12,614,220 127,660 18ms 33ms 188ms 45.1s 0 transport_latency_assumed best_bid_ask i 12,611,650 84,992 21ms 34ms 125ms 2.5s 0 transport_latency_assumed best_bid_ask m 12,612,552 6,293,082 5ms 17ms 102ms 5.8s 0 transport_latency_assumed best_bid_ask n 12,612,955 3,479 45ms 64ms 218ms 12.7s 0 transport_latency_assumed best_bid_ask o 12,614,623 6,106,285 5ms 18ms 101ms 7.6s 0 transport_latency_assumed book h 109,032 5,187 23ms 109ms 3.3h 112.6d 0 book_staleness book i 109,961 6,338 24ms 150ms 5.6h 112.6d 0 book_staleness book m 119,894 67,937 8ms 46.7s 3.9d 131.1d 0 book_staleness book n 110,969 6,424 51ms 1.5s 15.0h 131.1d 0 book_staleness book o 123,217 65,995 8ms 3.8min 11.5d 112.6d 0 book_staleness last_trade_price h 52,158 784 21ms 67ms 390ms 5.9s 0 transport_latency_assumed last_trade_price i 51,928 646 23ms 75ms 887ms 2.5s 0 transport_latency_assumed last_trade_price m 51,994 26,287 6ms 28ms 191ms 1.5s 0 transport_latency_assumed last_trade_price n 51,881 30 50ms 410ms 5.6s 12.7s 0 transport_latency_assumed last_trade_price o 52,128 24,532 6ms 30ms 201ms 3.1s 0 transport_latency_assumed market_resolved h 883 45 20ms 65ms 47.6s 57.2s 0 transport_latency_assumed market_resolved i 883 106 23ms 19.4s 49.6s 52.8s 0 transport_latency_assumed market_resolved m 883 403 6ms 21.0s 51.8s 54.0s 0 transport_latency_assumed market_resolved n 883 16 46ms 171ms 55.5s 55.6s 0 transport_latency_assumed market_resolved o 883 371 6ms 19.7s 51.2s 53.8s 0 transport_latency_assumed new_market h 698 117 148ms 18.7s 35.2s 1.5min 0 transport_latency_assumed new_market i 698 217 76ms 25.8s 34.6s 1.8min 0 transport_latency_assumed new_market m 698 337 53ms 31.4s 40.4s 1.7min 0 transport_latency_assumed new_market n 698 183 91ms 28.5s 38.2s 1.4min 0 transport_latency_assumed new_market o 698 255 77ms 32.1s 40.2s 1.5min 0 transport_latency_assumed price_change h 123,687,719 1,415,134 19ms 38ms 247ms 45.4s 0 transport_latency_assumed price_change i 123,602,269 966,228 21ms 39ms 219ms 2.5s 0 transport_latency_assumed price_change m 123,587,195 61,677,065 5ms 20ms 117ms 6.2s 0 transport_latency_assumed price_change n 123,565,337 41,840 45ms 79ms 747ms 12.8s 0 transport_latency_assumed price_change o 123,695,271 59,642,102 5ms 20ms 116ms 7.7s 0 transport_latency_assumed tick_size_change h 3,672 4 19ms 31ms 266ms 1.2s 0 transport_latency_assumed tick_size_change i 3,672 4 21ms 29ms 50ms 274ms 0 transport_latency_assumed tick_size_change m 3,672 1,797 5ms 12ms 43ms 547ms 0 transport_latency_assumed tick_size_change n 3,672 not meas. 44ms 58ms 160ms 211ms 0 transport_latency_assumed tick_size_change o 3,672 1,867 5ms 12ms 52ms 1.2s 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-08/01/2026-10-08T01.parquet sha256sum 2026-10-08T01.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.