Hour audit: 2026-08-28T12
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-28T12 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-08-28T12:00:00.034281353+00:00 · last event 2026-08-28T12:59:59.999911221+00:00
VOLUME 89,069,985 rows · 928,871,290 bytes (885.84 MiB) · 7 products, all holding rows
WITNESSES abceh — 5 machines contributed rows
captured c: 89,028,625 · h: 89,025,945 · a: 88,930,525 · b: 88,887,314 · e: 88,641,540 (each machine's own feed; these overlap and do not sum to the file)
supplied c: not measured · h: not measured · a: not measured · b: not measured · e: not measured (rows of the merged file that came from it; these partition it)
INTEGRITY sha256 c63bb06c27625b2795a4c88019bab14585f82a9910b345493aff73fa5854f458
the corpus checksum ledger names this file with the same digest
joined 89,070,911 to merged 89,069,985, minus 926 (minus 0.0010%)
boundary drops 926 · 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 8,530,960 102,056,973 0-32 78016c388ab1b9c61d7a63d58717f759dcaa4bc5457ba4c37d9bc3f382c6654b book 179,868 17,841,553 33-33 2e48a0a2007979836c2591aa615cc39e2bc7911aa86716c538cad6e85701d940 last_trade_price 67,594 3,803,859 34-34 1c21298f54b39f2524f649f4e678a36d2f7059b4678141c157082a144cf68c32 market_resolved 739 108,449 35-35 856edd8511eb3e6db7876147bcda1fad4c1fa04b57d3aafa25c24654f9474d5c new_market 1,268 126,381 36-36 6c0648c9f0a09095738e4b683730788ad3e6150eb248f5ccb7b5bbe885e58711 price_change 80,286,512 803,804,110 37-343 7a0036f770823c16c60b9d5813acdc551c1349fb02442d1a38a64b8d8692a775 tick_size_change 3,044 110,997 344-344 49be29a47062d57f18cfc0ea6c665c8de220e131aa736ae7d5b9fe63095f6f7e EVENT MIX count share price_change 80,286,512 90.14% best_bid_ask 8,530,960 9.58% book 179,868 0.20% last_trade_price 67,594 0.08% tick_size_change 3,044 <0.01% new_market 1,268 <0.01% market_resolved 739 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,531,034 8,530,960 74 145 FULL book 179,870 179,868 2 16,559 FULL last_trade_price 67,594 67,594 0 1 FULL market_resolved 739 739 0 2 FULL new_market 1,268 1,268 0 0 FULL price_change 80,287,362 80,286,512 850 53 FULL tick_size_change 3,044 3,044 0 0 FULL
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-28/12/2026-08-28T12.parquet sha256sum 2026-08-28T12.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.