Hour audit: 2026-08-19T03

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-19T03 · corpus v3 · verdict AUDIT PASS

COVERAGE    minutes present 60/60 · first event 2026-08-19T03:00:00.000945+00:00 · last event 2026-08-19T03:59:59.999964+00:00
VOLUME      81,334,982 rows · 699,368,806 bytes (666.97 MiB) · 7 products, all holding rows
WITNESSES   not measured (this hour carries no per-machine row accounting)
INTEGRITY   sha256 8f7eccc0c03b9b5df4326e13e3a3344732426c8c6c5de092dbd22e3a802bd1a6
            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    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,555,370     61,205,923         0-25  5f6104d04c1a3e132a0bcb86a8d2caeadfbca723c5f6ab95e0ddd8cb1dfc3e5a
book                     561,232     49,489,707        26-28  5ac82463e06174260bbbed06709673ae79c5e9b58c579bcfce5a3f0c66a622ad
last_trade_price          58,453      3,087,549        29-29  b58ba488102dd6565602a3189b9e0f5c4f400c5627758dc15aa4cd551c2fe9f2
market_resolved              674        109,084        30-30  273efb0d533cce82de37e38ca5a39de24f080acfc65992b7c0b221e4fc746a17
new_market                   333         44,102        31-31  e1a9721c0d2bd31d8d3f579d386dfce0e96ec560fc978090d2785116a49ff4d7
price_change          74,157,244    584,547,593       32-314  233e7a85b4954da70f30630290bd4d32a51db0b8fe8adf1673797af19b94eb0b
tick_size_change           1,676         57,641      315-315  f584bb70a55c97ee79d8fcf22a0aff1247d9ba340bc1014bb7c7577bff4eec81

EVENT MIX                  count    share
price_change          74,157,244   91.18%
best_bid_ask           6,555,370    8.06%
book                     561,232    0.69%
last_trade_price          58,453    0.07%
tick_size_change           1,676   <0.01%
market_resolved              674   <0.01%
new_market                   333   <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-19/03/2026-08-19T03.parquet
sha256sum 2026-08-19T03.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.