Hour audit: 2026-10-08T00
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-08T00 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-10-08T00:00:00.000104114+00:00 · last event 2026-10-08T00:59:59.999982151+00:00
VOLUME 133,157,184 rows · 1,520,779,556 bytes (1.42 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured i: 133,033,968 · o: 132,997,504 · h: 132,982,222 · m: 132,977,435 · n: 132,789,224 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 914,554 (0.69%) · o: 64,002,477 (48.07%) · h: 1,339,140 (1.01%) · m: 66,834,740 (50.19%) · n: 66,273 (0.05%) (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 133,157,184 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 5d7924b5966822b35af66f9f6df49ccdb6733dfc3442c71d9334d83c4e953bfe
the corpus checksum ledger names this file with a DIFFERENT digest
joined 133,158,626 to merged 133,157,184, minus 1,442 (minus 0.0011%)
boundary drops 1,442 · 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-09T06:12:22Z 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,681,920 157,008,827 0-48 d5cacc1bffbfc008c4ca85be51f009d4b95c6b958f7f50a28b63acc35e90b10d book 258,694 26,728,121 49-49 e439fb1c44a4572ad9071eb0f6bbc907d32424a5e1e4e3dcf8b8d7c37b91b9c9 last_trade_price 66,294 3,695,590 50-50 7eb56a54604372129a8b6079d03f3f0a4db16485b8501314e4bcb23a35d67968 market_resolved 484 80,181 51-51 13e33ea52c6af4249bfa3c0b426d6a32481e3260a4bb320564a78ea879bcf815 new_market 1,348 133,595 52-52 a0990330d2c5fb2b1929c35d2c1ab8629e505948f5f9ed8c8c8236e630cf3e3a price_change 120,145,304 1,331,503,612 53-511 74abaa5863a9e8c07baab752c409f4b4d91da48389032928b7dee63c59651a9d tick_size_change 3,140 114,170 512-512 0280e286aa429baa23582289aaf0ac85cfd858d40bc512fcad2e100a078db05b EVENT MIX count share price_change 120,145,304 90.23% best_bid_ask 12,681,920 9.52% book 258,694 0.19% last_trade_price 66,294 0.05% tick_size_change 3,140 <0.01% new_market 1,348 <0.01% market_resolved 484 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,682,052 12,681,920 132 93 FULL book 258,706 258,694 12 56,301 FULL last_trade_price 66,294 66,294 0 0 FULL market_resolved 484 484 0 0 FULL new_market 1,348 1,348 0 0 FULL price_change 120,146,602 120,145,304 1,298 102 FULL tick_size_change 3,140 3,140 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 12,680,120 116,397 18ms 32ms 203ms 44.2s 0 transport_latency_assumed best_bid_ask i 12,680,286 74,663 21ms 34ms 123ms 5.1s 0 transport_latency_assumed best_bid_ask m 12,681,087 6,416,257 5ms 17ms 101ms 4.3s 0 transport_latency_assumed best_bid_ask n 12,676,205 3,520 44ms 63ms 233ms 15.7s 0 transport_latency_assumed best_bid_ask o 12,680,733 6,071,083 5ms 17ms 96ms 4.3s 0 transport_latency_assumed book h 146,652 13,454 24ms 861ms 1.9d 112.6d 0 book_staleness book i 178,501 45,257 31ms 2.9h 30.2d 131.1d 0 book_staleness book m 162,099 94,234 8ms 17.7min 18.4d 131.1d 0 book_staleness book n 153,739 21,057 57ms 3.6min 10.8d 112.6d 0 book_staleness book o 156,279 84,692 8ms 3.9min 10.5d 112.6d 0 book_staleness last_trade_price h 66,070 794 20ms 114ms 787ms 8.9s 0 transport_latency_assumed last_trade_price i 66,093 536 24ms 144ms 1.6s 5.1s 0 transport_latency_assumed last_trade_price m 66,171 33,520 6ms 29ms 202ms 1.9s 0 transport_latency_assumed last_trade_price n 64,916 39 51ms 855ms 8.9s 15.7s 0 transport_latency_assumed last_trade_price o 66,042 31,405 6ms 29ms 262ms 2.4s 0 transport_latency_assumed market_resolved h 478 8 21ms 53ms 125ms 43.6s 0 transport_latency_assumed market_resolved i 478 10 24ms 78ms 53.8s 53.9s 0 transport_latency_assumed market_resolved m 478 240 6ms 14ms 55.9s 56.0s 0 transport_latency_assumed market_resolved n 478 not meas. 49ms 171ms 410ms 52.4s 0 transport_latency_assumed market_resolved o 478 226 6ms 14ms 54.6s 54.6s 0 transport_latency_assumed new_market h 826 171 82ms 25.1s 1.1min 1.8min 0 transport_latency_assumed new_market i 826 124 76ms 33.8s 1.1min 1.6min 0 transport_latency_assumed new_market m 826 484 44ms 35.7s 1.1min 1.8min 0 transport_latency_assumed new_market n 826 179 82ms 31.1s 58.0s 1.8min 0 transport_latency_assumed new_market o 826 390 50ms 26.6s 1.1min 1.8min 0 transport_latency_assumed price_change h 120,084,936 1,208,270 18ms 38ms 308ms 45.0s 0 transport_latency_assumed price_change i 120,104,644 793,938 21ms 39ms 227ms 5.1s 0 transport_latency_assumed price_change m 120,063,634 60,288,416 5ms 19ms 115ms 5.3s 0 transport_latency_assumed price_change n 119,889,920 41,478 45ms 80ms 821ms 15.7s 0 transport_latency_assumed price_change o 120,090,006 57,813,202 5ms 19ms 109ms 4.3s 0 transport_latency_assumed tick_size_change h 3,140 46 18ms 32ms 102ms 170ms 0 transport_latency_assumed tick_size_change i 3,140 26 21ms 38ms 120ms 259ms 0 transport_latency_assumed tick_size_change m 3,140 1,589 5ms 20ms 97ms 314ms 0 transport_latency_assumed tick_size_change n 3,140 not meas. 44ms 58ms 120ms 890ms 0 transport_latency_assumed tick_size_change o 3,140 1,479 5ms 19ms 110ms 238ms 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/00/2026-10-08T00.parquet sha256sum 2026-10-08T00.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.