Hour audit: 2026-08-29T21
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.
1 finding
- a machine expected this hour contributed nothing. Of the 5 machines expected to be capturing this hour, 1 contributed no rows: b. The hour is still whole on minutes; it simply rests on 4 machines rather than 5.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-08-29T21 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-29T21:00:00.006995346+00:00 · last event 2026-08-29T21:59:59.999990267+00:00
VOLUME 114,620,818 rows · 1,186,219,931 bytes (1.10 GiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured h: 113,815,437 · c: 112,909,064 · e: 110,883,080 · a: 104,488,484 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 2,946,502 (2.57%) · c: 71,380 (0.06%) · e: 110,881,894 (96.74%) · a: 721,042 (0.63%) (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 114,620,818 rows exactly, so those pairs supplied none
5 expected (abceh), 1 contributed nothing: b
INTEGRITY sha256 902dbda352b4d94b0f5bfc7f8ef73bb7bab79732e2d1b9a0fc0018ffd94db9ee
the corpus checksum ledger names this file with the same digest
joined 114,622,032 to merged 114,620,818, minus 1,214 (minus 0.0011%)
boundary drops 1,214 · 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-08-30T14:03:56Z as aceh
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 7/8 pass, 1 finding
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
FINDING a machine expected this hour contributed nothing
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 9,919,105 110,789,503 0-37 51f4378a91507dc7955caabb82f0ec81456d8eda571f17e91b5d365f7aea22be book 889,356 61,698,682 38-41 73cdd33795d7c09ee6f72f0a08a48b9a9de79d0ca4dccd720688a3327aacd5f6 last_trade_price 56,576 3,256,799 42-42 bceb802b358cebe054715666c871183a64f8d72dd71c23e4c9631d27a0acd022 market_resolved 2,617 391,336 43-43 b583ff0cd5cbdf3444050722071ea97aa1d5cc2988f8c236af07f3b8d8c3ae3c new_market 2,978 258,249 44-44 d8def5226f2266269c309b9bffc105687ab7f0809b28b55fde0fcc68ffc3c693 price_change 103,745,038 1,008,333,243 45-440 bbfa6090f345b08f39452005116b45e8084202226c3eafb73c815db0b4548194 tick_size_change 5,148 188,691 441-441 a75995ffe084c259c64f22a01e0de193f1cd51a308707cb9af6e7fedb6fdbfb7 EVENT MIX count share price_change 103,745,038 90.51% best_bid_ask 9,919,105 8.65% book 889,356 0.78% last_trade_price 56,576 0.05% tick_size_change 5,148 <0.01% new_market 2,978 <0.01% market_resolved 2,617 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,919,243 9,919,105 138 73,226 PARTIAL book 889,368 889,356 12 177,926 PARTIAL last_trade_price 56,576 56,576 0 3,850 PARTIAL market_resolved 2,617 2,617 0 2,410 PARTIAL new_market 2,978 2,978 0 1,636 PARTIAL price_change 103,746,102 103,745,038 1,064 136,961 PARTIAL tick_size_change 5,148 5,148 0 1,287 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 9,079,615 228 34ms 45ms 352ms 17.5s 0 transport_latency_assumed best_bid_ask c 9,853,781 1,844 4ms 8ms 161ms 5.3s 0 transport_latency_assumed best_bid_ask e 9,736,944 9,736,812 44ms 103ms 1.1s 25.2s 0 transport_latency_assumed best_bid_ask h 9,916,279 180,221 12ms 18ms 225ms 29.1s 0 transport_latency_assumed book a 846,747 713,478 1.5min 5.5h 27.4d 92.0d 0 book_staleness book c 166,590 49,889 9ms 6.9min 21.2d 92.0d 0 book_staleness book e 121,068 121,068 65ms 4.3s 18.3min 2.5d 0 book_staleness book h 119,628 4,921 18ms 137ms 20.4s 73.5d 0 book_staleness last_trade_price a 50,095 3 45ms 1.1s 7.1s 17.5s 0 transport_latency_assumed last_trade_price c 56,252 38 9ms 38ms 254ms 5.3s 0 transport_latency_assumed last_trade_price e 55,474 55,474 61ms 2.8s 10.6s 24.7s 0 transport_latency_assumed last_trade_price h 56,529 1,061 17ms 92ms 839ms 8.0s 0 transport_latency_assumed market_resolved a 2,352 167 81ms 428ms 9.0min 9.2min 0 transport_latency_assumed market_resolved c 2,403 6 4ms 12ms 31.0s 2.2min 0 transport_latency_assumed market_resolved e 2,402 2,402 67ms 369ms 44.2s 2.4min 0 transport_latency_assumed market_resolved h 2,410 42 18ms 59ms 532ms 1.0min 0 transport_latency_assumed new_market a 2,134 526 418ms 4.4min 5.0min 36.7min 0 transport_latency_assumed new_market c 1,636 320 72ms 21.1s 31.9s 26.2min 0 transport_latency_assumed new_market e 1,636 1,636 249ms 20.1s 27.8s 14.0min 0 transport_latency_assumed new_market h 1,636 496 152ms 19.1s 28.6s 42.2min 0 transport_latency_assumed price_change a 94,502,629 6,640 35ms 53ms 584ms 17.5s 0 transport_latency_assumed price_change c 102,823,278 19,283 4ms 8ms 169ms 9.0s 0 transport_latency_assumed price_change e 100,960,464 100,959,410 44ms 138ms 3.2s 25.2s 0 transport_latency_assumed price_change h 103,713,807 2,759,705 12ms 20ms 243ms 29.5s 0 transport_latency_assumed tick_size_change a 4,912 not meas. 35ms 44ms 256ms 485ms 0 transport_latency_assumed tick_size_change c 5,124 not meas. 4ms 8ms 252ms 686ms 0 transport_latency_assumed tick_size_change e 5,092 5,092 45ms 112ms 312ms 4.9s 0 transport_latency_assumed tick_size_change h 5,148 56 12ms 17ms 252ms 2.0s 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-08-29/21/2026-08-29T21.parquet sha256sum 2026-08-29T21.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.