Hour audit: 2026-10-05T14
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-05T14 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-05T14:00:00.000083549+00:00 · last event 2026-10-05T14:59:59.999983941+00:00
VOLUME 115,875,913 rows · 1,316,162,822 bytes (1.23 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 114,959,825 · n: 114,747,158 · m: 114,709,042 · i: 114,694,478 · h: 114,655,266 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 61,811,883 (53.34%) · n: 80,674 (0.07%) · m: 52,254,677 (45.10%) · i: 803,609 (0.69%) · h: 925,070 (0.80%) (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 115,875,913 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 bb34df98590f507c25c054b8f179658923efeaa34d87b35683e513a4286be31d
the corpus checksum ledger names this file with the same digest
joined 115,877,743 to merged 115,875,913, minus 1,830 (minus 0.0016%)
boundary drops 1,830 · 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-05T16:01:43Z 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,743,863 123,505,294 0-37 3fda0acca268061222ed6b5a8357742a4615e21ec28b31cea8574b86374bd976 book 163,714 18,286,711 38-38 f2d466c53eed8a4748727dac519bff01250ba44aa0a6d1ae6f13ab33fc75597c last_trade_price 64,977 3,725,371 39-39 540e494252e6beb9e66a4a10a5855ec1f6196751106fd9a0c9ea380e4e852345 market_resolved 1,311 200,149 40-40 22192412015eed98ce11ca6e2b8b541ccfd0a26456fb9ff48fa106a1bad8322a new_market 3,160 363,183 41-41 630439b56ed3e49067de38ba7dc211d7268f6c68c33becb1a35648712e7370a2 price_change 105,895,460 1,168,634,739 42-445 c2592a90408f89b0378b5224862fd441fc93075fe427170a529f8730eb062f5f tick_size_change 3,428 126,925 446-446 11d9db627d17baadef1a54f8279331da3e5f104c22d64008ad69a20b256b26fd EVENT MIX count share price_change 105,895,460 91.39% best_bid_ask 9,743,863 8.41% book 163,714 0.14% last_trade_price 64,977 0.06% tick_size_change 3,428 <0.01% new_market 3,160 <0.01% market_resolved 1,311 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,744,002 9,743,863 139 2,828 FULL book 163,724 163,714 10 10,853 FULL last_trade_price 64,978 64,977 1 118 FULL market_resolved 1,311 1,311 0 21 FULL new_market 3,160 3,160 0 0 FULL price_change 105,897,140 105,895,460 1,680 5,985 FULL tick_size_change 3,428 3,428 0 21 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 9,671,471 74,248 19ms 35ms 636ms 2.2min 0 transport_latency_assumed best_bid_ask i 9,672,534 64,843 21ms 36ms 247ms 20.5s 0 transport_latency_assumed best_bid_ask m 9,643,388 4,422,011 5ms 17ms 157ms 9.7s 0 transport_latency_assumed best_bid_ask n 9,692,437 4,666 45ms 75ms 545ms 35.4s 0 transport_latency_assumed best_bid_ask o 9,652,934 5,178,095 5ms 17ms 164ms 10.1s 0 transport_latency_assumed book h 147,998 16,376 27ms 9.4s 3.6d 110.2d 0 book_staleness book i 135,267 5,116 27ms 912ms 1.9h 110.1d 0 book_staleness book m 135,805 64,217 8ms 52ms 1.5min 68.0d 0 book_staleness book n 137,271 9,025 56ms 5.9s 8.3h 110.2d 0 book_staleness book o 134,985 68,980 8ms 43ms 8.9s 110.1d 0 book_staleness last_trade_price h 64,159 434 22ms 196ms 4.7s 51.7s 0 transport_latency_assumed last_trade_price i 63,658 331 26ms 329ms 5.8s 20.2s 0 transport_latency_assumed last_trade_price m 64,560 30,471 7ms 27ms 285ms 3.8s 0 transport_latency_assumed last_trade_price n 62,574 30 54ms 2.3s 13.2s 35.3s 0 transport_latency_assumed last_trade_price o 64,791 33,711 7ms 26ms 259ms 3.3s 0 transport_latency_assumed market_resolved h 1,236 36 21ms 34.6s 54.0s 2.0min 0 transport_latency_assumed market_resolved i 1,239 202 23ms 28.8s 52.3s 2.0min 0 transport_latency_assumed market_resolved m 1,235 467 7ms 32.8s 56.5s 1.7min 0 transport_latency_assumed market_resolved n 1,237 not meas. 47ms 41.6s 53.4s 1.2min 0 transport_latency_assumed market_resolved o 1,237 606 6ms 37.6s 49.9s 2.2min 0 transport_latency_assumed new_market h 2,409 255 19.1s 30.4s 56.5s 1.7min 0 transport_latency_assumed new_market i 2,409 496 19.8s 30.8s 57.4s 1.7min 0 transport_latency_assumed new_market m 2,409 786 18.2s 31.5s 53.0s 1.7min 0 transport_latency_assumed new_market n 2,409 846 19.5s 32.5s 56.9s 1.5min 0 transport_latency_assumed new_market o 2,409 777 18.5s 31.4s 56.3s 1.6min 0 transport_latency_assumed price_change h 104,764,585 833,705 19ms 50ms 1.1s 2.3min 0 transport_latency_assumed price_change i 104,815,951 732,598 22ms 52ms 1.2s 20.6s 0 transport_latency_assumed price_change m 104,858,249 47,735,235 6ms 20ms 194ms 10.7s 0 transport_latency_assumed price_change n 104,847,814 66,105 45ms 127ms 4.5s 35.5s 0 transport_latency_assumed price_change o 105,100,053 56,527,817 5ms 19ms 186ms 10.1s 0 transport_latency_assumed tick_size_change h 3,408 16 19ms 50ms 497ms 46.9s 0 transport_latency_assumed tick_size_change i 3,420 23 22ms 49ms 370ms 10.7s 0 transport_latency_assumed tick_size_change m 3,396 1,490 5ms 20ms 254ms 1.8s 0 transport_latency_assumed tick_size_change n 3,416 2 44ms 68ms 379ms 2.9s 0 transport_latency_assumed tick_size_change o 3,416 1,897 5ms 16ms 283ms 685ms 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/14/2026-10-05T14.parquet sha256sum 2026-10-05T14.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.