Hour audit: 2026-09-29T22
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-09-29T22 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-29T22:00:00.000509832+00:00 · last event 2026-09-29T22:59:59.999680713+00:00
VOLUME 104,774,793 rows · 1,089,088,678 bytes (1.01 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured k: 104,669,067 · c: 104,659,248 · h: 104,541,081 · i: 104,529,667 · g: 104,404,229 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 8,073,471 (7.71%) · c: 93,053,983 (88.81%) · h: 2,212,558 (2.11%) · i: 1,398,004 (1.33%) · g: 36,777 (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 104,774,793 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 a28c1b402fe8b89af33aff76f9cf450e8b3f311999eff73827b4190c44be4686
the corpus checksum ledger names this file with the same digest
joined 104,776,004 to merged 104,774,793, minus 1,211 (minus 0.0012%)
boundary drops 1,211 · 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-09-30T00:49:16Z as cghik
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,616,674 125,990,383 0-40 4357ac78da2ce18a41cace59a5ec0609f1857509a5c7155707127a90cf9f0d56 book 130,678 13,159,405 41-41 ccf5948546eb952ff639533e25206e9e6a86713b49b397f1d07fd400327aaef7 last_trade_price 43,169 2,569,398 42-42 2d6f470167e799012974f76f7227ee5533db1ae8db4b6ef91e40c59db012071f market_resolved 2,695 400,767 43-43 7fd93c09c42e23ceb60a9e211e0b5eca54d60c350195762290b6e64099de5771 new_market 1,405 137,697 44-44 3837a7d515e876b9b943e9ee7abf48398c3d2376fcdf605af65b9ac5eefe28ba price_change 93,977,652 945,542,004 45-403 49609d87f9406e92caf7d93944c4623ada5c641721a3b2b6e1a1b21afc8f0504 tick_size_change 2,520 93,614 404-404 a50a65b54666ce7294407e6a663621857452967a8104c152d3dfa273526f8956 EVENT MIX count share price_change 93,977,652 89.69% best_bid_ask 10,616,674 10.13% book 130,678 0.12% last_trade_price 43,169 0.04% market_resolved 2,695 <0.01% tick_size_change 2,520 <0.01% new_market 1,405 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,616,827 10,616,674 153 190 FULL book 130,682 130,678 4 14,933 FULL last_trade_price 43,169 43,169 0 7 FULL market_resolved 2,695 2,695 0 1 FULL new_market 1,405 1,405 0 0 FULL price_change 93,978,706 93,977,652 1,054 362 FULL tick_size_change 2,520 2,520 0 1 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,615,168 9,548,425 5ms 17ms 197ms 6.4s 0 transport_latency_assumed best_bid_ask g 10,611,312 2,020 80ms 107ms 496ms 23.4s 0 transport_latency_assumed best_bid_ask h 10,606,481 194,391 17ms 30ms 274ms 1.7min 0 transport_latency_assumed best_bid_ask i 10,611,953 119,192 20ms 30ms 185ms 34.6s 0 transport_latency_assumed best_bid_ask k 10,614,451 752,646 12ms 22ms 163ms 43.1s 0 transport_latency_assumed book c 96,802 83,458 8ms 2.4s 2.8d 104.5d 0 book_staleness book g 94,334 7,310 96ms 6.6s 2.5d 104.5d 0 book_staleness book h 103,053 17,325 26ms 14.9min 9.1d 123.0d 0 book_staleness book i 90,928 5,998 23ms 253ms 21.9h 123.0d 0 book_staleness book k 96,537 16,587 16ms 1.7s 2.7d 104.4d 0 book_staleness last_trade_price c 42,849 37,067 6ms 40ms 324ms 1.8s 0 transport_latency_assumed last_trade_price g 42,054 32 94ms 519ms 10.0s 23.3s 0 transport_latency_assumed last_trade_price h 42,771 995 20ms 109ms 675ms 14.8s 0 transport_latency_assumed last_trade_price i 42,614 655 22ms 106ms 888ms 7.6s 0 transport_latency_assumed last_trade_price k 42,936 4,420 14ms 50ms 287ms 5.5s 0 transport_latency_assumed market_resolved c 2,514 2,225 5ms 24ms 50.7s 56.6s 0 transport_latency_assumed market_resolved g 2,514 not meas. 81ms 454ms 45.0s 52.4s 0 transport_latency_assumed market_resolved h 2,513 38 18ms 100ms 52.1s 2.3min 0 transport_latency_assumed market_resolved i 2,514 305 21ms 16.3s 50.6s 54.5s 0 transport_latency_assumed market_resolved k 2,514 127 13ms 535ms 51.9s 55.4s 0 transport_latency_assumed new_market c 871 354 118ms 16.8s 54.7s 1.8min 0 transport_latency_assumed new_market g 871 100 320ms 18.2s 43.6s 1.6min 0 transport_latency_assumed new_market h 871 253 172ms 14.5s 43.3s 1.5min 0 transport_latency_assumed new_market i 871 471 67ms 15.8s 1.1min 1.6min 0 transport_latency_assumed new_market k 871 227 151ms 14.4s 40.1s 1.8min 0 transport_latency_assumed price_change c 93,898,524 83,380,150 5ms 23ms 279ms 6.6s 0 transport_latency_assumed price_change g 93,650,624 27,311 81ms 154ms 2.3s 23.6s 0 transport_latency_assumed price_change h 93,782,876 1,999,503 18ms 40ms 438ms 1.8min 0 transport_latency_assumed price_change i 93,778,271 1,271,359 21ms 41ms 415ms 35.5s 0 transport_latency_assumed price_change k 93,909,238 7,299,329 13ms 28ms 257ms 56.8s 0 transport_latency_assumed tick_size_change c 2,520 2,304 5ms 14ms 140ms 898ms 0 transport_latency_assumed tick_size_change g 2,520 4 80ms 98ms 224ms 766ms 0 transport_latency_assumed tick_size_change h 2,516 53 18ms 29ms 167ms 384ms 0 transport_latency_assumed tick_size_change i 2,516 24 21ms 32ms 199ms 596ms 0 transport_latency_assumed tick_size_change k 2,520 135 12ms 21ms 131ms 431ms 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-09-29/22/2026-09-29T22.parquet sha256sum 2026-09-29T22.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.