Hour audit: 2026-09-02T08
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-02T08 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-02T08:00:00.034593838+00:00 · last event 2026-09-02T08:59:59.999978144+00:00
VOLUME 92,072,101 rows · 921,953,004 bytes (879.24 MiB) · 7 products, all holding rows
WITNESSES ceh — 3 machines contributed rows
captured c: 91,915,475 · h: 91,581,721 · e: 90,788,209 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 426,518 (0.46%) · h: 858,188 (0.93%) · e: 90,787,395 (98.60%) (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 92,072,101 rows exactly, so those pairs supplied none
4 expected (bceh), 1 contributed nothing: b
INTEGRITY sha256 d8ac67b85edf578f65adc0d4eb462d21dfffa4d61f580b3fbed570b1ec3a1d2f
the corpus checksum ledger names this file with the same digest
joined 92,072,923 to merged 92,072,101, minus 822 (minus 0.0009%)
boundary drops 822 · 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-02T09:48:44Z 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 8,430,246 94,243,997 0-32 678e1a51672492c1b8ba5574023519b0d89b86da1ec85ad2089f961d140e3bdf book 525,181 52,050,268 33-35 d9a5699f9b8672bbe0aff2e34901a92504f7351f28e3694b9f4a1c03413c4199 last_trade_price 70,430 3,892,667 36-36 47634519109c30321c627c31c325de1c59e1bbdc52dea1aa4f06a4f5043f74f9 market_resolved 756 115,128 37-37 c6edcfd555a0177070ce0029b036aeef1d5222da5c5a82c7d93d780b3b01577f new_market 622 74,428 38-38 70c0226a0b3a496d9e795271f5ab4a79df5db8490844245b097ac7a90cd0699d price_change 83,042,222 770,427,567 39-355 28c37b50c191d4321312b3c37a5209d60418c93988323ec9a9de94626dcda739 tick_size_change 2,644 97,573 356-356 e1ba239217f64a904b5a27fef55a9f06be20e04aaa54ea209af0fcd422912b03 EVENT MIX count share price_change 83,042,222 90.19% best_bid_ask 8,430,246 9.16% book 525,181 0.57% last_trade_price 70,430 0.08% tick_size_change 2,644 <0.01% market_resolved 756 <0.01% new_market 622 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,430,320 8,430,246 74 77,300 PARTIAL book 525,197 525,181 16 176,977 PARTIAL last_trade_price 70,430 70,430 0 3,559 PARTIAL market_resolved 756 756 0 710 PARTIAL new_market 622 622 0 490 PARTIAL price_change 83,042,954 83,042,222 732 138,449 PARTIAL tick_size_change 2,644 2,644 0 661 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,416,674 4,884 3ms 10ms 57ms 2.9s 0 transport_latency_assumed best_bid_ask e 8,384,094 8,384,020 43ms 91ms 1.8s 24.1s 0 transport_latency_assumed best_bid_ask h 8,424,215 41,342 18ms 25ms 384ms 18.1s 0 transport_latency_assumed book c 502,961 350,530 1.2min 8.7h 26.4d 95.4d 0 book_staleness book e 160,165 160,157 172ms 2.0min 10.8d 76.9d 0 book_staleness book h 147,014 14,494 31ms 932ms 3.4min 24.8d 0 book_staleness last_trade_price c 70,342 539 12ms 39ms 192ms 4.8s 0 transport_latency_assumed last_trade_price e 64,401 64,401 84ms 5.4s 15.0s 23.8s 0 transport_latency_assumed last_trade_price h 69,746 5,490 31ms 784ms 3.0s 7.4s 0 transport_latency_assumed market_resolved c 710 46 2ms 12ms 34.0s 1.0min 0 transport_latency_assumed market_resolved e 709 709 43ms 1.1s 58.1s 58.2s 0 transport_latency_assumed market_resolved h 710 1 18ms 399ms 58.6s 58.6s 0 transport_latency_assumed new_market c 490 49 48ms 10.7s 44.2s 60.0s 0 transport_latency_assumed new_market e 490 490 226ms 13.9s 51.9s 53.8s 0 transport_latency_assumed new_market h 490 83 95ms 11.2s 52.7s 1.0min 0 transport_latency_assumed price_change c 82,921,654 70,470 3ms 11ms 77ms 3.1s 0 transport_latency_assumed price_change e 82,175,706 82,174,974 43ms 129ms 5.8s 24.2s 0 transport_latency_assumed price_change h 82,936,902 796,778 18ms 31ms 733ms 20.7s 0 transport_latency_assumed tick_size_change c 2,644 not meas. 6ms 11ms 51ms 244ms 0 transport_latency_assumed tick_size_change e 2,644 2,644 43ms 118ms 4.9s 13.3s 0 transport_latency_assumed tick_size_change h 2,644 not meas. 18ms 33ms 125ms 889ms 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/08/2026-09-02T08.parquet sha256sum 2026-09-02T08.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.