Hour audit: 2026-08-31T16
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-08-31T16 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-31T16:00:00.042387465+00:00 · last event 2026-08-31T16:59:59.999983041+00:00
VOLUME 99,890,445 rows · 988,244,322 bytes (942.46 MiB) · 7 products, all holding rows
WITNESSES ceh — 3 machines contributed rows
captured c: 99,861,082 · h: 99,783,977 · e: 97,991,806 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 46,432 (0.05%) · h: 1,853,412 (1.86%) · e: 97,990,601 (98.10%) (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 99,890,445 rows exactly, so those pairs supplied none
4 expected (bceh), 1 contributed nothing: b
the listing string reads "bche"; the letters above are the machines whose rows are in the file
INTEGRITY sha256 0f4ac6083de944efbea940966b1485dc7929120c0fec052b226907698c3d0e75
the corpus checksum ledger names this file with the same digest
joined 99,891,650 to merged 99,890,445, minus 1,205 (minus 0.0012%)
boundary drops 1,205 · 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-02T02:59:33Z 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 7,920,898 89,579,970 0-30 9498875b2279a893971545cc62a7934e50c3764731cf31d64a12ddeaa156a1c1 book 191,186 18,691,516 31-31 94b8be50ab2f585b07e87eac6f10f7eed63f1740ddcd0e079e5fdab7c781a75c last_trade_price 83,252 4,613,430 32-32 7beb41df17de3e0f4ee8c43fa79fa2512537add8918c3cc13be7ac8ea8ea3262 market_resolved 1,145 186,264 33-33 35dfb9c952c3ba4756101b85cc856b0f5c68f57517f5e73ac1d28c032b6f9c15 new_market 2,158 235,162 34-34 0f66f9f4c3d875a36264fdac7f9e02b32c59403002bceadaac5f830065bcaac1 price_change 91,687,482 873,642,881 35-384 8c1c33e8b3504d4ec54081ba6a4f5e26c824eef77292f5b2f5ab1f37bb87f10c tick_size_change 4,324 158,772 385-385 92679f86a7a4287f05026af50fb361bbb47b3d7f7dad2f512c8e8da9dfba4968 EVENT MIX count share price_change 91,687,482 91.79% best_bid_ask 7,920,898 7.93% book 191,186 0.19% last_trade_price 83,252 0.08% tick_size_change 4,324 <0.01% new_market 2,158 <0.01% market_resolved 1,145 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 7,920,926 7,920,898 28 71,030 PARTIAL book 191,218 191,186 32 9,785 PARTIAL last_trade_price 83,253 83,252 1 4,383 PARTIAL market_resolved 1,145 1,145 0 1,124 PARTIAL new_market 2,158 2,158 0 1,553 PARTIAL price_change 91,688,626 91,687,482 1,144 131,365 PARTIAL tick_size_change 4,324 4,324 0 1,081 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 7,918,930 1,442 0ms 4ms 126ms 7.0s 0 transport_latency_assumed best_bid_ask e 7,872,202 7,872,174 44ms 118ms 2.8s 26.6s 0 transport_latency_assumed best_bid_ask h 7,918,704 47,282 14ms 28ms 230ms 43.2s 0 transport_latency_assumed book c 174,291 1,900 2ms 23ms 2.0s 75.2d 0 book_staleness book e 174,777 174,745 120ms 8.4s 4.2h 48.0d 0 book_staleness book h 174,539 14,541 20ms 116ms 2.4s 75.2d 0 book_staleness last_trade_price c 83,174 30 5ms 35ms 253ms 5.0s 0 transport_latency_assumed last_trade_price e 77,473 77,472 85ms 5.2s 12.9s 25.0s 0 transport_latency_assumed last_trade_price h 83,194 5,750 20ms 107ms 519ms 41.9s 0 transport_latency_assumed market_resolved c 1,124 not meas. -1ms 4ms 206ms 437ms 0 transport_latency_assumed market_resolved e 1,124 1,124 45ms 488ms 59.6s 1.0min 0 transport_latency_assumed market_resolved h 1,124 21 14ms 55ms 179ms 3.8s 0 transport_latency_assumed new_market c 1,553 111 53ms 21.2s 240.9d 240.9d 0 transport_latency_assumed new_market e 1,553 1,553 250ms 21.7s 240.9d 240.9d 0 transport_latency_assumed new_market h 1,553 494 145ms 22.7s 240.9d 240.9d 0 transport_latency_assumed price_change c 91,677,790 42,949 0ms 5ms 159ms 7.2s 0 transport_latency_assumed price_change e 89,860,465 89,859,321 45ms 203ms 7.6s 26.6s 0 transport_latency_assumed price_change h 91,600,539 1,785,212 14ms 33ms 269ms 43.3s 0 transport_latency_assumed tick_size_change c 4,220 not meas. 0ms 9ms 420ms 1.1s 0 transport_latency_assumed tick_size_change e 4,212 4,212 45ms 145ms 1.4s 22.8s 0 transport_latency_assumed tick_size_change h 4,324 112 14ms 43ms 560ms 3.9s 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/16/2026-08-31T16.parquet sha256sum 2026-08-31T16.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.