Hour audit: 2026-10-05T07
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-05T07 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-05T07:00:00.000026437+00:00 · last event 2026-10-05T07:59:59.999954137+00:00
VOLUME 108,676,036 rows · 1,188,974,467 bytes (1.11 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 108,577,025 · m: 108,539,084 · h: 108,528,732 · i: 108,492,552 · n: 108,432,409 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 51,022,440 (46.95%) · m: 56,458,537 (51.95%) · h: 769,676 (0.71%) · i: 375,245 (0.35%) · n: 50,138 (0.05%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 108,676,036 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 3cde463aec8741f7947646e82449a09ffd6ece95599e60f9c8943d8fadc416fb
the corpus checksum ledger names this file with the same digest
joined 108,677,413 to merged 108,676,036, minus 1,377 (minus 0.0013%)
boundary drops 1,377 · 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-05T09:02:47Z 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,673,998 119,370,332 0-36 77ebf8acc7c849ee059eee119c2490ec56941a949027238fd6db2ad9ec9e0113 book 145,711 15,871,440 37-37 71a677484ed2e70a796315f6edf8f71e2a9eda03494e080ffed268264bd5f8ab last_trade_price 49,990 2,895,549 38-38 cacabece2b1f45ec6f1c2eee43c11bb4202787f0adb1e8603272559666ffcf85 market_resolved 484 81,039 39-39 0a36ef4efd935fbde61c1607683d90756061db45044b3546882fed5887553c64 new_market 1,465 136,777 40-40 2fdc3a2832d44f79f1a4b5299b2c0210a877deddcd31a261c332517bf5640efd price_change 98,801,984 1,049,290,266 41-417 709232129c440e19fb8c24668de8dbe098f2792df071adf8c789b70849a5c71b tick_size_change 2,404 90,622 418-418 adbe8c34ca4cfbfc4dbbde36ee8eb0c271a682a4f1b1617e77a5ee4a0bcf395b EVENT MIX count share price_change 98,801,984 90.91% best_bid_ask 9,673,998 8.90% book 145,711 0.13% last_trade_price 49,990 0.05% tick_size_change 2,404 <0.01% new_market 1,465 <0.01% market_resolved 484 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,674,111 9,673,998 113 106 FULL book 145,717 145,711 6 17,864 FULL last_trade_price 49,990 49,990 0 0 FULL market_resolved 484 484 0 0 FULL new_market 1,465 1,465 0 0 FULL price_change 98,803,242 98,801,984 1,258 1,552 FULL tick_size_change 2,404 2,404 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 9,671,808 59,587 19ms 33ms 353ms 1.1min 0 transport_latency_assumed best_bid_ask i 9,672,126 31,022 23ms 33ms 130ms 3.9s 0 transport_latency_assumed best_bid_ask m 9,672,898 5,087,275 5ms 14ms 76ms 5.3s 0 transport_latency_assumed best_bid_ask n 9,670,303 2,316 47ms 65ms 240ms 23.4s 0 transport_latency_assumed best_bid_ask o 9,673,094 4,493,798 5ms 14ms 77ms 7.1s 0 transport_latency_assumed book h 124,382 23,729 28ms 33.1min 25.9d 109.9d 0 book_staleness book i 104,388 3,715 27ms 316ms 4.6h 109.8d 0 book_staleness book m 103,516 54,051 7ms 38ms 27.8min 109.9d 0 book_staleness book n 114,462 13,388 55ms 55.3s 8.7d 128.4d 0 book_staleness book o 104,440 50,828 7ms 42ms 6.2h 109.9d 0 book_staleness last_trade_price h 49,945 463 21ms 90ms 695ms 28.9s 0 transport_latency_assumed last_trade_price i 49,815 178 26ms 198ms 998ms 2.8s 0 transport_latency_assumed last_trade_price m 49,869 25,373 6ms 23ms 211ms 2.2s 0 transport_latency_assumed last_trade_price n 49,395 14 52ms 975ms 10.0s 23.5s 0 transport_latency_assumed last_trade_price o 49,846 23,962 6ms 23ms 198ms 3.0s 0 transport_latency_assumed market_resolved h 484 1 23ms 82ms 36.9s 45.1s 0 transport_latency_assumed market_resolved i 484 33 26ms 93ms 27.8s 37.4s 0 transport_latency_assumed market_resolved m 484 232 6ms 23ms 30.5s 39.3s 0 transport_latency_assumed market_resolved n 484 not meas. 50ms 202ms 40.7s 50.4s 0 transport_latency_assumed market_resolved o 484 218 6ms 27ms 38.3s 47.5s 0 transport_latency_assumed new_market h 863 126 208ms 29.1s 44.9s 1.6min 0 transport_latency_assumed new_market i 863 207 122ms 17.3s 37.9s 1.5min 0 transport_latency_assumed new_market m 863 560 63ms 21.7s 39.1s 1.5min 0 transport_latency_assumed new_market n 863 118 184ms 24.1s 53.0s 1.5min 0 transport_latency_assumed new_market o 863 454 60ms 23.0s 41.9s 1.7min 0 transport_latency_assumed price_change h 98,678,846 685,734 19ms 41ms 519ms 1.1min 0 transport_latency_assumed price_change i 98,662,472 340,090 23ms 43ms 377ms 4.0s 0 transport_latency_assumed price_change m 98,709,050 51,289,744 5ms 16ms 93ms 5.7s 0 transport_latency_assumed price_change n 98,594,498 34,302 48ms 84ms 2.3s 23.5s 0 transport_latency_assumed price_change o 98,745,894 46,452,114 5ms 16ms 92ms 7.2s 0 transport_latency_assumed tick_size_change h 2,404 36 19ms 38ms 453ms 6.7s 0 transport_latency_assumed tick_size_change i 2,404 not meas. 23ms 42ms 117ms 300ms 0 transport_latency_assumed tick_size_change m 2,404 1,302 5ms 14ms 67ms 187ms 0 transport_latency_assumed tick_size_change n 2,404 not meas. 47ms 68ms 163ms 284ms 0 transport_latency_assumed tick_size_change o 2,404 1,066 5ms 17ms 89ms 278ms 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/07/2026-10-05T07.parquet sha256sum 2026-10-05T07.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.