Hour audit: 2026-09-12T00
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: f. 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-09-12T00 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-12T00:00:00.000091565+00:00 · last event 2026-09-12T00:59:59.999954523+00:00
VOLUME 121,286,210 rows · 1,276,630,267 bytes (1.19 GiB) · 7 products, all holding rows
WITNESSES cegh — 4 machines contributed rows
captured h: 119,130,742 · e: 115,100,689 · g: 114,169,211 · c: 98,786,781 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 23,404,573 (19.30%) · e: 1,990,751 (1.64%) · g: 132,060 (0.11%) · c: 95,758,826 (78.95%) (rows of the merged file that came from it; these partition it)
5 expected (cefgh), 1 contributed nothing: f
INTEGRITY sha256 8682210eaab60d0940b2882c705e6d7c82fc26b82fc26a9d7f7bbb45ecb32b91
the corpus checksum ledger names this file with the same digest
joined 121,292,605 to merged 121,286,210, minus 6,395 (minus 0.0053%)
boundary drops 6,395 · 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-12T03:22:29Z as cegh
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 11,229,402 124,764,593 0-42 32bf71aefec3e21232fadec5081f36f7ac7523b44ca3a78bff83ef5ecac60af3 book 2,197,310 96,103,646 43-51 fd7cf94b9539b92f1a2a4330a93177234b6cc57609be21510f69345a9d14e785 last_trade_price 46,238 2,673,466 52-52 dfdef5209554af58da2958ad75192ca76b9a5b2ed91c463d78bd72fdfd69b57c market_resolved 1,248 145,042 53-53 0af540f970c9cb8a12b8d8746f6e57eacbbc331181a27b397a84bb3c3f52562b new_market 1,214 115,040 54-54 ad438f782829dda457a0348058a7ec7bafe653c357c538428c679eba339ac9f3 price_change 107,808,042 1,051,347,393 55-466 fe9a9e20385bdebb7c2c58921ec5fe48678dd841a39ddfd56a13fc8707380dfa tick_size_change 2,756 101,970 467-467 fff6426e89ea4611e02a24a948d7b39e6acae079ce27b30372ff3a33a598d8b7 EVENT MIX count share price_change 107,808,042 88.89% best_bid_ask 11,229,402 9.26% book 2,197,310 1.81% last_trade_price 46,238 0.04% tick_size_change 2,756 <0.01% market_resolved 1,248 <0.01% new_market 1,214 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,229,682 11,229,402 280 75,793 PARTIAL book 2,198,628 2,197,310 1,318 214,308 PARTIAL last_trade_price 46,239 46,238 1 3,054 PARTIAL market_resolved 1,248 1,248 0 873 PARTIAL new_market 1,214 1,214 0 709 PARTIAL price_change 107,812,838 107,808,042 4,796 134,476 PARTIAL tick_size_change 2,756 2,756 0 689 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,186,770 8,915,248 5ms 8ms 70ms 3.5s 0 transport_latency_assumed best_bid_ask e 10,838,491 167,835 39ms 44ms 128ms 4.9s 0 transport_latency_assumed best_bid_ask g 10,742,378 4,600 83ms 102ms 321ms 14.4s 0 transport_latency_assumed best_bid_ask h 11,228,099 2,141,719 17ms 23ms 108ms 20.0s 0 transport_latency_assumed book c 2,036,300 1,949,185 10.3min 6.7h 31.2d 105.1d 0 book_staleness book e 520,287 145,396 6.0min 6.7h 27.4d 105.1d 0 book_staleness book g 548,513 76,678 5.4min 6.6h 27.4d 105.1d 0 book_staleness book h 102,108 26,051 21ms 77ms 3.4h 105.1d 0 book_staleness last_trade_price c 36,832 35,013 10ms 42ms 201ms 5.0s 0 transport_latency_assumed last_trade_price e 44,327 1,008 46ms 105ms 647ms 5.0s 0 transport_latency_assumed last_trade_price g 43,873 51 97ms 226ms 2.1s 9.2s 0 transport_latency_assumed last_trade_price h 46,088 10,166 23ms 61ms 249ms 5.0s 0 transport_latency_assumed market_resolved c 1,025 945 5ms 8.3min 13.6min 14.4min 0 transport_latency_assumed market_resolved e 897 63 40ms 168ms 7.4min 7.5min 0 transport_latency_assumed market_resolved g 871 15 88ms 379ms 5.0min 5.0min 0 transport_latency_assumed market_resolved h 873 225 18ms 43.1s 59.3s 59.3s 0 transport_latency_assumed new_market c 979 672 122ms 7.7min 8.5min 8.6min 0 transport_latency_assumed new_market e 724 208 148ms 28.0s 1.6h 1.6h 0 transport_latency_assumed new_market g 673 99 310ms 18.0s 57.3s 1.1min 0 transport_latency_assumed new_market h 673 235 103ms 16.5s 32.6s 54.8s 0 transport_latency_assumed price_change c 87,522,591 84,855,575 5ms 9ms 76ms 5.0s 0 transport_latency_assumed price_change e 103,693,323 1,676,180 39ms 46ms 160ms 6.1s 0 transport_latency_assumed price_change g 102,830,191 50,613 83ms 106ms 370ms 14.6s 0 transport_latency_assumed price_change h 107,750,145 21,225,674 17ms 24ms 120ms 20.0s 0 transport_latency_assumed tick_size_change c 2,284 2,188 5ms 10ms 401ms 459ms 0 transport_latency_assumed tick_size_change e 2,640 61 39ms 48ms 447ms 596ms 0 transport_latency_assumed tick_size_change g 2,712 4 83ms 101ms 643ms 1.3s 0 transport_latency_assumed tick_size_change h 2,756 503 18ms 31ms 489ms 994ms 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-12/00/2026-09-12T00.parquet sha256sum 2026-09-12T00.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.