Hour audit: 2026-09-28T16
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-28T16 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-28T16:00:00.000146902+00:00 · last event 2026-09-28T16:59:59.999831494+00:00
VOLUME 113,669,228 rows · 1,286,225,181 bytes (1.20 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured i: 113,181,842 · h: 109,813,372 · k: 109,804,777 · g: 108,758,156 · c: 108,696,768 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 7,238,415 (6.37%) · h: 2,019,657 (1.78%) · k: 10,956,274 (9.64%) · g: 38,767 (0.03%) · c: 93,416,115 (82.18%) (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 113,669,228 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 a76411d9d7dc583a1a3c1ba225a183bc7165bb5f566817c20162c2760797f872
the corpus checksum ledger names this file with the same digest
joined 113,670,968 to merged 113,669,228, minus 1,740 (minus 0.0015%)
boundary drops 1,740 · 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-28T19:08:43Z 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,767,106 128,756,197 0-41 e012ec7fbdd547740c2c7954a52f9154399594357e1d5d70e206a510a5b4e315 book 565,715 56,266,783 42-44 099ce103898d85ac77a9a6cb9f81917c6a937ecfa0a087fcaa417d44a9820760 last_trade_price 60,862 3,486,186 45-45 bc6f8dde25d650286951e4d2c564d2b0c154db383bdeb2f8b149387a1e10a7f4 market_resolved 1,097 151,638 46-46 fb3e9bff5742b61c6a2669ee6d305ca84d84f442d761c0d066a7d1b0e1d1fec9 new_market 2,830 254,313 47-47 5f0b924342694da09face5e3ba6356bb34b278da7d178e7fbf8c35bd898a4ed7 price_change 102,268,906 1,095,911,147 48-438 34a1425fd64feb5dc0944fd1d2247c13eda8d6b5a4050f3d8cd0b168892a86fc tick_size_change 2,712 100,790 439-439 77093bc0d88aa13adf77230540a89d79146332ff367ec3950940608e5b2786e3 EVENT MIX count share price_change 102,268,906 89.97% best_bid_ask 10,767,106 9.47% book 565,715 0.50% last_trade_price 60,862 0.05% new_market 2,830 <0.01% tick_size_change 2,712 <0.01% market_resolved 1,097 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,767,310 10,767,106 204 4,566 FULL book 565,769 565,715 54 204,026 FULL last_trade_price 60,862 60,862 0 347 FULL market_resolved 1,097 1,097 0 87 FULL new_market 2,830 2,830 0 0 FULL price_change 102,270,388 102,268,906 1,482 7,146 FULL tick_size_change 2,712 2,712 0 65 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,283,856 8,894,671 6ms 19ms 208ms 9.7s 0 transport_latency_assumed best_bid_ask g 10,478,318 1,180 80ms 130ms 1.5s 36.4s 0 transport_latency_assumed best_bid_ask h 10,512,072 170,587 18ms 29ms 277ms 51.6s 0 transport_latency_assumed best_bid_ask i 10,764,251 697,831 17ms 27ms 191ms 37.8s 0 transport_latency_assumed best_bid_ask k 10,559,434 1,002,837 12ms 23ms 173ms 26.3s 0 transport_latency_assumed book c 539,138 505,138 26.3min 1.5d 37.1d 121.8d 0 book_staleness book g 129,076 15,758 97ms 1.8min 5.9d 103.2d 0 book_staleness book h 124,473 6,359 24ms 254ms 15.2h 103.3d 0 book_staleness book i 134,176 17,376 22ms 791ms 1.5d 103.2d 0 book_staleness book k 130,351 21,084 18ms 393ms 1.5d 103.2d 0 book_staleness last_trade_price c 58,581 50,318 7ms 29ms 332ms 1.9s 0 transport_latency_assumed last_trade_price g 54,679 25 92ms 2.0s 15.8s 35.9s 0 transport_latency_assumed last_trade_price h 58,132 1,136 20ms 102ms 934ms 27.9s 0 transport_latency_assumed last_trade_price i 60,664 3,063 20ms 164ms 1.3s 6.9s 0 transport_latency_assumed last_trade_price k 58,422 6,320 14ms 47ms 379ms 5.1s 0 transport_latency_assumed market_resolved c 1,022 899 7ms 8.3min 15.2min 15.3min 0 transport_latency_assumed market_resolved g 902 8 87ms 369ms 48.4s 2.3min 0 transport_latency_assumed market_resolved h 902 21 20ms 88ms 36.0s 2.5min 0 transport_latency_assumed market_resolved i 922 68 21ms 112ms 13.0s 38.6s 0 transport_latency_assumed market_resolved k 907 101 14ms 53ms 28.4s 34.4s 0 transport_latency_assumed new_market c 2,128 1,024 264ms 5.8min 10.3min 10.4min 0 transport_latency_assumed new_market g 1,591 198 362ms 25.9s 1.3min 5.3min 0 transport_latency_assumed new_market h 1,591 569 165ms 24.3s 1.2min 1.7min 0 transport_latency_assumed new_market i 1,591 604 116ms 35.3s 1.2min 1.7min 0 transport_latency_assumed new_market k 1,591 435 191ms 27.1s 1.3min 1.5min 0 transport_latency_assumed price_change c 97,809,407 83,961,835 6ms 22ms 248ms 9.9s 0 transport_latency_assumed price_change g 98,090,970 21,598 81ms 247ms 8.5s 36.5s 0 transport_latency_assumed price_change h 99,113,554 1,840,938 18ms 40ms 480ms 52.1s 0 transport_latency_assumed price_change i 102,217,526 6,519,304 18ms 40ms 480ms 39.6s 0 transport_latency_assumed price_change k 99,051,404 9,925,231 13ms 28ms 237ms 26.4s 0 transport_latency_assumed tick_size_change c 2,636 2,230 6ms 22ms 162ms 966ms 0 transport_latency_assumed tick_size_change g 2,620 not meas. 79ms 103ms 720ms 1.3s 0 transport_latency_assumed tick_size_change h 2,648 47 18ms 24ms 110ms 1.4s 0 transport_latency_assumed tick_size_change i 2,712 169 17ms 24ms 60ms 91ms 0 transport_latency_assumed tick_size_change k 2,668 266 12ms 21ms 93ms 182ms 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-28/16/2026-09-28T16.parquet sha256sum 2026-09-28T16.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.