Hour audit: 2026-10-02T09
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-02T09 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-02T09:00:00.000080174+00:00 · last event 2026-10-02T09:59:59.999860793+00:00
VOLUME 114,658,059 rows · 1,195,946,406 bytes (1.11 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured h: 114,531,441 · m: 114,522,068 · k: 114,518,210 · i: 114,502,518 · g: 114,463,687 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 1,167,379 (1.02%) · m: 107,902,731 (94.11%) · k: 5,154,280 (4.50%) · i: 308,749 (0.27%) · g: 124,920 (0.11%) (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 114,658,059 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 83b1da7f9f33d66e03a91214c59d688da4007ee1973eaccba7cd23132f26dea2
the corpus checksum ledger names this file with the same digest
joined 114,659,731 to merged 114,658,059, minus 1,672 (minus 0.0015%)
boundary drops 1,672 · 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-02T11:46:22Z as ghikm
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 10,504,742 124,533,143 0-40 c38873dc01f7208af9fa00c5cf4e42206e22bf566d5e2e8f94d8417774902ccb book 220,194 23,568,664 41-41 407a6b749251a42bf9de859215702b217ebb66b5cb69abe07f6509e3275e6848 last_trade_price 52,072 3,008,750 42-42 1a6c8b846276630c6187a2b8d66bd0013c7ef104d896c3dc7d3ad83b4c6bc055 market_resolved 560 85,287 43-43 a3d6934cfcde129f803d7d1ba9ba22fc21a9f4043778c947abeca8326aa8baf4 new_market 401 44,395 44-44 166022563f69781615f27077226ae11006dc9240bd697d27a8943de16d7cc303 price_change 103,877,058 1,043,285,540 45-441 ecfb21e729720593d002976cbc1b6dba4765509802fe790c1491aa31f83ef4a7 tick_size_change 3,032 111,751 442-442 5cafd48ac9a98d85b3bb12794f18cc73e70ae86983782a119dacf6b3a54f815e EVENT MIX count share price_change 103,877,058 90.60% best_bid_ask 10,504,742 9.16% book 220,194 0.19% last_trade_price 52,072 0.05% tick_size_change 3,032 <0.01% market_resolved 560 <0.01% new_market 401 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,504,950 10,504,742 208 74 FULL book 220,198 220,194 4 52,980 FULL last_trade_price 52,072 52,072 0 1 FULL market_resolved 560 560 0 0 FULL new_market 401 401 0 0 FULL price_change 103,878,518 103,877,058 1,460 101 FULL tick_size_change 3,032 3,032 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 10,498,361 955 76ms 97ms 386ms 20.3s 0 transport_latency_assumed best_bid_ask h 10,504,324 84,101 19ms 33ms 149ms 9.6s 0 transport_latency_assumed best_bid_ask i 10,504,262 22,979 23ms 42ms 153ms 5.3s 0 transport_latency_assumed best_bid_ask k 10,504,291 404,722 13ms 23ms 126ms 7.9s 0 transport_latency_assumed best_bid_ask m 10,504,696 9,991,985 5ms 10ms 87ms 3.4s 0 transport_latency_assumed book g 214,671 113,257 12.2s 8.7h 37.6d 125.5d 0 book_staleness book h 104,927 1,953 22ms 66ms 633ms 106.8d 0 book_staleness book i 104,937 1,150 27ms 83ms 1.2s 106.9d 0 book_staleness book k 105,671 5,999 17ms 82ms 2.4s 106.9d 0 book_staleness book m 104,945 97,835 7ms 15ms 234ms 8.3h 0 book_staleness last_trade_price g 50,535 6 82ms 1.6s 14.2s 20.3s 0 transport_latency_assumed last_trade_price h 52,058 761 20ms 59ms 499ms 5.9s 0 transport_latency_assumed last_trade_price i 52,053 273 27ms 76ms 851ms 3.3s 0 transport_latency_assumed last_trade_price k 52,052 2,453 15ms 62ms 210ms 2.2s 0 transport_latency_assumed last_trade_price m 52,051 48,579 6ms 13ms 146ms 1.3s 0 transport_latency_assumed market_resolved g 515 not meas. 81ms 257ms 56.8s 56.9s 0 transport_latency_assumed market_resolved h 515 8 27ms 99ms 56.0s 1.0min 0 transport_latency_assumed market_resolved i 515 not meas. 39ms 40.9s 52.3s 54.2s 0 transport_latency_assumed market_resolved k 515 60 15ms 38ms 55.9s 55.9s 0 transport_latency_assumed market_resolved m 515 492 6ms 36.7s 48.1s 50.7s 0 transport_latency_assumed new_market g 283 28 121ms 9.2s 24.7s 1.7min 0 transport_latency_assumed new_market h 283 34 58ms 9.7s 34.7s 1.6min 0 transport_latency_assumed new_market i 283 35 58ms 10.6s 24.8s 1.5min 0 transport_latency_assumed new_market k 283 39 71ms 8.5s 1.4min 1.6min 0 transport_latency_assumed new_market m 283 265 15ms 8.6s 22.8s 1.6min 0 transport_latency_assumed price_change g 103,696,290 10,674 77ms 147ms 4.5s 20.3s 0 transport_latency_assumed price_change h 103,866,302 1,080,452 19ms 34ms 327ms 13.0s 0 transport_latency_assumed price_change i 103,837,436 284,296 23ms 44ms 436ms 5.6s 0 transport_latency_assumed price_change k 103,852,366 4,740,918 13ms 28ms 233ms 8.7s 0 transport_latency_assumed price_change m 103,856,546 97,760,718 5ms 11ms 177ms 3.9s 0 transport_latency_assumed tick_size_change g 3,032 not meas. 76ms 93ms 180ms 496ms 0 transport_latency_assumed tick_size_change h 3,032 70 19ms 33ms 69ms 140ms 0 transport_latency_assumed tick_size_change i 3,032 16 24ms 43ms 92ms 155ms 0 transport_latency_assumed tick_size_change k 3,032 89 13ms 24ms 118ms 129ms 0 transport_latency_assumed tick_size_change m 3,032 2,857 5ms 10ms 90ms 193ms 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-02/09/2026-10-02T09.parquet sha256sum 2026-10-02T09.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.