Hour audit: 2026-10-05T12
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-05T12 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-05T12:00:00.000066610+00:00 · last event 2026-10-05T12:59:59.999885702+00:00
VOLUME 105,810,056 rows · 1,190,666,710 bytes (1.11 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 105,642,655 · m: 105,631,122 · h: 105,622,803 · i: 105,425,404 · n: 105,389,087 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 50,535,415 (47.76%) · m: 53,555,563 (50.61%) · h: 687,517 (0.65%) · i: 943,934 (0.89%) · n: 87,627 (0.08%) (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 105,810,056 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 a6a7d46a122fd1cdc94ca88b4e5444d498ae5ca285540dcb108a9c164931172e
the corpus checksum ledger names this file with the same digest
joined 105,811,342 to merged 105,810,056, minus 1,286 (minus 0.0012%)
boundary drops 1,286 · 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-05T13:59:38Z 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,312,621 118,389,547 0-35 c51c02443892244a39d695a04b41250bd88605a5e7cff8b63ab7c7419c8e26ba book 144,146 16,092,802 36-36 829150fed7644b05becf0f2166d84f62795ac7599e4a708f214d6dafbe51d0f1 last_trade_price 53,761 3,136,857 37-37 1d73a7e00d3ff499a5f20b86ec86c05867207d138600389dc3ea6116f6e6cea2 market_resolved 656 106,330 38-38 9772e8b1b95f3e3bfe9e667bf10a93d668f5c4b425dbfe2bcc05eab175df2934 new_market 5,310 472,528 39-39 a9d2e463b365ef5ea6dfd15b13d4168b7cfe13452fdaac3db4956f8a2e581f30 price_change 96,289,910 1,051,126,687 40-407 f31a296cb399e620c37eb3a5515c8ca5a68b5b371a4701c4b8447c457a86b38f tick_size_change 3,652 133,725 408-408 1e9dcdb803b5b4b9c11e2005f7d0e2c164673135c0d553f412271226c50c236a EVENT MIX count share price_change 96,289,910 91.00% best_bid_ask 9,312,621 8.80% book 144,146 0.14% last_trade_price 53,761 0.05% new_market 5,310 <0.01% tick_size_change 3,652 <0.01% market_resolved 656 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,312,743 9,312,621 122 470 FULL book 144,146 144,146 0 11,970 FULL last_trade_price 53,761 53,761 0 0 FULL market_resolved 656 656 0 1 FULL new_market 5,310 5,310 0 0 FULL price_change 96,291,074 96,289,910 1,164 1,382 FULL tick_size_change 3,652 3,652 0 2 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 9,306,213 54,385 19ms 41ms 936ms 1.7min 0 transport_latency_assumed best_bid_ask i 9,301,895 80,894 21ms 34ms 205ms 24.1s 0 transport_latency_assumed best_bid_ask m 9,306,006 4,721,676 5ms 16ms 202ms 31.2s 0 transport_latency_assumed best_bid_ask n 9,300,628 5,905 44ms 78ms 517ms 36.9s 0 transport_latency_assumed best_bid_ask o 9,306,596 4,449,761 5ms 15ms 175ms 23.7s 0 transport_latency_assumed book h 127,688 17,029 28ms 29.2s 4.1d 128.6d 0 book_staleness book i 115,208 5,555 25ms 497ms 2.6h 110.1d 0 book_staleness book m 115,731 59,019 7ms 97ms 55.6min 110.1d 0 book_staleness book n 116,476 6,388 56ms 3.9s 10.7h 110.0d 0 book_staleness book o 115,658 56,155 7ms 94ms 39.0min 110.0d 0 book_staleness last_trade_price h 53,580 335 22ms 177ms 2.0s 57.4s 0 transport_latency_assumed last_trade_price i 52,981 410 24ms 165ms 1.8s 23.7s 0 transport_latency_assumed last_trade_price m 53,614 27,678 6ms 25ms 284ms 30.2s 0 transport_latency_assumed last_trade_price n 52,463 27 54ms 1.1s 11.1s 37.0s 0 transport_latency_assumed last_trade_price o 53,620 25,311 6ms 26ms 267ms 5.4s 0 transport_latency_assumed market_resolved h 646 12 23ms 36.3s 55.4s 55.4s 0 transport_latency_assumed market_resolved i 646 133 25ms 17.2s 43.4s 43.5s 0 transport_latency_assumed market_resolved m 646 272 6ms 20.5s 47.1s 47.2s 0 transport_latency_assumed market_resolved n 645 not meas. 51ms 30.5s 49.6s 57.0s 0 transport_latency_assumed market_resolved o 646 239 6ms 27.6s 54.0s 54.0s 0 transport_latency_assumed new_market h 3,045 875 290ms 38.0s 48.0s 1.6min 0 transport_latency_assumed new_market i 3,045 614 166ms 38.0s 47.4s 1.6min 0 transport_latency_assumed new_market m 3,045 1,815 97ms 37.7s 49.5s 1.7min 0 transport_latency_assumed new_market n 3,045 295 292ms 38.3s 48.4s 1.6min 0 transport_latency_assumed new_market o 3,045 1,711 79ms 35.8s 47.3s 1.4min 0 transport_latency_assumed price_change h 96,127,979 614,877 20ms 57ms 1.1s 1.8min 0 transport_latency_assumed price_change i 95,947,977 856,298 21ms 47ms 500ms 24.1s 0 transport_latency_assumed price_change m 96,148,432 48,743,193 5ms 18ms 213ms 31.2s 0 transport_latency_assumed price_change n 95,912,178 75,012 45ms 130ms 3.2s 37.0s 0 transport_latency_assumed price_change o 96,159,442 46,000,530 5ms 18ms 189ms 25.7s 0 transport_latency_assumed tick_size_change h 3,652 4 20ms 35ms 554ms 31.7s 0 transport_latency_assumed tick_size_change i 3,652 30 21ms 40ms 135ms 343ms 0 transport_latency_assumed tick_size_change m 3,648 1,910 5ms 11ms 114ms 303ms 0 transport_latency_assumed tick_size_change n 3,652 not meas. 44ms 65ms 456ms 937ms 0 transport_latency_assumed tick_size_change o 3,648 1,708 4ms 12ms 191ms 386ms 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/12/2026-10-05T12.parquet sha256sum 2026-10-05T12.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.