Hour audit: 2026-10-08T07
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-08T07 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-10-08T07:00:00.000046153+00:00 · last event 2026-10-08T07:59:59.998276796+00:00
VOLUME 108,177,806 rows · 1,234,126,210 bytes (1.15 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 107,722,447 · h: 107,717,889 · m: 107,716,078 · n: 107,599,199 · i: 107,565,153 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 51,580,831 (47.68%) · h: 691,380 (0.64%) · m: 55,225,991 (51.05%) · n: 185,144 (0.17%) · i: 494,460 (0.46%) (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 108,177,806 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 bf9c812d3c7441adf58e9e58a6ec11d58ac69694abe9462d8e234a20b18ec446
the corpus checksum ledger names this file with a DIFFERENT digest
joined 108,179,570 to merged 108,177,806, minus 1,764 (minus 0.0016%)
boundary drops 1,764 · 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-09T12:07:13Z 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 11,369,576 140,258,943 0-43 b677439bc5c484b85c058f3e8441cf55e748fab983e5d8ec19efdc84eb269603 book 675,563 59,624,690 44-46 a501ef32a48a297fd1d30abc8a5810e3ccc3b4d31264156790969986775b24a2 last_trade_price 45,179 2,638,046 47-47 8334d9acef079f58dc582bb9eb3ebbbfca4b329d8839530970703d114f39f0c8 market_resolved 502 80,345 48-48 4a73e8d53e46c3bef9cd7cef28f61ab92fb244c07af1aa29acf381253284c3c5 new_market 762 79,576 49-49 d7c16a17ed81992245ef27323086301c3ff7933fa86df73cca4f4061cb5670fc price_change 96,084,240 1,030,137,135 50-416 ad07b484b5282dae3e86a7a4e9b1b9c2ac20866ce3dd919eac880bfddc5b0532 tick_size_change 1,984 72,496 417-417 2d403cb081a9dfaea1a8e9d55b5f6a9003f9df14de4cb8ca78c76754c09b2584 EVENT MIX count share price_change 96,084,240 88.82% best_bid_ask 11,369,576 10.51% book 675,563 0.62% last_trade_price 45,179 0.04% tick_size_change 1,984 <0.01% new_market 762 <0.01% market_resolved 502 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,369,668 11,369,576 92 71 FULL book 676,137 675,563 574 206,577 FULL last_trade_price 45,179 45,179 0 1 FULL market_resolved 502 502 0 0 FULL new_market 762 762 0 0 FULL price_change 96,085,338 96,084,240 1,098 53 FULL tick_size_change 1,984 1,984 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 11,367,437 50,693 19ms 34ms 255ms 49.6s 0 transport_latency_assumed best_bid_ask i 11,367,555 42,726 21ms 29ms 113ms 5.7s 0 transport_latency_assumed best_bid_ask m 11,367,981 5,767,788 5ms 12ms 70ms 4.2s 0 transport_latency_assumed best_bid_ask n 11,366,775 1,987 43ms 56ms 205ms 7.9s 0 transport_latency_assumed best_bid_ask o 11,368,508 5,506,382 5ms 12ms 77ms 4.8s 0 transport_latency_assumed book h 275,648 146,273 2.3min 3.5h 46.7d 131.4d 0 book_staleness book i 149,587 40,089 61ms 3.4h 32.7d 131.4d 0 book_staleness book m 251,220 166,307 1.7min 3.5h 46.7d 131.4d 0 book_staleness book n 290,493 160,100 2.8min 3.5h 46.7d 131.4d 0 book_staleness book o 244,569 162,794 1.5min 3.5h 46.7d 131.4d 0 book_staleness last_trade_price h 45,043 282 21ms 100ms 750ms 10.9s 0 transport_latency_assumed last_trade_price i 44,974 192 23ms 154ms 932ms 5.7s 0 transport_latency_assumed last_trade_price m 45,006 23,472 6ms 21ms 171ms 1.3s 0 transport_latency_assumed last_trade_price n 45,006 26 48ms 583ms 4.1s 7.9s 0 transport_latency_assumed last_trade_price o 45,095 21,207 6ms 19ms 178ms 1.3s 0 transport_latency_assumed market_resolved h 487 1 22ms 170ms 53.3s 54.5s 0 transport_latency_assumed market_resolved i 487 39 23ms 87ms 42.5s 43.6s 0 transport_latency_assumed market_resolved m 487 244 6ms 25ms 43.1s 44.1s 0 transport_latency_assumed market_resolved n 487 15 45ms 166ms 52.7s 56.3s 0 transport_latency_assumed market_resolved o 487 203 6ms 29ms 43.4s 44.4s 0 transport_latency_assumed new_market h 508 71 177ms 15.6s 26.1s 1.6min 0 transport_latency_assumed new_market i 508 64 112ms 15.6s 26.4s 1.3min 0 transport_latency_assumed new_market m 508 301 47ms 14.8s 26.2s 1.2min 0 transport_latency_assumed new_market n 508 136 203ms 15.4s 25.7s 1.7min 0 transport_latency_assumed new_market o 508 190 71ms 11.4s 21.4s 1.3min 0 transport_latency_assumed price_change h 96,026,782 494,056 19ms 40ms 374ms 49.9s 0 transport_latency_assumed price_change i 96,000,058 411,350 21ms 35ms 324ms 5.7s 0 transport_latency_assumed price_change m 96,048,892 49,266,872 5ms 14ms 88ms 4.8s 0 transport_latency_assumed price_change n 95,893,946 22,880 44ms 71ms 1.4s 7.9s 0 transport_latency_assumed price_change o 96,061,296 45,889,082 5ms 14ms 97ms 5.8s 0 transport_latency_assumed tick_size_change h 1,984 4 19ms 30ms 130ms 300ms 0 transport_latency_assumed tick_size_change i 1,984 not meas. 21ms 30ms 54ms 291ms 0 transport_latency_assumed tick_size_change m 1,984 1,007 5ms 12ms 62ms 276ms 0 transport_latency_assumed tick_size_change n 1,984 not meas. 44ms 54ms 164ms 393ms 0 transport_latency_assumed tick_size_change o 1,984 973 5ms 15ms 66ms 80ms 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/07/2026-10-08T07.parquet sha256sum 2026-10-08T07.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.