Hour audit: 2026-09-15T19
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-15T19 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-15T19:00:00.000723487+00:00 · last event 2026-09-15T19:59:59.999960619+00:00
VOLUME 132,529,997 rows · 1,491,704,515 bytes (1.39 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 129,848,208 · e: 129,207,624 · f: 120,313,291 · g: 119,112,786 · c: 101,427,932 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 32,207,813 (24.30%) · e: 3,786,179 (2.86%) · f: 1,266,450 (0.96%) · g: 548,172 (0.41%) · c: 94,721,383 (71.47%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 3ce663655b78d0dfc90d7b6cf065e04685714461a521f8b4c67146190367b9d3
the corpus checksum ledger names this file with the same digest
joined 132,564,125 to merged 132,529,997, minus 34,128 (minus 0.0257%)
boundary drops 34,128 · 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-15T21:02:25Z as cefgh
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 our incident register was checked against the venue's own status feed at 2026-09-23T20:35Z and names no event in this hour. That is a statement about what they published, not a check that every message they sent reached us.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 12,164,355 145,814,876 0-46 d93805ca9b8e306ecadd8b77982594c539f3550d8874ef28687b3074c9909b37 book 2,934,263 124,941,210 47-58 ec7b91ed26ffda2c42fe1c515ffcbf5e62e08bb203d1b4093c52bca23e483b4b last_trade_price 66,705 3,793,314 59-59 3cf3ea486079a9276da0cd33a70ba7ffb96ad0254c6ca03eb9cb9ce65cf694cb market_resolved 1,712 174,341 60-60 debc06acb5c3a2801d886cf6438de8551f78d94b6ec5e4c0789045141e51cbc5 new_market 5,806 510,943 61-61 b30ac15594ca59b13c55a0416806c7319e616fff1e52f594e3673f161aa1a2ae price_change 117,350,776 1,214,732,440 62-509 3ccb7565fbde8beba16253b19267b3d412d6362039c777aeae591d9f2186e853 tick_size_change 6,380 229,876 510-510 260e6e7dbf0b792659b074fd096fa88359fe0850f4ca4101c7aab8150878f8c2 EVENT MIX count share price_change 117,350,776 88.55% best_bid_ask 12,164,355 9.18% book 2,934,263 2.21% last_trade_price 66,705 0.05% tick_size_change 6,380 <0.01% new_market 5,806 <0.01% market_resolved 1,712 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,164,635 12,164,355 280 4,123 FULL book 2,965,753 2,934,263 31,490 123,306 FULL last_trade_price 66,705 66,705 0 667 FULL market_resolved 1,712 1,712 0 96 FULL new_market 5,806 5,806 0 68 FULL price_change 117,353,134 117,350,776 2,358 1,324 FULL tick_size_change 6,380 6,380 0 370 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,325,903 8,741,235 6ms 18ms 197ms 8.9s 0 transport_latency_assumed best_bid_ask e 12,150,799 351,048 37ms 74ms 504ms 29.3s 0 transport_latency_assumed best_bid_ask f 11,239,310 82,532 45ms 73ms 433ms 24.5s 0 transport_latency_assumed best_bid_ask g 11,186,903 9,301 82ms 167ms 967ms 41.2s 0 transport_latency_assumed best_bid_ask h 12,161,214 2,980,239 20ms 47ms 487ms 46.4s 0 transport_latency_assumed book c 2,267,845 1,930,130 4.0min 2.9d 38.1d 108.9d 0 book_staleness book e 348,456 100,835 23.8s 37.3min 24.3d 108.9d 0 book_staleness book f 1,112,648 337,207 2.8min 1.7d 37.2d 108.9d 0 book_staleness book g 1,175,397 438,101 3.5min 1.7d 37.1d 108.9d 0 book_staleness book h 353,670 127,990 19.8s 40.9min 24.3d 108.9d 0 book_staleness last_trade_price c 51,891 48,429 12ms 59ms 354ms 5.0s 0 transport_latency_assumed last_trade_price e 64,051 1,325 70ms 2.2s 11.5s 29.3s 0 transport_latency_assumed last_trade_price f 60,233 402 72ms 1.5s 10.1s 24.5s 0 transport_latency_assumed last_trade_price g 57,702 110 121ms 3.7s 18.8s 41.2s 0 transport_latency_assumed last_trade_price h 66,562 16,439 30ms 139ms 811ms 39.0s 0 transport_latency_assumed market_resolved c 1,201 899 10ms 5.5min 13.1min 14.2min 0 transport_latency_assumed market_resolved e 1,000 20 42ms 358ms 29.5s 57.1s 0 transport_latency_assumed market_resolved f 1,108 319 68ms 4.5min 5.5min 6.6min 0 transport_latency_assumed market_resolved g 1,104 159 204ms 5.3min 14.6min 15.1min 0 transport_latency_assumed market_resolved h 1,000 315 24ms 138ms 29.4s 57.0s 0 transport_latency_assumed new_market c 3,896 2,566 133ms 5.8min 7.1min 8.5min 0 transport_latency_assumed new_market e 3,124 637 255ms 18.5s 2.0min 2.3min 0 transport_latency_assumed new_market f 3,118 498 221ms 2.0min 14.5min 14.6min 0 transport_latency_assumed new_market g 4,395 961 547ms 9.4min 11.1min 11.3min 0 transport_latency_assumed new_market h 3,124 1,144 183ms 19.1s 2.2min 2.4min 0 transport_latency_assumed price_change c 89,772,060 83,993,258 6ms 20ms 213ms 9.0s 0 transport_latency_assumed price_change e 116,633,814 3,332,213 38ms 124ms 3.7s 29.3s 0 transport_latency_assumed price_change f 107,890,806 845,486 45ms 108ms 2.8s 24.5s 0 transport_latency_assumed price_change g 106,681,185 99,536 85ms 261ms 7.0s 41.2s 0 transport_latency_assumed price_change h 117,256,258 29,080,283 20ms 55ms 595ms 1.2min 0 transport_latency_assumed tick_size_change c 5,136 4,866 6ms 13ms 54ms 230ms 0 transport_latency_assumed tick_size_change e 6,380 101 37ms 51ms 222ms 3.1s 0 transport_latency_assumed tick_size_change f 6,068 6 45ms 56ms 262ms 1.2s 0 transport_latency_assumed tick_size_change g 6,100 4 81ms 107ms 447ms 912ms 0 transport_latency_assumed tick_size_change h 6,380 1,403 19ms 36ms 220ms 4.8s 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-15/19/2026-09-15T19.parquet sha256sum 2026-09-15T19.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.