Hour audit: 2026-08-28T00
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-28T00 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-08-28T00:00:00.040056298+00:00 · last event 2026-08-28T00:59:59.999995686+00:00
VOLUME 103,711,900 rows · 1,145,726,332 bytes (1.07 GiB) · 7 products, all holding rows
WITNESSES abceh — 5 machines contributed rows
captured c: 102,249,260 · h: 102,215,807 · e: 99,473,681 · a: 98,015,493 · b: 89,862,751 (each machine's own feed; these overlap and do not sum to the file)
supplied c: not measured · h: not measured · e: not measured · a: not measured · b: not measured (rows of the merged file that came from it; these partition it)
INTEGRITY sha256 a80af3ee9583773b4fc16d57b17e6cde8c561d1f0ba793e741093eb82f9bd9e1
the corpus checksum ledger names this file with the same digest
joined 103,713,018 to merged 103,711,900, minus 1,118 (minus 0.0011%)
boundary drops 1,118 · 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,652,425 100,555,733 0-33 e318b2217c26d3ceebdac147637c36cef72d1d03a69e81bc41c689d549b9b9ce book 1,810,117 93,407,895 34-40 88c5f0fc73b74e3ccfc4af1ed3b806fcac736560476c4631f18cb6a9e234c44d last_trade_price 64,353 3,578,900 41-41 fd4034566c841c2af7e45c34c8654380d60d27fc8abbd28cb4c63818cb17201d market_resolved 600 74,535 42-42 bf9ff99289b07a872bae8084ca575490b040aae69939a3133d01ab93235335a8 new_market 1,593 157,303 43-43 618373458b91205a109dc698ad8c7697fab945124cd1491edd914451166f3b13 price_change 93,180,652 946,687,197 44-399 7efe4353dc4011d0ee3beb4aa2fd9dbc63542873225de787214d303e3cb2248f tick_size_change 2,160 80,724 400-400 71bc84af4dcfede2d08f3496ed3cb130a3abebd39ffdf4f6e7294abc2dc0aea1 EVENT MIX count share price_change 93,180,652 89.85% best_bid_ask 8,652,425 8.34% book 1,810,117 1.75% last_trade_price 64,353 0.06% tick_size_change 2,160 <0.01% new_market 1,593 <0.01% market_resolved 600 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,652,511 8,652,425 86 1,766 FULL book 1,810,145 1,810,117 28 144,366 FULL last_trade_price 64,353 64,353 0 212 FULL market_resolved 600 600 0 21 FULL new_market 1,593 1,593 0 0 FULL price_change 93,181,656 93,180,652 1,004 1,145 FULL tick_size_change 2,160 2,160 0 86 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/00/2026-08-28T00.parquet sha256sum 2026-08-28T00.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.