Hour audit: 2026-10-03T04
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-03T04 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-03T04:00:00.000072794+00:00 · last event 2026-10-03T04:59:59.999903907+00:00
VOLUME 90,848,759 rows · 928,413,794 bytes (885.40 MiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured k: 90,714,303 · i: 90,696,730 · m: 90,690,934 · h: 90,664,506 · g: 90,567,632 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 2,439,352 (2.69%) · i: 509,831 (0.56%) · m: 87,139,886 (95.92%) · h: 722,198 (0.79%) · g: 37,492 (0.04%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 90,848,759 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 e3b11070eb2967396ca3a26abc293dee6e7c34e766a6d23f20e150bd724fdc6e
the corpus checksum ledger names this file with the same digest
joined 90,850,758 to merged 90,848,759, minus 1,999 (minus 0.0022%)
boundary drops 1,999 · 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-03T06:40:57Z 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 8,470,270 97,662,315 0-32 5bb7228895514208831b72f147b42741ff47140913f0bc86a6c948e3320e8ec6 book 159,676 16,637,646 33-33 d674a775170bfb1e7901d88e45b0de3eb7750a4eebea92ef4a4ad937891015f9 last_trade_price 42,208 2,479,314 34-34 14352c576492d2296411cf0d4cf7c995f942b5b8f4b382a0da43dbe976e2e716 market_resolved 1,099 161,336 35-35 8c254c5c504fd827fcf0649b089ffdde095893048e07f97ea4ee21be7952e476 new_market 3,608 326,371 36-36 6d59a08cfee49ce7dce8ff2fce3204fda907d54d7bb46ace377cda09f59766bd price_change 82,169,206 810,009,120 37-350 6dd36335c6268ddf402b85e18df9c42a51fd98bbfb3810070935824b29118a45 tick_size_change 2,692 97,407 351-351 9a277a2cfdfc40c9abfae824634f4fcf8282333ebdae4fb0218d108705cd8ba2 EVENT MIX count share price_change 82,169,206 90.45% best_bid_ask 8,470,270 9.32% book 159,676 0.18% last_trade_price 42,208 0.05% new_market 3,608 <0.01% tick_size_change 2,692 <0.01% market_resolved 1,099 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,470,458 8,470,270 188 135 FULL book 159,680 159,676 4 30,320 FULL last_trade_price 42,209 42,208 1 3 FULL market_resolved 1,099 1,099 0 0 FULL new_market 3,608 3,608 0 0 FULL price_change 82,171,012 82,169,206 1,806 256 FULL tick_size_change 2,692 2,692 0 1 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 8,467,526 2,256 78ms 101ms 891ms 37.1s 0 transport_latency_assumed best_bid_ask h 8,465,868 58,795 17ms 25ms 1.6s 1.8min 0 transport_latency_assumed best_bid_ask i 8,469,072 40,032 20ms 26ms 367ms 55.1s 0 transport_latency_assumed best_bid_ask k 8,468,200 212,523 13ms 21ms 563ms 1.1min 0 transport_latency_assumed best_bid_ask m 8,468,828 8,156,664 4ms 8ms 139ms 27.5s 0 transport_latency_assumed book g 100,780 12,580 90ms 1.6min 7.1d 107.7d 0 book_staleness book h 117,371 30,086 24ms 3.3h 25.8d 107.8d 0 book_staleness book i 93,694 7,360 23ms 586ms 1.1d 107.7d 0 book_staleness book k 105,896 20,710 18ms 21.5min 13.6d 126.3d 0 book_staleness book m 96,502 88,940 6ms 2.7s 17.7h 65.5d 0 book_staleness last_trade_price g 41,915 6 83ms 277ms 9.9s 37.2s 0 transport_latency_assumed last_trade_price h 42,096 507 18ms 50ms 1.4s 56.0s 0 transport_latency_assumed last_trade_price i 42,171 356 22ms 45ms 600ms 5.7s 0 transport_latency_assumed last_trade_price k 42,086 1,688 14ms 31ms 606ms 50.9s 0 transport_latency_assumed last_trade_price m 42,083 39,651 5ms 13ms 196ms 7.8s 0 transport_latency_assumed market_resolved g 1,001 38 79ms 474ms 51.5s 51.6s 0 transport_latency_assumed market_resolved h 1,001 12 18ms 24.7s 54.6s 1.4min 0 transport_latency_assumed market_resolved i 1,001 1 23ms 27.6s 47.4s 53.0s 0 transport_latency_assumed market_resolved k 1,001 67 15ms 20.4s 49.5s 56.9s 0 transport_latency_assumed market_resolved m 1,001 981 5ms 26.1s 47.1s 48.2s 0 transport_latency_assumed new_market g 2,156 338 677ms 38.7s 46.9s 1.7min 0 transport_latency_assumed new_market h 2,156 494 396ms 38.4s 43.2s 1.7min 0 transport_latency_assumed new_market i 2,156 842 447ms 38.3s 41.9s 1.8min 0 transport_latency_assumed new_market k 2,156 666 419ms 38.8s 45.2s 1.5min 0 transport_latency_assumed new_market m 2,156 1,268 150ms 37.4s 48.3s 1.7min 0 transport_latency_assumed price_change g 81,951,562 22,274 78ms 132ms 2.1s 37.2s 0 transport_latency_assumed price_change h 82,033,326 632,276 17ms 30ms 1.5s 2.2min 0 transport_latency_assumed price_change i 82,085,944 461,236 21ms 30ms 476ms 55.7s 0 transport_latency_assumed price_change k 82,092,272 2,203,598 13ms 24ms 581ms 1.2min 0 transport_latency_assumed price_change m 82,077,672 78,849,822 4ms 9ms 151ms 27.5s 0 transport_latency_assumed tick_size_change g 2,692 not meas. 77ms 91ms 164ms 1.4s 0 transport_latency_assumed tick_size_change h 2,688 28 17ms 25ms 374ms 7.1s 0 transport_latency_assumed tick_size_change i 2,692 4 21ms 25ms 46ms 93ms 0 transport_latency_assumed tick_size_change k 2,692 100 14ms 19ms 49ms 737ms 0 transport_latency_assumed tick_size_change m 2,692 2,560 4ms 8ms 52ms 69ms 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-03/04/2026-10-03T04.parquet sha256sum 2026-10-03T04.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.