Hour audit: 2026-09-02T10
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 4 machines expected to be capturing this hour, 1 contributed no rows: b. The hour is still whole on minutes; it simply rests on 3 machines rather than 4.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-02T10 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-02T10:00:00.017378868+00:00 · last event 2026-09-02T10:59:59.999999911+00:00
VOLUME 107,994,393 rows · 1,107,963,216 bytes (1.03 GiB) · 7 products, all holding rows
WITNESSES ceh — 3 machines contributed rows
captured c: 107,582,662 · h: 107,574,207 · e: 107,281,435 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 206,136 (0.19%) · h: 508,308 (0.47%) · e: 107,279,949 (99.34%) (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 107,994,393 rows exactly, so those pairs supplied none
4 expected (bceh), 1 contributed nothing: b
INTEGRITY sha256 5b41dcb2d94eafa603a202b5f3960bb6daa168b2787f79a5240951fe3ebc21b8
the corpus checksum ledger names this file with the same digest
joined 107,996,703 to merged 107,994,393, minus 2,310 (minus 0.0021%)
boundary drops 2,310 · 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-09-02T12:36:14Z as ceh
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 9,505,988 106,786,380 0-36 08c0f20652cf2e129fadacbf67eb955bb109f4428018adb46b219bf0fe9ba63e book 839,733 67,411,987 37-40 2729ec4ea52c73b3781344fca20cfaf6714a16884b8dbfa3159d647a2ab65edb last_trade_price 75,265 4,206,248 41-41 1ce556463f13af3b11bfdbeb65304eaf9b21c18eb58f3d733a5830998347e13b market_resolved 1,205 194,549 42-42 923111b7bcde9c1856f021d3a794c0b1652f6f850bff5c9b251c9e640a2fb888 new_market 646 70,558 43-43 f4e7478cd7d372ea732617e4ecaf9c79eadf5891e8ecdbc807d801692afef9cc price_change 97,566,868 927,893,386 44-416 9693c607ffc0ba266caa89abaa0deb651b9324981f4ba9c17b64962c77d5bc4f tick_size_change 4,688 169,828 417-417 fa32bf062e7209b20245da4bcc2bd40cf0b325d8aad3f5caa8d0db47ddb8bbf2 EVENT MIX count share price_change 97,566,868 90.34% best_bid_ask 9,505,988 8.80% book 839,733 0.78% last_trade_price 75,265 0.07% tick_size_change 4,688 <0.01% market_resolved 1,205 <0.01% new_market 646 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,506,074 9,505,988 86 88,024 PARTIAL book 841,037 839,733 1,304 177,307 PARTIAL last_trade_price 75,265 75,265 0 4,084 PARTIAL market_resolved 1,205 1,205 0 1,190 PARTIAL new_market 646 646 0 461 PARTIAL price_change 97,567,788 97,566,868 920 138,956 PARTIAL tick_size_change 4,688 4,688 0 1,172 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,504,297 592 7ms 13ms 52ms 1.3s 0 transport_latency_assumed best_bid_ask e 9,492,189 9,492,103 42ms 77ms 881ms 21.9s 0 transport_latency_assumed best_bid_ask h 9,503,190 13,293 17ms 25ms 113ms 6.5s 0 transport_latency_assumed book c 452,727 201,798 41.3s 3.8h 24.9d 95.5d 0 book_staleness book e 395,228 394,736 28.2s 3.3h 24.9d 95.5d 0 book_staleness book h 450,206 243,199 38.6s 3.7h 24.9d 95.5d 0 book_staleness last_trade_price c 75,179 14 14ms 42ms 161ms 4.9s 0 transport_latency_assumed last_trade_price e 73,517 73,517 71ms 3.8s 16.0s 21.9s 0 transport_latency_assumed last_trade_price h 75,178 1,734 25ms 213ms 1.0s 4.9s 0 transport_latency_assumed market_resolved c 1,190 10 8ms 16ms 48.8s 1.0min 0 transport_latency_assumed market_resolved e 1,190 1,190 43ms 359ms 57.4s 1.0min 0 transport_latency_assumed market_resolved h 1,190 5 18ms 130ms 58.1s 1.0min 0 transport_latency_assumed new_market c 461 62 37ms 20.8s 27.3s 1.7min 0 transport_latency_assumed new_market e 461 461 185ms 15.1s 32.5s 1.7min 0 transport_latency_assumed new_market h 461 123 80ms 13.6s 25.7s 57.9s 0 transport_latency_assumed price_change c 97,544,124 3,660 8ms 13ms 63ms 1.6s 0 transport_latency_assumed price_change e 97,314,162 97,313,254 43ms 120ms 3.7s 21.9s 0 transport_latency_assumed price_change h 97,539,294 249,954 17ms 29ms 185ms 6.5s 0 transport_latency_assumed tick_size_change c 4,684 not meas. 7ms 12ms 31ms 618ms 0 transport_latency_assumed tick_size_change e 4,688 4,688 43ms 108ms 386ms 8.3s 0 transport_latency_assumed tick_size_change h 4,688 not meas. 17ms 30ms 111ms 2.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-09-02/10/2026-09-02T10.parquet sha256sum 2026-09-02T10.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.