Hour audit: 2026-10-02T00
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-02T00 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-02T00:00:00.000769149+00:00 · last event 2026-10-02T00:59:59.999725867+00:00
VOLUME 124,456,502 rows · 1,324,850,748 bytes (1.23 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured m: 123,395,107 · h: 123,342,090 · g: 123,336,388 · i: 123,334,623 · k: 112,032,307 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 121,028,201 (97.25%) · h: 532,308 (0.43%) · g: 92,048 (0.07%) · i: 190,730 (0.15%) · k: 2,613,215 (2.10%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 124,456,502 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 347d07d30532b47d8ed7a16fcd68380629a7349520b4aad65009214e5d765d85
the corpus checksum ledger names this file with the same digest
joined 124,458,615 to merged 124,456,502, minus 2,113 (minus 0.0017%)
boundary drops 2,113 · 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-02T02:48:02Z 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,388,695 133,742,286 0-43 c75ad98e220b1b9ce00d66b25dac98dfb5ca82fe2c991dda674dea40c24fc003 book 1,226,575 79,628,119 44-48 1ba7306fefa61eca3e928605857934440f9e095efb1639acdc24f284417b4a2b last_trade_price 57,300 3,173,465 49-49 095f65dd170db1b08d2e0bd7b1b61f3f399a6e561a57cab65d955ae77d7b9747 market_resolved 1,414 180,509 50-50 8625a6ea5231c38bc37a0075c3150b88d3089749f42b01397f99521facea2665 new_market 1,104 105,022 51-51 127f8f56251830d50d3373afad461def1c6e657e456e235aa1134c4acb625386 price_change 111,778,958 1,106,512,696 52-478 febc52e920f8f736a903baf41fd57e35d487ee213a7171e65f8ae3f1a5e12c02 tick_size_change 2,456 90,674 479-479 fadd1e84fa72028dc8bd78d10e27b6eb585e5c02c6ec851f32941a706589438f EVENT MIX count share price_change 111,778,958 89.81% best_bid_ask 11,388,695 9.15% book 1,226,575 0.99% last_trade_price 57,300 0.05% tick_size_change 2,456 <0.01% market_resolved 1,414 <0.01% new_market 1,104 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,388,873 11,388,695 178 13,684 FULL book 1,227,015 1,226,575 440 233,900 FULL last_trade_price 57,301 57,300 1 187 FULL market_resolved 1,414 1,414 0 9 FULL new_market 1,104 1,104 0 18 FULL price_change 111,780,452 111,778,958 1,494 27,185 FULL tick_size_change 2,456 2,456 0 95 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 11,383,816 1,833 76ms 91ms 363ms 18.8s 0 transport_latency_assumed best_bid_ask h 11,385,845 46,258 17ms 31ms 395ms 39.8s 0 transport_latency_assumed best_bid_ask i 11,386,368 15,170 27ms 41ms 209ms 7.3s 0 transport_latency_assumed best_bid_ask k 10,261,876 149,551 13ms 22ms 149ms 14.2s 0 transport_latency_assumed best_bid_ask m 11,387,429 11,175,883 5ms 8ms 129ms 5.0s 0 transport_latency_assumed book g 207,635 73,136 96ms 17.6h 32.4d 125.1d 0 book_staleness book h 163,190 34,363 25ms 5.7h 24.6d 125.1d 0 book_staleness book i 148,497 20,906 39ms 2.2h 24.5d 106.6d 0 book_staleness book k 1,123,110 926,818 10.9min 3.4d 40.5d 125.1d 0 book_staleness book m 188,026 171,352 8ms 13.8h 40.4d 125.1d 0 book_staleness last_trade_price g 56,824 6 77ms 96ms 363ms 18.7s 0 transport_latency_assumed last_trade_price h 57,279 253 19ms 33ms 557ms 9.1s 0 transport_latency_assumed last_trade_price i 57,274 55 37ms 42ms 161ms 3.3s 0 transport_latency_assumed last_trade_price k 49,451 971 14ms 23ms 134ms 5.1s 0 transport_latency_assumed last_trade_price m 57,278 56,015 6ms 9ms 38ms 1.2s 0 transport_latency_assumed market_resolved g 1,094 1 77ms 202ms 47.5s 47.6s 0 transport_latency_assumed market_resolved h 1,094 23 18ms 39ms 48.4s 48.5s 0 transport_latency_assumed market_resolved i 1,094 2 39ms 68ms 48.3s 57.7s 0 transport_latency_assumed market_resolved k 1,165 312 17ms 5.5min 8.5min 10.9min 0 transport_latency_assumed market_resolved m 1,094 1,076 6ms 13ms 47.1s 57.2s 0 transport_latency_assumed new_market g 673 70 142ms 58.3s 2.2min 2.7min 0 transport_latency_assumed new_market h 664 99 148ms 57.6s 2.3min 2.7min 0 transport_latency_assumed new_market i 664 191 133ms 1.1min 2.3min 2.8min 0 transport_latency_assumed new_market k 704 175 131ms 1.6min 7.2min 7.2min 0 transport_latency_assumed new_market m 664 569 38ms 50.0s 2.3min 2.7min 0 transport_latency_assumed price_change g 111,683,894 17,002 76ms 93ms 468ms 18.9s 0 transport_latency_assumed price_change h 111,731,562 451,296 18ms 31ms 343ms 39.9s 0 transport_latency_assumed price_change i 111,738,278 154,406 30ms 41ms 216ms 10.5s 0 transport_latency_assumed price_change k 100,593,913 1,535,368 13ms 22ms 149ms 17.6s 0 transport_latency_assumed price_change m 111,758,160 109,620,886 5ms 8ms 103ms 5.0s 0 transport_latency_assumed tick_size_change g 2,452 not meas. 76ms 90ms 162ms 243ms 0 transport_latency_assumed tick_size_change h 2,456 16 17ms 30ms 59ms 2.0s 0 transport_latency_assumed tick_size_change i 2,448 not meas. 37ms 41ms 64ms 138ms 0 transport_latency_assumed tick_size_change k 2,088 20 13ms 18ms 79ms 120ms 0 transport_latency_assumed tick_size_change m 2,456 2,420 5ms 8ms 25ms 111ms 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/00/2026-10-02T00.parquet sha256sum 2026-10-02T00.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.