Hour audit: 2026-08-27T13
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-27T13 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-08-27T13:00:00.038454109+00:00 · last event 2026-08-27T13:59:59.999998867+00:00
VOLUME 97,929,315 rows · 1,005,602,340 bytes (959.02 MiB) · 7 products, all holding rows
WITNESSES abceh — 5 machines contributed rows
captured h: 97,816,100 · c: 97,790,630 · a: 97,536,619 · b: 96,939,543 · e: 93,268,450 (each machine's own feed; these overlap and do not sum to the file)
supplied h: not measured · c: 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 f47095a91177a6cb9c4d87686e577cfbdc85fcb1362db1b9ba9eb5542eaf67e5
the corpus checksum ledger names this file with the same digest
joined 97,930,344 to merged 97,929,315, minus 1,029 (minus 0.0011%)
boundary drops 1,029 · 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 9,403,720 109,640,881 0-35 78a854bc274581ddcf79431efa017e154a5fff8e220942d49d6dde0a154def4e book 238,371 21,795,779 36-36 d52b095b30f8891cfad7d7ac4a0391d97f826554d962ef941815f3a613c11317 last_trade_price 78,086 4,372,094 37-37 61115067858e40e0d052f529fa2641ecc252d225406d70087cea056f24029e36 market_resolved 451 72,828 38-38 8f128019526ea05ccc0c3894fd2a646bc85179cdec9d8638e3770e0356b2942b new_market 529 59,016 39-39 4565285448aaf7b813578baac149e90976894e89626114ba7e96232df82f189a price_change 88,205,122 868,433,153 40-376 e0b0c6df0be73d0fcb323c6749d8460b83aa908b88225a2d2544cc08aa411797 tick_size_change 3,036 112,055 377-377 4a6d440af20a4e8c872bf9c68798f33f49e203179279786b5d61e7ecaa45613a EVENT MIX count share price_change 88,205,122 90.07% best_bid_ask 9,403,720 9.60% book 238,371 0.24% last_trade_price 78,086 0.08% tick_size_change 3,036 <0.01% new_market 529 <0.01% market_resolved 451 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,403,804 9,403,720 84 96 FULL book 238,475 238,371 104 20,218 FULL last_trade_price 78,087 78,086 1 2 FULL market_resolved 451 451 0 20 FULL new_market 529 529 0 0 FULL price_change 88,205,962 88,205,122 840 407 FULL tick_size_change 3,036 3,036 0 32 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-27/13/2026-08-27T13.parquet sha256sum 2026-08-27T13.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.