Hour audit: 2026-10-05T02
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-05T02 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-05T02:00:00.000578485+00:00 · last event 2026-10-05T02:59:59.999890670+00:00
VOLUME 104,233,457 rows · 1,151,132,751 bytes (1.07 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 104,131,790 · n: 104,109,102 · m: 104,081,928 · h: 104,050,700 · i: 103,838,087 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 48,388,851 (46.42%) · n: 59,361 (0.06%) · m: 54,399,796 (52.19%) · h: 1,015,745 (0.97%) · i: 369,704 (0.35%) (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 104,233,457 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 36164562ec9b3ecf71c525fe8f591af78415e9a10ff0f609914d3be0d20e9345
the corpus checksum ledger names this file with the same digest
joined 104,234,843 to merged 104,233,457, minus 1,386 (minus 0.0013%)
boundary drops 1,386 · 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-05T04:00:16Z 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,909,315 120,448,580 0-37 0a75a7ce00b947ecfa84d48819ea7432055f80654c0a8a9edcdce56dafb61179 book 173,266 18,262,134 38-38 df7fccba66866da6c4b8730bb31d6dd515efb7599a181a94bc6dfc7abc8e990f last_trade_price 53,898 3,042,837 39-39 7f98a135c3564a51de67c6f5cc1a48353f9c99b551b0ae0d077e06ef75134197 market_resolved 1,089 169,819 40-40 184cceef34680e4c4f86deec89eae2798e5c4eeefe5814897856607f59a9aaff new_market 1,435 149,800 41-41 1e1721d367cfd744f11c438e02f3a4c537a71e72556679dbea28060ba61d21b8 price_change 94,092,178 1,007,786,403 42-400 9db6fd5ab53fcd428a86694f64b6767efd17da610ea89d009ccf2d30cc0752e5 tick_size_change 2,276 85,218 401-401 2dbdcde207404d9c69bbee48eefee4a4d73815c25aad2ab3cda19554f847ba3b EVENT MIX count share price_change 94,092,178 90.27% best_bid_ask 9,909,315 9.51% book 173,266 0.17% last_trade_price 53,898 0.05% tick_size_change 2,276 <0.01% new_market 1,435 <0.01% market_resolved 1,089 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,909,391 9,909,315 76 102 FULL book 173,500 173,266 234 27,542 FULL last_trade_price 53,898 53,898 0 0 FULL market_resolved 1,089 1,089 0 5 FULL new_market 1,435 1,435 0 0 FULL price_change 94,093,254 94,092,178 1,076 1,368 FULL tick_size_change 2,276 2,276 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 9,907,279 82,185 17ms 26ms 197ms 2.2min 0 transport_latency_assumed best_bid_ask i 9,899,892 28,738 22ms 31ms 126ms 51.6s 0 transport_latency_assumed best_bid_ask m 9,908,624 5,185,749 5ms 13ms 76ms 6.6s 0 transport_latency_assumed best_bid_ask n 9,907,618 3,076 48ms 67ms 202ms 14.0s 0 transport_latency_assumed best_bid_ask o 9,908,514 4,609,567 5ms 14ms 76ms 6.9s 0 transport_latency_assumed book h 115,141 7,386 20ms 123ms 7.2h 128.2d 0 book_staleness book i 114,136 7,505 24ms 131ms 6.9h 109.7d 0 book_staleness book m 114,180 60,397 7ms 50ms 9.4h 109.5d 0 book_staleness book n 128,392 18,918 54ms 6.4min 14.7d 109.7d 0 book_staleness book o 138,933 79,060 8ms 1.6h 27.3d 128.2d 0 book_staleness last_trade_price h 53,800 930 18ms 49ms 350ms 55.3s 0 transport_latency_assumed last_trade_price i 52,994 328 23ms 52ms 356ms 1.7s 0 transport_latency_assumed last_trade_price m 53,841 27,995 6ms 23ms 177ms 2.3s 0 transport_latency_assumed last_trade_price n 53,813 22 51ms 194ms 2.4s 5.7s 0 transport_latency_assumed last_trade_price o 53,759 24,623 6ms 23ms 174ms 1.8s 0 transport_latency_assumed market_resolved h 1,045 4 20ms 32.9s 55.3s 1.7min 0 transport_latency_assumed market_resolved i 1,040 172 24ms 30.1s 52.7s 52.8s 0 transport_latency_assumed market_resolved m 1,045 495 6ms 31.3s 54.8s 54.9s 0 transport_latency_assumed market_resolved n 1,045 not meas. 51ms 37.9s 50.6s 50.6s 0 transport_latency_assumed market_resolved o 1,044 418 6ms 34.0s 46.6s 46.7s 0 transport_latency_assumed new_market h 972 125 12.7s 24.2s 44.9s 1.6min 0 transport_latency_assumed new_market i 972 182 12.2s 24.6s 52.5s 1.6min 0 transport_latency_assumed new_market m 972 415 9.6s 23.9s 42.6s 1.3min 0 transport_latency_assumed new_market n 972 252 10.2s 25.4s 51.8s 1.6min 0 transport_latency_assumed new_market o 972 461 150ms 25.9s 51.0s 1.7min 0 transport_latency_assumed price_change h 93,970,187 925,106 17ms 31ms 262ms 2.2min 0 transport_latency_assumed price_change i 93,766,777 332,776 22ms 35ms 198ms 51.9s 0 transport_latency_assumed price_change m 94,000,990 49,123,521 5ms 15ms 89ms 7.7s 0 transport_latency_assumed price_change n 94,014,986 37,093 48ms 79ms 445ms 20.1s 0 transport_latency_assumed price_change o 94,026,292 43,673,682 5ms 15ms 88ms 7.0s 0 transport_latency_assumed tick_size_change h 2,276 9 17ms 23ms 67ms 7.2s 0 transport_latency_assumed tick_size_change i 2,276 3 22ms 31ms 348ms 368ms 0 transport_latency_assumed tick_size_change m 2,276 1,224 5ms 11ms 68ms 193ms 0 transport_latency_assumed tick_size_change n 2,276 not meas. 48ms 60ms 122ms 227ms 0 transport_latency_assumed tick_size_change o 2,276 1,040 5ms 12ms 46ms 84ms 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/02/2026-10-05T02.parquet sha256sum 2026-10-05T02.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.