Hour audit: 2026-08-29T12
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.
1 check could not be evaluated for this hour, listed with the reason in the block below. A check we could not run is recorded as exactly that, and never counted as a pass.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-08-29T12 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-08-29T12:00:00.034941643+00:00 · last event 2026-08-29T12:59:59.999994468+00:00
VOLUME 96,578,251 rows · 1,035,239,884 bytes (987.28 MiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured c: 96,070,978 · a: 96,032,199 · h: 96,012,786 · e: 95,975,369 (each machine's own feed; these overlap and do not sum to the file)
supplied c: not measured · a: not measured · h: not measured · e: not measured (rows of the merged file that came from it; these partition it)
28 product-machine pairs publish no supplied count, and the figures above do not reconcile to the file's row count, so the split is incomplete by an unrecorded amount
INTEGRITY sha256 b7602a5fc7695135c955ac20093844b0e96637de86c0c84b85a781922eb209f5
the corpus checksum ledger names this file with the same digest
joined 96,579,181 to merged 96,578,251, minus 930 (minus 0.0010%)
boundary drops 930 · 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 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 not evaluated
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
SKIPPED which machines were expected is not published beside this hour
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 6,852,724 81,302,559 0-26 2c181c53e02f25ded15dc6ac00b228b4d01c21c6494d9fc530ca50551ff8470a book 900,466 68,241,958 27-30 ef4166681bf29aeea6e1e579055d30670c90d251dd5fdb696277f90d2ba3ee88 last_trade_price 66,514 3,825,543 31-31 4716fc5764a4476eea0bfb4b975db9d1335abe9540504e2a354622dd7393e1e3 market_resolved 1,310 209,277 32-32 38376d63430777fb60b9280995c1bee10ae9baac017c73d6ec0ca8e201708fa6 new_market 1,035 107,101 33-33 ef2a52b5febfd486d3cd8dc9404aa406cfc11b3389dc7664ad63e16923a9cdef price_change 88,749,494 880,205,004 34-372 df266fa2bc4e45e1f6dd104262ae586ce800d99e2a13fd387f022811af4e3267 tick_size_change 6,708 244,649 373-373 336bf0cc7580b1730e3522240878277eb782838cecac8e0b59747efe3bebc5a6 EVENT MIX count share price_change 88,749,494 91.89% best_bid_ask 6,852,724 7.10% book 900,466 0.93% last_trade_price 66,514 0.07% tick_size_change 6,708 <0.01% market_resolved 1,310 <0.01% new_market 1,035 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 6,852,762 6,852,724 38 71,974 PARTIAL book 900,480 900,466 14 181,513 PARTIAL last_trade_price 66,514 66,514 0 4,791 PARTIAL market_resolved 1,310 1,310 0 1,295 PARTIAL new_market 1,035 1,035 0 698 PARTIAL price_change 88,750,372 88,749,494 878 135,184 PARTIAL tick_size_change 6,708 6,708 0 1,677 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 6,850,528 not meas. 40ms 48ms 308ms 10.1s 0 not stated best_bid_ask c 6,851,526 not meas. 4ms 8ms 74ms 18.7s 0 not stated best_bid_ask e 6,848,910 not meas. 44ms 98ms 1.0s 24.5s 0 not stated best_bid_ask h 6,849,946 not meas. 12ms 18ms 156ms 1.8min 0 not stated book a 375,979 not meas. 28.9s 5.0h 21.0d 91.6d 0 not stated book c 419,944 not meas. 37.9s 5.1h 21.1d 91.6d 0 not stated book e 427,939 not meas. 39.8s 5.1h 21.0d 91.6d 0 not stated book h 360,696 not meas. 25.1s 5.0h 21.0d 91.6d 0 not stated last_trade_price a 66,493 not meas. 49ms 578ms 5.5s 10.1s 0 not stated last_trade_price c 66,495 not meas. 9ms 36ms 202ms 12.6s 0 not stated last_trade_price e 66,321 not meas. 60ms 1.8s 8.8s 24.5s 0 not stated last_trade_price h 66,481 not meas. 17ms 65ms 804ms 1.6min 0 not stated market_resolved a 1,295 not meas. 42ms 285ms 558ms 1.0min 0 not stated market_resolved c 1,295 not meas. 4ms 9ms 83ms 48.6s 0 not stated market_resolved e 1,295 not meas. 45ms 289ms 1.0s 1.8min 0 not stated market_resolved h 1,295 not meas. 13ms 62ms 125ms 547ms 0 not stated new_market a 698 not meas. 267ms 16.3s 21.7s 1.4min 0 not stated new_market c 698 not meas. 104ms 16.3s 24.6s 1.2min 0 not stated new_market e 698 not meas. 208ms 17.2s 22.5s 1.5min 0 not stated new_market h 698 not meas. 166ms 17.5s 27.2s 1.1min 0 not stated price_change a 88,730,506 not meas. 40ms 60ms 518ms 10.1s 0 not stated price_change c 88,724,312 not meas. 4ms 8ms 91ms 18.7s 0 not stated price_change e 88,623,498 not meas. 44ms 133ms 3.1s 24.5s 0 not stated price_change h 88,726,962 not meas. 12ms 19ms 184ms 1.8min 0 not stated tick_size_change a 6,700 not meas. 40ms 48ms 307ms 611ms 0 not stated tick_size_change c 6,708 not meas. 4ms 8ms 240ms 479ms 0 not stated tick_size_change e 6,708 not meas. 44ms 110ms 719ms 4.1s 0 not stated tick_size_change h 6,708 not meas. 12ms 18ms 292ms 842ms 0 not stated
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/12/2026-08-29T12.parquet sha256sum 2026-08-29T12.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.