Hour audit: 2026-10-04T17
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.
No findings
Every check that could be evaluated for this hour passed. That is not the same as the hour being perfect: it means the records this archive keeps about it agree with each other and with the corpus ledger.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-10-04T17 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-04T17:00:00.000067077+00:00 · last event 2026-10-04T17:59:59.999891526+00:00
VOLUME 142,482,042 rows · 1,728,949,968 bytes (1.61 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured i: 140,237,583 · h: 139,860,768 · m: 139,793,606 · o: 127,855,981 · n: 122,363,853 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 1,027,991 (0.72%) · h: 2,060,642 (1.45%) · m: 70,941,416 (49.79%) · o: 66,918,606 (46.97%) · n: 1,533,387 (1.08%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 684c38cde532db3f3e0ae4037a7ca7bb8ab7e904db31eecb918fb127fd784a46
the corpus checksum ledger names this file with the same digest
joined 142,482,759 to merged 142,482,042, minus 717 (minus 0.0005%)
boundary drops 717 · 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-04T19:41: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 8/8 pass
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
PASS the checksum ledger names 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 11,202,206 143,857,031 0-42 47b4d6135da87675cfc417056043767f465f58f864d30bc31576b3d65d0c49e3 book 1,832,801 97,617,398 43-49 44d11ee3ab4f04be819bc24b069cb822d1913a6f7b3cb4957aa07703977f1896 last_trade_price 65,694 3,829,676 50-50 667247cbf43cbdccf14d31069a5cc0bed3a0efcca199d8929c16a7b55c6aac33 market_resolved 4,546 440,528 51-51 343dc2a95cb9fe8dacc87bced9c6b50159b8e5d60b4152225a4356978bba51b4 new_market 5,651 464,877 52-52 30ad3d35942a1bda5b82984bd26a23183fd14fed81cb3bb97e9c2b5fc2768228 price_change 129,366,196 1,480,937,082 53-546 224955416780b739d06abea68e9729f70ce8fa618affa5a9e4ceb0b0bcdfa752 tick_size_change 4,948 185,734 547-547 421ddd7b1a7479a5612120213bd41277ad0c227e62f47954029e993f7d6ac00a EVENT MIX count share price_change 129,366,196 90.79% best_bid_ask 11,202,206 7.86% book 1,832,801 1.29% last_trade_price 65,694 0.05% new_market 5,651 <0.01% tick_size_change 4,948 <0.01% market_resolved 4,546 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,202,262 11,202,206 56 5,561 FULL book 1,832,803 1,832,801 2 232,686 FULL last_trade_price 65,694 65,694 0 546 FULL market_resolved 4,547 4,546 1 107 FULL new_market 5,651 5,651 0 0 FULL price_change 129,366,854 129,366,196 658 7,823 FULL tick_size_change 4,948 4,948 0 283 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 11,096,496 160,750 19ms 40ms 695ms 1.1min 0 transport_latency_assumed best_bid_ask i 11,156,186 79,739 22ms 43ms 361ms 29.6s 0 transport_latency_assumed best_bid_ask m 11,109,973 5,622,958 6ms 20ms 197ms 7.0s 0 transport_latency_assumed best_bid_ask n 9,636,315 10,280 48ms 85ms 405ms 27.6s 0 transport_latency_assumed best_bid_ask o 10,079,609 5,328,479 5ms 21ms 237ms 8.0s 0 transport_latency_assumed book h 139,311 5,030 25ms 234ms 27.9min 109.2d 0 book_staleness book i 139,897 4,139 26ms 460ms 2.0h 109.2d 0 book_staleness book m 139,382 67,358 9ms 72ms 25.9min 109.3d 0 book_staleness book n 1,548,930 1,397,886 20.9min 2.7d 43.2d 127.8d 0 book_staleness book o 1,075,795 358,388 16.3min 2.3d 43.2d 127.8d 0 book_staleness last_trade_price h 65,386 1,207 21ms 87ms 851ms 52.0s 0 transport_latency_assumed last_trade_price i 65,368 455 25ms 161ms 2.4s 5.5s 0 transport_latency_assumed last_trade_price m 65,486 31,863 7ms 30ms 231ms 2.4s 0 transport_latency_assumed last_trade_price n 56,479 82 56ms 322ms 5.3s 27.3s 0 transport_latency_assumed last_trade_price o 59,228 32,087 7ms 28ms 246ms 3.3s 0 transport_latency_assumed market_resolved h 2,591 65 24ms 28.9s 54.1s 2.4min 0 transport_latency_assumed market_resolved i 2,595 25 27ms 32.6s 53.8s 2.2min 0 transport_latency_assumed market_resolved m 2,594 1,370 8ms 29.4s 56.5s 2.3min 0 transport_latency_assumed market_resolved n 3,916 1,571 174ms 16.7min 21.5min 23.2min 0 transport_latency_assumed market_resolved o 2,886 1,515 10ms 5.9min 9.6min 13.2min 0 transport_latency_assumed new_market h 2,899 595 187ms 35.6s 56.7s 1.6min 0 transport_latency_assumed new_market i 2,899 543 180ms 33.6s 52.8s 1.6min 0 transport_latency_assumed new_market m 2,899 1,749 63ms 35.6s 53.9s 1.7min 0 transport_latency_assumed new_market n 3,757 929 290ms 3.6min 16.9min 17.8min 0 transport_latency_assumed new_market o 3,058 1,835 96ms 46.2s 4.9min 5.7min 0 transport_latency_assumed price_change h 128,549,173 1,892,922 20ms 45ms 774ms 1.1min 0 transport_latency_assumed price_change i 128,865,714 943,044 22ms 49ms 559ms 29.7s 0 transport_latency_assumed price_change m 128,468,364 65,213,397 6ms 21ms 209ms 7.7s 0 transport_latency_assumed price_change n 111,109,872 122,628 49ms 100ms 866ms 27.7s 0 transport_latency_assumed price_change o 116,631,173 61,194,205 6ms 22ms 245ms 9.7s 0 transport_latency_assumed tick_size_change h 4,912 73 19ms 44ms 2.5s 10.8s 0 transport_latency_assumed tick_size_change i 4,924 46 22ms 45ms 301ms 847ms 0 transport_latency_assumed tick_size_change m 4,908 2,721 6ms 21ms 183ms 292ms 0 transport_latency_assumed tick_size_change n 4,584 11 48ms 104ms 462ms 1.7s 0 transport_latency_assumed tick_size_change o 4,232 2,097 6ms 24ms 240ms 926ms 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-04/17/2026-10-04T17.parquet sha256sum 2026-10-04T17.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.