Hour audit: 2026-08-27T20
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-27T20 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-08-27T20:00:00.032747317+00:00 · last event 2026-08-27T20:59:59.999964521+00:00
VOLUME 96,952,534 rows · 1,074,164,655 bytes (1.00 GiB) · 7 products, all holding rows
WITNESSES abceh — 5 machines contributed rows
captured c: 95,719,691 · h: 95,600,993 · e: 93,042,414 · b: 87,775,577 · a: 87,721,350 (each machine's own feed; these overlap and do not sum to the file)
supplied c: not measured · h: not measured · e: not measured · b: not measured · a: not measured (rows of the merged file that came from it; these partition it)
INTEGRITY sha256 fc74362487c2321c708a1d4527a714bacc0d5483cdea8d4013ee071a864a218f
the corpus checksum ledger names this file with the same digest
joined 96,954,274 to merged 96,952,534, minus 1,740 (minus 0.0018%)
boundary drops 1,740 · 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 7,580,590 91,682,177 0-28 d61767c54bb4f0cd8a5f0755104d466bbcd6968439bcfa873e5124f1a3bffcc1 book 1,410,752 82,742,167 29-34 0583e8aec111ca8138f1dcdd2f8ed2e62d3334063c2875f7b8002988c5c93a53 last_trade_price 63,827 3,636,169 35-35 d56b152b8f58bbbf3a9358da4bdb79efd0447c2f595c02b4cb8f7803bee98484 market_resolved 1,850 254,629 36-36 2b7f193ace8d842d917a46dff6fd2ec889314aa003207c132deefcc37fed815a new_market 3,085 253,037 37-37 5f95fe03633abf6409a34ea7e3c88b5070424c183153003013e29f0709a62df0 price_change 87,888,230 894,332,055 38-373 6ed366a3a154460140fb2e001cb77ac7479f066a64d45240135bc369fe340ccd tick_size_change 4,200 156,349 374-374 a758863aed89b7b200beccab68623804bf59c110ff4a64f62ab15ebcfcba5356 EVENT MIX count share price_change 87,888,230 90.65% best_bid_ask 7,580,590 7.82% book 1,410,752 1.46% last_trade_price 63,827 0.07% tick_size_change 4,200 <0.01% new_market 3,085 <0.01% market_resolved 1,850 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 7,580,768 7,580,590 178 1,623 FULL book 1,410,826 1,410,752 74 183,762 FULL last_trade_price 63,827 63,827 0 276 FULL market_resolved 1,850 1,850 0 55 FULL new_market 3,085 3,085 0 5 FULL price_change 87,889,718 87,888,230 1,488 1,141 FULL tick_size_change 4,200 4,200 0 151 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/20/2026-08-27T20.parquet sha256sum 2026-08-27T20.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.