Hour audit: 2026-08-31T09
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.
1 finding
- a machine expected this hour contributed nothing. Of the 5 machines expected to be capturing this hour, 1 contributed no rows: b. The hour is still whole on minutes; it simply rests on 4 machines rather than 5.
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-31T09 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-31T09:00:00.043811828+00:00 · last event 2026-08-31T09:59:59.129504989+00:00
VOLUME 164,650 rows · 3,684,085 bytes (3.51 MiB) · 7 products, 2 holding no rows
WITNESSES aceh — 4 machines contributed rows
captured a: 160,257 · c: 155,939 · e: 155,451 · h: 154,065 (each machine's own feed; these overlap and do not sum to the file)
supplied a: 6,251 (3.80%) · c: 2,042 (1.24%) · e: 155,391 (94.38%) · h: 966 (0.59%) (rows of the merged file that came from it; these partition it)
6 product-machine pairs publish no supplied count; the figures above still sum to the file's 164,650 rows exactly, so those pairs supplied none
5 expected (abceh), 1 contributed nothing: b
INTEGRITY sha256 f62b3f35a740bbaa2138197b9c46f02675ce1c89918c5c11584d03bbc31effe4
the corpus checksum ledger names this file with the same digest
joined 164,720 to merged 164,650, minus 70 (minus 0.0425%)
boundary drops 70 · 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 merged 2026-08-31T11:44:53Z as aceh
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 6/8 pass, 1 finding, 1 not evaluated
PASS all products present
PASS row counts reconcile
SKIPPED the byte ranges could not be checked
PASS the merge delta is explained
FINDING a machine expected this hour contributed nothing
PASS the checksum ledger names this file
PASS the hour is whole
PASS a boundary guard ran
UPSTREAM an incident recorded by the venue intersects this hour: Venue stopped trading for four hours, 2026-08-31T06:30Z to 2026-08-31T10:47ZThe 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 2,306 103,099 0-0 7fe0e8ccdaff27ffec4761ff69828b61d12b19e7e4427acd0b911f2b0be9e807 book 11,654 1,293,741 1-1 70f70e3cf5de00779df0c5391093a693b4f430fea50edcdc7fab3f5af895b6c5 last_trade_price 0 not meas. 2-1 not published market_resolved 272 44,793 2-2 b3c5841bce02836951f1583915f8fd354a7062d050a6ee11dbe2a0891b990f1b new_market 800 87,850 3-3 a7487a65196c5861ddf286807b1fc9ab0c9c2df180f20bc681af745f538339cc price_change 149,618 2,136,848 4-4 3869465707f157d9330f05f97f418eb9716f7da63fce4fc035d7c92e8c4c3f13 tick_size_change 0 not meas. 5-4 not published EVENT MIX count share price_change 149,618 90.87% book 11,654 7.08% best_bid_ask 2,306 1.40% new_market 800 0.49% market_resolved 272 0.17% last_trade_price 0 0.00% tick_size_change 0 0.00% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 2,308 2,306 2 662 PARTIAL book 11,664 11,654 10 5,828 PARTIAL last_trade_price 0 0 0 0 NO-SOURCE market_resolved 272 272 0 271 PARTIAL new_market 800 800 0 590 PARTIAL price_change 149,676 149,618 58 7,358 PARTIAL tick_size_change 0 0 0 0 NO-SOURCE ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 2,308 not meas. 39ms 145ms 386ms 956ms 0 transport_latency_assumed best_bid_ask c 2,306 not meas. 3ms 10ms 198ms 511ms 0 transport_latency_assumed best_bid_ask e 2,308 2,306 44ms 214ms 1.3s 2.3s 0 transport_latency_assumed best_bid_ask h 2,308 not meas. 15ms 43ms 159ms 709ms 0 transport_latency_assumed book a 7,438 6,230 2.7h 13.8h 28.9d 75.0d 0 book_staleness book c 3,154 1,980 2.7h 3.5h 22.8d 74.9d 0 book_staleness book e 3,268 3,268 2.4h 14.2h 19.6d 19.6d 0 book_staleness book h 1,346 176 2.2s 2.5h 12.7d 74.8d 0 book_staleness market_resolved a 271 1 39ms 139ms 687ms 1.1s 0 transport_latency_assumed market_resolved c 271 not meas. 1ms 4ms 330ms 498ms 0 transport_latency_assumed market_resolved e 271 271 44ms 161ms 611ms 657ms 0 transport_latency_assumed market_resolved h 271 not meas. 13ms 23ms 354ms 677ms 0 transport_latency_assumed new_market a 590 20 126ms 16.4s 23.9s 1.2min 0 transport_latency_assumed new_market c 590 58 55ms 15.3s 24.9s 1.0min 0 transport_latency_assumed new_market e 590 590 173ms 16.3s 23.9s 1.0min 0 transport_latency_assumed new_market h 590 132 73ms 346ms 20.1s 58.3s 0 transport_latency_assumed price_change a 149,650 not meas. 43ms 181ms 387ms 1.1s 0 transport_latency_assumed price_change c 149,618 4 3ms 19ms 120ms 804ms 0 transport_latency_assumed price_change e 149,014 148,956 44ms 1.1s 3.8s 4.6s 0 transport_latency_assumed price_change h 149,550 658 19ms 50ms 131ms 1.0s 0 transport_latency_assumed
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-31/09/2026-08-31T09.parquet sha256sum 2026-08-31T09.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.