Hour audit: 2026-10-01T18
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-01T18 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-01T18:00:00.000083878+00:00 · last event 2026-10-01T18:59:59.999937178+00:00
VOLUME 123,366,743 rows · 1,360,226,660 bytes (1.27 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured m: 122,500,016 · h: 122,449,973 · i: 122,402,923 · k: 117,173,618 · g: 116,517,659 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 115,167,782 (93.35%) · h: 1,408,072 (1.14%) · i: 3,368,542 (2.73%) · k: 2,574,172 (2.09%) · g: 848,175 (0.69%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 9f675a6ccbcf94c66699c81cdd4f8bea252fcb4b95aa94ae614fb2a8ed5074d4
the corpus checksum ledger names this file with the same digest
joined 123,371,841 to merged 123,366,743, minus 5,098 (minus 0.0041%)
boundary drops 5,098 · 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-01T21:11:49Z 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,169,780 123,405,258 0-38 c2c0478d2152e0d698824d558aeb6561ab5e0ba23e7c7a9b91e0e2336ae02d88 book 1,153,431 83,285,627 39-43 5b19ec87c0e4fdebbdf9a9334ea717a7053c6d434b295005c96700201be55070 last_trade_price 58,071 3,360,143 44-44 6399a6a3fafa387b2c31ba7c35f5d4830fe11112a340fb2202aa8562bb06cea8 market_resolved 944 146,260 45-45 317bc1aac56d7de7a8e1c79337d3c1c37aae9444b72a7f4880a61dc40828dd5b new_market 9,449 821,708 46-46 d0a85cfa8ff792dcb040c6da2a78b4ac4039e2b1abbc606dc613dd28fa7ef44f price_change 111,972,396 1,147,702,525 47-474 2e5d11c7731186578a96260db6ff9f4a7300102eb3b5a717f416afac261b2542 tick_size_change 2,672 98,757 475-475 62f0633b2040842e0dca7311a29e463f2ea80107cc24c4c6231105a4ea075f4b EVENT MIX count share price_change 111,972,396 90.76% best_bid_ask 10,169,780 8.24% book 1,153,431 0.93% last_trade_price 58,071 0.05% new_market 9,449 <0.01% tick_size_change 2,672 <0.01% market_resolved 944 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,169,966 10,169,780 186 1,205 FULL book 1,156,755 1,153,431 3,324 224,327 FULL last_trade_price 58,071 58,071 0 161 FULL market_resolved 944 944 0 61 FULL new_market 9,449 9,449 0 3 FULL price_change 111,973,984 111,972,396 1,588 1,141 FULL tick_size_change 2,672 2,672 0 43 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,663,772 23,766 75ms 102ms 664ms 33.1s 0 transport_latency_assumed best_bid_ask h 10,162,468 110,094 21ms 49ms 3.5s 2.3min 0 transport_latency_assumed best_bid_ask i 10,165,360 285,687 21ms 41ms 389ms 51.6s 0 transport_latency_assumed best_bid_ask k 9,692,981 174,903 16ms 37ms 430ms 57.8s 0 transport_latency_assumed best_bid_ask m 10,166,280 9,575,330 5ms 12ms 236ms 7.1s 0 transport_latency_assumed book g 738,155 532,869 9.7min 3.1d 40.2d 124.8d 0 book_staleness book h 316,833 91,653 49.8s 2.0d 40.2d 124.9d 0 book_staleness book i 229,838 47,947 339ms 21.3h 32.1d 124.8d 0 book_staleness book k 745,758 265,559 10.7min 3.1d 40.2d 124.8d 0 book_staleness book m 326,478 215,403 50.4s 1.7d 40.2d 124.9d 0 book_staleness last_trade_price g 54,187 134 76ms 185ms 4.2s 32.6s 0 transport_latency_assumed last_trade_price h 58,023 569 23ms 123ms 5.0s 54.6s 0 transport_latency_assumed last_trade_price i 58,055 1,364 26ms 81ms 944ms 51.6s 0 transport_latency_assumed last_trade_price k 54,686 1,212 17ms 44ms 515ms 16.9s 0 transport_latency_assumed last_trade_price m 58,038 54,792 6ms 13ms 272ms 6.4s 0 transport_latency_assumed market_resolved g 893 33 78ms 19.4s 5.2min 7.7min 0 transport_latency_assumed market_resolved h 899 14 23ms 348ms 52.8s 1.0min 0 transport_latency_assumed market_resolved i 898 35 30ms 246ms 39.2s 47.5s 0 transport_latency_assumed market_resolved k 842 22 18ms 537ms 56.1s 5.8min 0 transport_latency_assumed market_resolved m 900 840 5ms 91ms 39.4s 46.4s 0 transport_latency_assumed new_market g 5,186 1,167 170ms 15.2s 6.0min 450.0d 0 transport_latency_assumed new_market h 5,170 1,272 496ms 2.0min 3.0min 1.4d 0 transport_latency_assumed new_market i 5,170 2,040 294ms 2.0min 3.0min 1.4d 0 transport_latency_assumed new_market k 5,343 2,445 193ms 2.2min 7.1min 210.1d 0 transport_latency_assumed new_market m 5,170 2,525 9.7s 2.0min 2.9min 3.4min 0 transport_latency_assumed price_change g 106,052,898 290,198 75ms 120ms 1.2s 33.2s 0 transport_latency_assumed price_change h 111,903,908 1,204,414 22ms 70ms 4.1s 2.7min 0 transport_latency_assumed price_change i 111,940,930 3,031,416 23ms 46ms 605ms 52.2s 0 transport_latency_assumed price_change k 106,671,488 2,129,956 17ms 40ms 473ms 59.8s 0 transport_latency_assumed price_change m 111,940,478 105,316,412 5ms 13ms 258ms 8.1s 0 transport_latency_assumed tick_size_change g 2,568 8 75ms 95ms 603ms 903ms 0 transport_latency_assumed tick_size_change h 2,672 56 22ms 55ms 1.4s 45.7s 0 transport_latency_assumed tick_size_change i 2,672 53 23ms 56ms 450ms 4.1s 0 transport_latency_assumed tick_size_change k 2,520 75 16ms 43ms 195ms 1.0s 0 transport_latency_assumed tick_size_change m 2,672 2,480 5ms 15ms 331ms 517ms 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/18/2026-10-01T18.parquet sha256sum 2026-10-01T18.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.