Hour audit: 2026-08-22T13
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.
3 checks 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-22T13 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-08-22T13:00:00.000238+00:00 · last event 2026-08-22T13:59:59.999940+00:00
VOLUME 46,837,802 rows · 445,088,867 bytes (424.47 MiB) · 7 products, all holding rows
WITNESSES not measured (this hour carries no per-machine row accounting)
INTEGRITY sha256 8c9465a8401bb1eda827fed057ae4922850b47867a6beffa01ce625c9e1a1814
the corpus checksum ledger names this file with the same digest
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 5/8 pass, 3 not evaluated
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
SKIPPED the merge delta could not be checked
SKIPPED which machines were expected is not published beside this hour
PASS the checksum ledger names this file
PASS the hour is whole
SKIPPED whether a boundary guard ran is not recorded
UPSTREAM an incident recorded by the venue intersects this hour: Venue paused trading for about forty minutes, 2026-08-22T13:13Z to 2026-08-22T13:51ZThe 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 4,257,783 45,565,472 0-16 8b806e25391c1717ffe1fe5beb61e11e3386d704580754cb2c7e673434dc7d34 book 558,265 48,128,857 17-19 bea90203ec2dcd4273ecd4baca58f73034471c101c12b64f880924ea4f9041c2 last_trade_price 41,641 2,378,193 20-20 ef4090be0cbf956b0ce99b1a96b4854957f43a65b0393875f563b4dbf08f472c market_resolved 2,793 378,601 21-21 7310b4481e367364d08abdabb5833d3da48121ccdcd2c1a18ce4480070efc26d new_market 1,972 239,632 22-22 1e945ba1c02c059fdfdb71b0e1dbc0d01b258c0f6d8a44205a5fc89d68e2b31b price_change 41,970,168 347,736,006 23-183 ea80d239f91358586e0cc34d0db314c83276b23120367f0bcca15bcf87d3a3d9 tick_size_change 5,180 177,327 184-184 593d0a7c1bacbbfa0484bd7511019024d607d051bdebd3fbd378ace1f3e3c646 EVENT MIX count share price_change 41,970,168 89.61% best_bid_ask 4,257,783 9.09% book 558,265 1.19% last_trade_price 41,641 0.09% tick_size_change 5,180 0.01% market_resolved 2,793 <0.01% new_market 1,972 <0.01%
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-22/13/2026-08-22T13.parquet sha256sum 2026-08-22T13.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.