Hour audit: 2026-10-05T19
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-05T19 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-05T19:00:00.000141507+00:00 · last event 2026-10-05T19:59:59.999955057+00:00
VOLUME 115,011,741 rows · 1,323,005,144 bytes (1.23 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured m: 114,776,151 · h: 114,552,824 · o: 114,318,051 · n: 114,188,262 · i: 114,105,116 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 55,413,341 (48.18%) · h: 1,238,148 (1.08%) · o: 56,924,726 (49.49%) · n: 147,897 (0.13%) · i: 1,287,629 (1.12%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 b6d144a900ed24bff1e58c4fe7f241581145d8493ba6bbda9c00827391f3b2fa
the corpus checksum ledger names this file with the same digest
joined 115,013,183 to merged 115,011,741, minus 1,442 (minus 0.0013%)
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-05T21:01:20Z 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 9,656,328 124,856,614 0-36 77c7661bb71172a04e669d3f692167b21573d70ed42c239b83dcd4b3b89e6882 book 193,466 20,289,275 37-37 098632fc5403c9972741ea0013909bd09559757b4b03e03a00dc858ec1ccec01 last_trade_price 61,532 3,571,424 38-38 ebd5c53c9eea87ade93c665db26d0811e891d50e392fad5bb550155419c12138 market_resolved 973 148,359 39-39 42a0167885d5c70693aa1f1f1a579f66e56435d11a23bfabb176dec9ade45b0f new_market 6,012 573,270 40-40 a21454631734ea5475daac6e182b727c9c81d78138f17f6fa8e5082cfac35930 price_change 105,089,750 1,172,120,760 41-441 faf43d280aef7ba53b5023a90d9d23b87d7e257faa849e24079c437420c60b2e tick_size_change 3,680 136,422 442-442 334ac67a799301a124a766ea8d598078773ccd760a59f6b9658c7ef2a7ef8fd3 EVENT MIX count share price_change 105,089,750 91.37% best_bid_ask 9,656,328 8.40% book 193,466 0.17% last_trade_price 61,532 0.05% new_market 6,012 <0.01% tick_size_change 3,680 <0.01% market_resolved 973 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,656,478 9,656,328 150 249 FULL book 193,470 193,466 4 21,111 FULL last_trade_price 61,532 61,532 0 1 FULL market_resolved 973 973 0 0 FULL new_market 6,012 6,012 0 0 FULL price_change 105,091,038 105,089,750 1,288 1,575 FULL tick_size_change 3,680 3,680 0 5 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 9,647,871 95,119 19ms 50ms 1.6s 2.5min 0 transport_latency_assumed best_bid_ask i 9,637,602 102,327 22ms 42ms 317ms 20.9s 0 transport_latency_assumed best_bid_ask m 9,654,897 4,640,660 6ms 21ms 236ms 9.8s 0 transport_latency_assumed best_bid_ask n 9,645,334 9,233 45ms 96ms 678ms 43.1s 0 transport_latency_assumed best_bid_ask o 9,639,680 4,808,989 5ms 22ms 257ms 8.3s 0 transport_latency_assumed book h 143,596 15,780 27ms 14.4s 1.4d 110.3d 0 book_staleness book i 143,668 19,573 30ms 18.4s 2.2d 110.4d 0 book_staleness book m 139,596 74,396 9ms 2.5s 9.9h 110.3d 0 book_staleness book n 137,073 13,098 60ms 9.5s 1.4d 110.8d 0 book_staleness book o 140,790 70,619 9ms 2.7s 3.9h 110.3d 0 book_staleness last_trade_price h 61,102 907 22ms 318ms 3.7s 1.7min 0 transport_latency_assumed last_trade_price i 60,066 664 26ms 304ms 2.8s 20.7s 0 transport_latency_assumed last_trade_price m 61,349 31,821 7ms 41ms 349ms 3.1s 0 transport_latency_assumed last_trade_price n 59,108 106 54ms 1.2s 10.5s 42.0s 0 transport_latency_assumed last_trade_price o 60,242 28,034 7ms 49ms 431ms 8.3s 0 transport_latency_assumed market_resolved h 905 15 21ms 106ms 52.4s 55.1s 0 transport_latency_assumed market_resolved i 905 115 25ms 21.8s 52.0s 52.0s 0 transport_latency_assumed market_resolved m 905 407 7ms 82ms 50.7s 55.0s 0 transport_latency_assumed market_resolved n 905 9 48ms 208ms 48.6s 57.1s 0 transport_latency_assumed market_resolved o 905 427 7ms 46ms 47.2s 56.8s 0 transport_latency_assumed new_market h 3,752 1,213 333ms 1.1min 1.4min 354.9d 0 transport_latency_assumed new_market i 3,752 1,198 19.7s 1.0min 1.4min 354.9d 0 transport_latency_assumed new_market m 3,752 1,459 17.1s 1.1min 1.5min 354.9d 0 transport_latency_assumed new_market n 3,752 735 17.3s 1.0min 1.5min 354.9d 0 transport_latency_assumed new_market o 3,752 1,407 17.6s 1.0min 1.5min 354.9d 0 transport_latency_assumed price_change h 104,691,918 1,125,078 19ms 73ms 2.2s 2.5min 0 transport_latency_assumed price_change i 104,255,443 1,163,678 22ms 57ms 842ms 20.9s 0 transport_latency_assumed price_change m 104,911,972 50,662,789 6ms 24ms 235ms 10.1s 0 transport_latency_assumed price_change n 104,338,410 124,700 46ms 165ms 4.0s 43.1s 0 transport_latency_assumed price_change o 104,469,022 52,013,505 6ms 25ms 265ms 8.6s 0 transport_latency_assumed tick_size_change h 3,680 36 20ms 127ms 1.2s 50.3s 0 transport_latency_assumed tick_size_change i 3,680 74 22ms 65ms 455ms 1.3s 0 transport_latency_assumed tick_size_change m 3,680 1,809 6ms 37ms 304ms 826ms 0 transport_latency_assumed tick_size_change n 3,680 16 46ms 165ms 746ms 1.9s 0 transport_latency_assumed tick_size_change o 3,660 1,745 6ms 52ms 373ms 1.4s 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-05/19/2026-10-05T19.parquet sha256sum 2026-10-05T19.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.