Hour audit: 2026-08-30T10
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.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-08-30T10 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-30T10:00:00.023616012+00:00 · last event 2026-08-30T10:59:59.999989632+00:00
VOLUME 94,367,125 rows · 956,138,681 bytes (911.84 MiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured c: 94,351,420 · a: 94,332,695 · h: 94,251,652 · e: 94,242,980 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 87,406 (0.09%) · a: 5,981 (0.01%) · h: 31,998 (0.03%) · e: 94,241,740 (99.87%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 94,367,125 rows exactly, so those pairs supplied none
5 expected (abceh), 1 contributed nothing: b
INTEGRITY sha256 130df4395e6e319041643ea3d399dcde19e441e824c95b1c100bfacb903f3892
the corpus checksum ledger names this file with the same digest
joined 94,368,367 to merged 94,367,125, minus 1,242 (minus 0.0013%)
boundary drops 1,242 · 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-31T15:06:17Z 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 7/8 pass, 1 finding
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
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 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,559,478 95,709,946 0-32 9216f867fda5d069e19cdae82adbf0a21dfcc23a85e0ef640e08659d68aa7039 book 124,756 13,008,024 33-33 49ecf8f4f83c2fdcf715cd30ebaf107e4dc8e41af8d2793a99cbf8184cd59f2f last_trade_price 55,122 3,160,910 34-34 424fde1f21e98364f511d6bf2a0a334712f1de288d4cd1f20fbcf470582e055a market_resolved 501 80,952 35-35 97cac27e64ef858f9fc50952ebc55b9298d29361830c47c6c1ad39e5d98c1af9 new_market 354 41,214 36-36 46e23896054de44dc2d7b9b7025cf87392cb83f8f5b06faab6c8667fb19c2bb9 price_change 85,624,238 842,964,625 37-363 c5ec1db8209d94727d53a278bc16c97110ce1ef167c85cc445475d090fb3b66a tick_size_change 2,676 97,046 364-364 01a3346bd447ac3c1d4dc761132cc9abaca3491e378592760f69634fbb8efcd0 EVENT MIX count share price_change 85,624,238 90.74% best_bid_ask 8,559,478 9.07% book 124,756 0.13% last_trade_price 55,122 0.06% tick_size_change 2,676 <0.01% market_resolved 501 <0.01% new_market 354 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,559,550 8,559,478 72 68,350 PARTIAL book 124,756 124,756 0 9,185 PARTIAL last_trade_price 55,122 55,122 0 3,476 PARTIAL market_resolved 501 501 0 492 PARTIAL new_market 354 354 0 270 PARTIAL price_change 85,625,408 85,624,238 1,170 128,510 PARTIAL tick_size_change 2,676 2,676 0 669 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 8,557,613 4 38ms 44ms 163ms 10.1s 0 transport_latency_assumed best_bid_ask c 8,559,387 376 31ms 49ms 64ms 1.6s 0 transport_latency_assumed best_bid_ask e 8,557,486 8,557,414 43ms 64ms 417ms 11.4s 0 transport_latency_assumed best_bid_ask h 8,558,790 1,684 12ms 16ms 57ms 7.6s 0 transport_latency_assumed book a 117,404 5,281 46ms 1.3s 2.0h 74.0d 0 book_staleness book c 114,395 1,944 35ms 56ms 55.5s 74.0d 0 book_staleness book e 115,405 115,405 52ms 1.7s 5.9min 84.8d 0 book_staleness book h 113,907 2,126 17ms 60ms 20.8s 74.0d 0 book_staleness last_trade_price a 54,898 6 48ms 629ms 4.4s 10.1s 0 transport_latency_assumed last_trade_price c 55,098 3 40ms 66ms 166ms 5.0s 0 transport_latency_assumed last_trade_price e 54,873 54,873 57ms 1.2s 5.4s 11.6s 0 transport_latency_assumed last_trade_price h 55,035 240 17ms 60ms 543ms 5.0s 0 transport_latency_assumed market_resolved a 492 7 40ms 321ms 597ms 1.0s 0 transport_latency_assumed market_resolved c 492 2 33ms 49ms 31.9s 1.0min 0 transport_latency_assumed market_resolved e 492 492 43ms 382ms 27.7s 59.1s 0 transport_latency_assumed market_resolved h 492 not meas. 12ms 69ms 25.9s 57.8s 0 transport_latency_assumed new_market a 270 11 138ms 10.6s 36.6s 1.2min 0 transport_latency_assumed new_market c 270 29 68ms 12.4s 56.4s 1.1min 0 transport_latency_assumed new_market e 270 270 82ms 12.8s 39.3s 1.2min 0 transport_latency_assumed new_market h 270 44 45ms 262ms 28.9s 1.2min 0 transport_latency_assumed price_change a 85,599,342 672 39ms 51ms 345ms 10.1s 0 transport_latency_assumed price_change c 85,619,102 85,052 30ms 49ms 73ms 2.9s 0 transport_latency_assumed price_change e 85,511,778 85,510,610 43ms 95ms 1.2s 11.4s 0 transport_latency_assumed price_change h 85,520,482 27,904 12ms 17ms 78ms 7.7s 0 transport_latency_assumed tick_size_change a 2,676 not meas. 38ms 43ms 106ms 317ms 0 transport_latency_assumed tick_size_change c 2,676 not meas. 29ms 45ms 56ms 81ms 0 transport_latency_assumed tick_size_change e 2,676 2,676 43ms 112ms 201ms 1.2s 0 transport_latency_assumed tick_size_change h 2,676 not meas. 12ms 17ms 39ms 55ms 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-30/10/2026-08-30T10.parquet sha256sum 2026-08-30T10.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.