Hour audit: 2026-10-01T19
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-01T19 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-01T19:00:00.000118351+00:00 · last event 2026-10-01T19:59:59.999975297+00:00
VOLUME 123,599,912 rows · 1,385,050,295 bytes (1.29 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured m: 122,241,034 · h: 122,238,024 · i: 122,124,220 · k: 116,639,305 · g: 110,466,728 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 109,044,321 (88.22%) · h: 951,027 (0.77%) · i: 9,929,395 (8.03%) · k: 2,414,404 (1.95%) · g: 1,260,765 (1.02%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 90f645250b3d693e7b046fce34ce299b917b8de31f4951c506332ea4ea70f00b
the corpus checksum ledger names this file with the same digest
joined 123,602,444 to merged 123,599,912, minus 2,532 (minus 0.0020%)
boundary drops 2,532 · 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-01T22:13: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 9,640,018 115,894,095 0-36 2ad939b86ed1f38cd613e13d5f3c60bdf04b3f102f65d035bfd5c47c29c2b66f book 1,825,516 102,822,238 37-43 807d9c7eaa0195c3735db38c01772077ab326be030a5960232977404cfe579db last_trade_price 63,100 3,604,056 44-44 ec46b3fb8f0b8fa5a7c5b6b433663fa83902efac619f5eb43eac1a419cfe4cc5 market_resolved 1,305 187,214 45-45 6047ccdf536db8d46ce6337a6da548d64b4f7e8ab1ab6b9799664f15e2894a48 new_market 5,303 445,463 46-46 3be464aa171b1b09890551044ab614c2ba15b5e241b34681c056ff313e71799a price_change 112,061,782 1,160,583,529 47-474 421c2d1bb966f18b134db0e33bc49066862c5fa4bf6b616bf145dbcb5f9b288c tick_size_change 2,888 107,136 475-475 f0d1ac1a052c3429c8064b5ef059f976e19a7a9d52c9b570ab815f6465e1d7a5 EVENT MIX count share price_change 112,061,782 90.66% best_bid_ask 9,640,018 7.80% book 1,825,516 1.48% last_trade_price 63,100 0.05% new_market 5,303 <0.01% tick_size_change 2,888 <0.01% market_resolved 1,305 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,640,224 9,640,018 206 1,917 FULL book 1,826,114 1,825,516 598 170,717 FULL last_trade_price 63,100 63,100 0 257 FULL market_resolved 1,305 1,305 0 2 FULL new_market 5,303 5,303 0 1 FULL price_change 112,063,510 112,061,782 1,728 1,508 FULL tick_size_change 2,888 2,888 0 104 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 8,715,950 9,451 75ms 94ms 534ms 30.8s 0 transport_latency_assumed best_bid_ask h 9,633,022 60,915 21ms 36ms 1.9s 1.6min 0 transport_latency_assumed best_bid_ask i 9,634,193 809,988 25ms 45ms 337ms 52.5s 0 transport_latency_assumed best_bid_ask k 9,184,998 168,143 16ms 30ms 349ms 1.2min 0 transport_latency_assumed best_bid_ask m 9,636,484 8,591,521 5ms 10ms 178ms 10.6s 0 transport_latency_assumed book g 1,301,860 1,137,136 47.4min 3.3d 40.2d 124.9d 0 book_staleness book h 536,693 147,395 9.7min 2.7d 40.2d 124.9d 0 book_staleness book i 454,706 118,545 5.7min 2.5d 40.2d 124.9d 0 book_staleness book k 869,184 174,816 27.7min 3.1d 40.2d 124.9d 0 book_staleness book m 534,535 247,624 11.0min 2.7d 40.2d 124.9d 0 book_staleness last_trade_price g 56,013 85 76ms 159ms 1.4s 26.0s 0 transport_latency_assumed last_trade_price h 63,054 451 24ms 49ms 2.1s 1.0min 0 transport_latency_assumed last_trade_price i 62,956 4,401 27ms 48ms 594ms 24.4s 0 transport_latency_assumed last_trade_price k 59,502 1,219 16ms 36ms 484ms 55.8s 0 transport_latency_assumed last_trade_price m 63,073 56,944 6ms 12ms 220ms 2.7s 0 transport_latency_assumed market_resolved g 1,201 71 79ms 44.0s 11.5min 11.5min 0 transport_latency_assumed market_resolved h 1,148 15 23ms 65ms 50.5s 53.1s 0 transport_latency_assumed market_resolved i 1,148 72 28ms 26.8s 51.5s 56.6s 0 transport_latency_assumed market_resolved k 1,149 94 17ms 116ms 4.6min 6.2min 0 transport_latency_assumed market_resolved m 1,148 1,053 6ms 26.5s 51.1s 56.8s 0 transport_latency_assumed new_market g 3,146 656 326ms 5.7min 6.7min 210.1d 0 transport_latency_assumed new_market h 2,767 810 245ms 35.3s 41.0s 210.1d 0 transport_latency_assumed new_market i 2,767 1,144 219ms 36.0s 43.1s 210.1d 0 transport_latency_assumed new_market k 2,893 1,050 225ms 4.6min 5.5min 154.0d 0 transport_latency_assumed new_market m 2,767 1,643 91ms 34.0s 41.6s 210.1d 0 transport_latency_assumed price_change g 100,386,050 113,362 75ms 99ms 849ms 30.9s 0 transport_latency_assumed price_change h 111,998,456 741,417 22ms 38ms 2.2s 1.7min 0 transport_latency_assumed price_change i 111,965,578 8,995,000 26ms 45ms 470ms 53.3s 0 transport_latency_assumed price_change k 106,518,883 2,069,064 16ms 33ms 419ms 1.2min 0 transport_latency_assumed price_change m 112,000,139 100,142,939 5ms 11ms 208ms 11.6s 0 transport_latency_assumed tick_size_change g 2,508 4 75ms 99ms 672ms 3.2s 0 transport_latency_assumed tick_size_change h 2,884 24 22ms 39ms 907ms 23.4s 0 transport_latency_assumed tick_size_change i 2,872 245 25ms 44ms 248ms 2.6s 0 transport_latency_assumed tick_size_change k 2,696 18 16ms 30ms 302ms 429ms 0 transport_latency_assumed tick_size_change m 2,888 2,597 5ms 9ms 151ms 247ms 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-01/19/2026-10-01T19.parquet sha256sum 2026-10-01T19.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.