Hour audit: 2026-09-01T20
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-01T20 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-01T20:00:00.028826027+00:00 · last event 2026-09-01T20:59:59.999941887+00:00
VOLUME 81,079,941 rows · 890,924,392 bytes (849.65 MiB) · 7 products, all holding rows
WITNESSES ceh — 3 machines contributed rows
captured h: 80,686,743 · c: 80,674,093 · e: 79,983,765 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 961,935 (1.19%) · c: 150,594 (0.19%) · e: 79,967,412 (98.63%) (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 81,079,941 rows exactly, so those pairs supplied none
4 expected (bceh), 1 contributed nothing: b
INTEGRITY sha256 cfbdd533cee16671797297eaf247e9225c6f06205f985bfdda630a24419eb919
the corpus checksum ledger names this file with the same digest
joined 81,102,212 to merged 81,079,941, minus 22,271 (minus 0.0275%)
boundary drops 22,271 · 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-01T23:25:25Z 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 5,653,129 77,555,474 0-21 db604a27ab1ea59e4c6af27c02272f7132eb6abcd57f7c92ba3bc39e97d976b4 book 720,373 68,317,234 22-24 7966f2a1387e55f2d9d0c2da01e70dfdf061d3ae798094b1ab58e627d9f6e633 last_trade_price 67,254 3,784,692 25-25 733e1cd0b90c1d813c5561942e2d60ccc0d5fefe36903729cd69308d3dd3fbe3 market_resolved 1,314 211,942 26-26 b85c7b6e157a82d40b428a04b57fc205f58a91f79d7c26efe6f19823b4bf4c5d new_market 9,939 1,068,947 27-27 619984956b0a7b6dac12d4476a5ddcaf48423abe3123e3b7bce6b4e0bbfc9a09 price_change 74,620,128 738,779,411 28-312 570da692df63d238ba825f0de8dbd2237c8a43b796e73cf6c889ff015a4abf4c tick_size_change 7,804 280,963 313-313 e70ee253fd5bfdbb3ddab1e008bc41b559cf3a4405b5da6d5be009d7be8ce20f EVENT MIX count share price_change 74,620,128 92.03% best_bid_ask 5,653,129 6.97% book 720,373 0.89% last_trade_price 67,254 0.08% new_market 9,939 0.01% tick_size_change 7,804 <0.01% market_resolved 1,314 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 5,654,324 5,653,129 1,195 125,176 PARTIAL book 724,466 720,373 4,093 165,091 PARTIAL last_trade_price 67,279 67,254 25 3,619 PARTIAL market_resolved 1,314 1,314 0 1,312 PARTIAL new_market 9,939 9,939 0 6,797 PARTIAL price_change 74,637,086 74,620,128 16,958 158,537 PARTIAL tick_size_change 7,804 7,804 0 1,951 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 5,651,905 1,169 5ms 21ms 390ms 5.0s 0 transport_latency_assumed best_bid_ask e 5,626,916 5,626,220 43ms 337ms 3.9s 47.0s 0 transport_latency_assumed best_bid_ask h 5,650,774 25,740 19ms 60ms 782ms 47.8s 0 transport_latency_assumed book c 337,558 142,953 9.8s 18.2min 24.3d 94.9d 0 book_staleness book e 388,461 387,116 30.2s 28.3min 29.2d 94.9d 0 book_staleness book h 365,700 190,304 18.5s 20.6min 24.3d 94.9d 0 book_staleness last_trade_price c 67,159 14 10ms 72ms 444ms 5.0s 0 transport_latency_assumed last_trade_price e 63,510 63,486 140ms 5.4s 19.7s 40.5s 0 transport_latency_assumed last_trade_price h 67,064 3,754 31ms 386ms 3.1s 43.2s 0 transport_latency_assumed market_resolved c 1,312 not meas. 5ms 23ms 401ms 643ms 0 transport_latency_assumed market_resolved e 1,309 1,309 43ms 405ms 1.4s 1.3min 0 transport_latency_assumed market_resolved h 1,312 5 19ms 134ms 650ms 6.2s 0 transport_latency_assumed new_market c 6,797 542 102ms 3.6min 8.0min 9.0min 0 transport_latency_assumed new_market e 6,797 6,797 249ms 3.1min 8.2min 9.6min 0 transport_latency_assumed new_market h 6,797 2,600 192ms 3.6min 7.8min 9.0min 0 transport_latency_assumed price_change c 74,601,558 5,916 5ms 26ms 401ms 6.7s 0 transport_latency_assumed price_change e 73,888,980 73,874,692 44ms 490ms 8.6s 47.5s 0 transport_latency_assumed price_change h 74,587,292 739,520 19ms 77ms 842ms 50.9s 0 transport_latency_assumed tick_size_change c 7,804 not meas. 5ms 14ms 341ms 821ms 0 transport_latency_assumed tick_size_change e 7,792 7,792 48ms 374ms 3.1s 29.4s 0 transport_latency_assumed tick_size_change h 7,804 12 19ms 42ms 686ms 5.3s 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-01/20/2026-09-01T20.parquet sha256sum 2026-09-01T20.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.