Hour audit: 2026-08-28T09
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-28T09 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-08-28T09:00:00.027446672+00:00 · last event 2026-08-28T09:59:59.999959992+00:00
VOLUME 94,625,150 rows · 1,048,499,733 bytes (999.93 MiB) · 7 products, all holding rows
WITNESSES abceh — 5 machines contributed rows
captured c: 92,843,592 · b: 92,571,558 · e: 92,148,071 · a: 88,940,308 · h: 83,332,746 (each machine's own feed; these overlap and do not sum to the file)
supplied c: not measured · b: not measured · e: not measured · a: not measured · h: not measured (rows of the merged file that came from it; these partition it)
INTEGRITY sha256 327176f28cf153c9c0e6aff0df8b65bc4b82864a0d2ce363fc65afb997a36174
the corpus checksum ledger names this file with the same digest
joined 94,626,623 to merged 94,625,150, minus 1,473 (minus 0.0016%)
boundary drops 1,473 · 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,853,220 105,426,924 0-33 1a13541b3d5ef018008300a59831ca212d1de62cd9c765ead570738c324cefa9 book 2,268,187 101,887,886 34-42 d3523919ca687d36e52f9a150332e4b060046c1ef8c78f36068e7a3f1e633d43 last_trade_price 67,255 3,773,875 43-43 ac56f121a5837262b34d2c94b9fae362871a1af0423730ac29aa1ca8d5daed14 market_resolved 674 89,688 44-44 30ea3274a6e63cc02d65e6b233c604328dc2be7efcfa3fb9b1a9ae812b769161 new_market 454 44,386 45-45 d7ad5f615d0b1ecfac2b0138bf94f872707b29003b696ede0237ad38c4bc71d0 price_change 83,432,508 836,091,237 46-364 975ae6931593aac60a00b8cf66886bd862baab38e72f51c124ff9bd55725dad6 tick_size_change 2,852 104,975 365-365 7b64d41d4fc2fbdc85b249d97400d1a966e39aa5ca54b40b43a06351c3e5ff5c EVENT MIX count share price_change 83,432,508 88.17% best_bid_ask 8,853,220 9.36% book 2,268,187 2.40% last_trade_price 67,255 0.07% tick_size_change 2,852 <0.01% market_resolved 674 <0.01% new_market 454 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,853,367 8,853,220 147 2,288 FULL book 2,268,287 2,268,187 100 96,853 FULL last_trade_price 67,255 67,255 0 246 FULL market_resolved 674 674 0 35 FULL new_market 454 454 0 2 FULL price_change 83,433,734 83,432,508 1,226 772 FULL tick_size_change 2,852 2,852 0 99 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/09/2026-08-28T09.parquet sha256sum 2026-08-28T09.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.