Hour audit: 2026-10-01T09
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-01T09 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-01T09:00:00.000002131+00:00 · last event 2026-10-01T09:59:59.999975896+00:00
VOLUME 122,350,575 rows · 1,379,819,825 bytes (1.29 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured i: 120,609,323 · h: 117,790,350 · m: 115,692,123 · g: 114,040,369 · k: 109,899,309 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 14,183,784 (11.59%) · h: 22,381,742 (18.29%) · m: 50,414,922 (41.21%) · g: 4,308,721 (3.52%) · k: 31,061,406 (25.39%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 340079cf134117fb4f9bb71956634d7cceee43bb47e621214096c24421b70b39
the corpus checksum ledger names this file with the same digest
joined 122,353,906 to merged 122,350,575, minus 3,331 (minus 0.0027%)
boundary drops 3,331 · 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-01T12:10:33Z 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 11,436,690 143,096,377 0-43 cb008081662fbaea24b09ea558ee47a1ad4548bb0d0588b5a532fc57e6dc702e book 1,360,349 85,673,668 44-49 9c3f76953f617f9d662550ef7311cf90bd06a2935c0853caa64f7d45c13bde29 last_trade_price 47,591 2,818,426 50-50 53b3545cef7573026c853862fa12e5958ad19f59ea42f86319d1958cf9f4f2ab market_resolved 778 108,863 51-51 b172f01360cd2c9389a37df258357027a4159dff87ec37f9bc603e5c31cae034 new_market 345 36,736 52-52 7161269605a404532eba2931783a19494529316a184b6a3706212c691766218f price_change 109,502,018 1,146,585,815 53-470 ac4af7c71847c24727af3760a4cc9ceb8f422069aa3d95b5fc70c43e0e170997 tick_size_change 2,804 106,766 471-471 da0bb8352e17c0402b65988eb284ea0a8faba8e69e25faa2c401026d867f6bfd EVENT MIX count share price_change 109,502,018 89.50% best_bid_ask 11,436,690 9.35% book 1,360,349 1.11% last_trade_price 47,591 0.04% tick_size_change 2,804 <0.01% market_resolved 778 <0.01% new_market 345 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,436,969 11,436,690 279 997 FULL book 1,361,287 1,360,349 938 223,377 FULL last_trade_price 47,591 47,591 0 241 FULL market_resolved 778 778 0 41 FULL new_market 345 345 0 0 FULL price_change 109,504,132 109,502,018 2,114 18,538 FULL tick_size_change 2,804 2,804 0 51 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 11,416,502 384,198 194ms 587ms 1.3s 18.2s 0 transport_latency_assumed best_bid_ask h 11,427,494 2,024,431 40ms 456ms 1.1s 12.5s 0 transport_latency_assumed best_bid_ask i 11,423,515 1,198,409 121ms 504ms 1.2s 17.7s 0 transport_latency_assumed best_bid_ask k 10,317,907 2,740,573 73ms 450ms 1.1s 11.6s 0 transport_latency_assumed best_bid_ask m 11,415,100 5,089,079 90ms 462ms 1.2s 9.0s 0 transport_latency_assumed book g 311,606 150,693 4.2min 2.4d 39.8d 124.5d 0 book_staleness book h 296,576 155,680 3.0min 2.2d 39.8d 124.5d 0 book_staleness book i 283,537 133,190 2.2min 2.1d 39.8d 124.5d 0 book_staleness book k 1,087,025 742,593 1.5h 4.0d 39.9d 124.5d 0 book_staleness book m 293,397 178,193 3.3min 2.4d 39.8d 124.5d 0 book_staleness last_trade_price g 46,467 511 244ms 874ms 4.7s 17.4s 0 transport_latency_assumed last_trade_price h 47,187 8,543 22ms 565ms 3.7s 12.5s 0 transport_latency_assumed last_trade_price i 46,933 4,566 104ms 706ms 4.4s 17.8s 0 transport_latency_assumed last_trade_price k 43,358 9,385 95ms 663ms 2.6s 11.7s 0 transport_latency_assumed last_trade_price m 46,105 24,586 10ms 548ms 2.6s 9.0s 0 transport_latency_assumed market_resolved g 676 16 262ms 1.4s 54.5s 54.5s 0 transport_latency_assumed market_resolved h 676 95 148ms 1.1s 53.1s 53.1s 0 transport_latency_assumed market_resolved i 676 64 220ms 9.6s 43.2s 1.7min 0 transport_latency_assumed market_resolved k 695 285 127ms 4.3min 11.4min 11.4min 0 transport_latency_assumed market_resolved m 673 318 138ms 8.9s 42.4s 55.6s 0 transport_latency_assumed new_market g 227 19 350ms 11.1s 1.5min 1.8min 0 transport_latency_assumed new_market h 227 31 30ms 9.9s 58.1s 1.6min 0 transport_latency_assumed new_market i 227 37 34ms 10.1s 1.0min 1.6min 0 transport_latency_assumed new_market k 281 83 75ms 7.4min 7.5min 7.5min 0 transport_latency_assumed new_market m 227 175 18ms 8.8s 1.2min 1.7min 0 transport_latency_assumed price_change g 102,262,087 3,773,196 222ms 668ms 1.7s 18.5s 0 transport_latency_assumed price_change h 106,015,386 20,192,468 80ms 503ms 1.3s 12.5s 0 transport_latency_assumed price_change i 108,851,631 12,847,216 135ms 551ms 1.4s 18.2s 0 transport_latency_assumed price_change k 98,447,443 27,567,727 95ms 500ms 1.3s 11.9s 0 transport_latency_assumed price_change m 103,933,817 45,121,411 103ms 501ms 1.4s 9.1s 0 transport_latency_assumed tick_size_change g 2,804 88 254ms 588ms 1.1s 11.8s 0 transport_latency_assumed tick_size_change h 2,804 494 67ms 488ms 823ms 1.0s 0 transport_latency_assumed tick_size_change i 2,804 302 158ms 461ms 871ms 1.3s 0 transport_latency_assumed tick_size_change k 2,600 760 64ms 441ms 1.1s 1.3s 0 transport_latency_assumed tick_size_change m 2,804 1,160 134ms 478ms 1.1s 3.1s 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/09/2026-10-01T09.parquet sha256sum 2026-10-01T09.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.