Hour audit: 2026-08-29T20
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-29T20 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-29T20:00:00.014480737+00:00 · last event 2026-08-29T20:59:59.999999061+00:00
VOLUME 125,555,466 rows · 1,327,643,620 bytes (1.24 GiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured h: 123,706,101 · e: 121,133,971 · c: 117,630,074 · a: 99,621,405 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 2,579,050 (2.05%) · e: 121,132,655 (96.48%) · c: 376,056 (0.30%) · a: 1,467,705 (1.17%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 125,555,466 rows exactly, so those pairs supplied none
5 expected (abceh), 1 contributed nothing: b
INTEGRITY sha256 8959f04da6c500a992da550cca7978d79ec2669bd8cdafc03b17c317dc75a872
the corpus checksum ledger names this file with the same digest
joined 125,556,792 to merged 125,555,466, minus 1,326 (minus 0.0011%)
boundary drops 1,326 · 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-30T04:09:09Z 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 10,547,350 118,429,035 0-40 fa8b37697a73af687defca20ceb4504aed26f5d682d0fea257ab1acecac6aeaa book 1,962,347 85,683,565 41-48 7a4ce3c75354999bb39e3f4ff91f6d12a856e5fc4c2b28768e9f664fb243e791 last_trade_price 66,713 3,815,626 49-49 e247d3aceb69d561835aaf415b9f3dd352451ce881454d72ccbfb4b8a63e1789 market_resolved 4,586 406,188 50-50 c6fa33d00cfd3b846f6ede3f361744c4de52daf63bd7922aff0ddb59dade1cf2 new_market 1,442 136,579 51-51 1f2bb657cde5c9affdb39f209a0f3a2912d6ce60d19b45c8658d9dcdbf312470 price_change 112,964,652 1,117,438,336 52-482 59dd414235013c2b79d1e0eac831c841c143f8496cae5f19e9f451e6abe757dd tick_size_change 8,376 306,551 483-483 1bcaeb381a5cb8770bfd072e161841e4401ccf493f113ddf8b6e02f2c2e4b962 EVENT MIX count share price_change 112,964,652 89.97% best_bid_ask 10,547,350 8.40% book 1,962,347 1.56% last_trade_price 66,713 0.05% tick_size_change 8,376 <0.01% market_resolved 4,586 <0.01% new_market 1,442 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,547,460 10,547,350 110 73,775 PARTIAL book 1,962,351 1,962,347 4 178,763 PARTIAL last_trade_price 66,713 66,713 0 4,400 PARTIAL market_resolved 4,586 4,586 0 2,434 PARTIAL new_market 1,442 1,442 0 876 PARTIAL price_change 112,965,864 112,964,652 1,212 139,636 PARTIAL tick_size_change 8,376 8,376 0 2,094 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 8,407,385 122 29ms 45ms 320ms 13.9s 0 transport_latency_assumed best_bid_ask c 10,045,114 754 5ms 8ms 74ms 7.6s 0 transport_latency_assumed best_bid_ask e 10,326,803 10,326,693 42ms 106ms 1.1s 22.8s 0 transport_latency_assumed best_bid_ask h 10,546,242 219,781 13ms 22ms 125ms 32.0s 0 transport_latency_assumed book a 1,899,233 1,464,769 1.8min 7.5h 27.4d 91.9d 0 book_staleness book c 487,882 358,315 54.9s 2.1h 26.1d 91.9d 0 book_staleness book e 135,557 135,555 71ms 3.2s 14.1s 1.7d 0 book_staleness book h 137,545 3,708 21ms 89ms 913ms 9.8s 0 book_staleness last_trade_price a 52,237 6 46ms 1.7s 7.9s 13.8s 0 transport_latency_assumed last_trade_price c 62,880 3 9ms 36ms 179ms 5.0s 0 transport_latency_assumed last_trade_price e 65,182 65,182 65ms 3.0s 12.6s 21.7s 0 transport_latency_assumed last_trade_price h 66,695 1,522 19ms 88ms 721ms 6.5s 0 transport_latency_assumed market_resolved a 3,991 2,052 4.8min 17.9min 23.1min 26.1min 0 transport_latency_assumed market_resolved c 2,268 59 5ms 11ms 4.8min 7.2min 0 transport_latency_assumed market_resolved e 2,397 2,397 45ms 248ms 2.1min 2.4min 0 transport_latency_assumed market_resolved h 2,433 78 14ms 56ms 23.9s 50.7s 0 transport_latency_assumed new_market a 1,002 302 255ms 8.9min 28.6min 43.5min 0 transport_latency_assumed new_market c 876 89 78ms 20.3s 25.0s 12.1min 0 transport_latency_assumed new_market e 876 876 227ms 16.5s 25.3s 9.5min 0 transport_latency_assumed new_market h 876 175 124ms 14.3s 23.9s 10.1min 0 transport_latency_assumed price_change a 89,250,750 454 31ms 59ms 590ms 13.9s 0 transport_latency_assumed price_change c 107,023,186 16,836 5ms 8ms 92ms 7.7s 0 transport_latency_assumed price_change e 110,594,928 110,593,724 43ms 159ms 3.2s 22.8s 0 transport_latency_assumed price_change h 112,943,934 2,353,638 13ms 24ms 151ms 32.0s 0 transport_latency_assumed tick_size_change a 6,807 not meas. 29ms 42ms 147ms 1.8s 0 transport_latency_assumed tick_size_change c 7,868 not meas. 5ms 7ms 154ms 460ms 0 transport_latency_assumed tick_size_change e 8,228 8,228 43ms 114ms 297ms 3.0s 0 transport_latency_assumed tick_size_change h 8,376 148 13ms 20ms 157ms 1.2s 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-29/20/2026-08-29T20.parquet sha256sum 2026-08-29T20.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.