Hour audit: 2026-09-25T22
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, 2 contributed no rows: c, g. The hour is still whole on minutes; it simply rests on 3 machines rather than 5.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-25T22 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-25T22:00:00.000277241+00:00 · last event 2026-09-25T22:59:59.999941625+00:00
VOLUME 110,675,082 rows · 1,150,381,356 bytes (1.07 GiB) · 7 products, all holding rows
WITNESSES hik — 3 machines contributed rows
captured k: 110,202,087 · i: 110,100,976 · h: 105,345,197 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 99,032,038 (89.48%) · i: 4,979,410 (4.50%) · h: 6,663,634 (6.02%) (rows of the merged file that came from it; these partition it)
5 expected (cghik), 2 contributed nothing: c, g
INTEGRITY sha256 d82159bd6e1690a2f4f3e587bbfce7050627a49fe2406474099c8368535abeb2
the corpus checksum ledger names this file with the same digest
joined 110,675,482 to merged 110,675,082, minus 400 (minus 0.0004%)
boundary drops 400 · 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-26T01:00:09Z as hik
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 status feed unobserved for this hour. Our incident register was last checked against the venue's feed at 2026-09-23T20:35Z, before this hour ended, so nothing has looked yet. This is a could-not-look and never an all-clear.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 10,589,683 117,137,291 0-40 0fefb7d279e6025950b0f0dcd1a40c2d24b4ff220f2e50e25404267099f01d3c book 633,624 57,566,100 41-43 df195159c683675b59680986192a82ed08da5e5e02d885783d03670f5cfdb1ff last_trade_price 46,377 2,680,684 44-44 63512ea3e81adad2008af651f127df05c2eea3ef72f21ef1f9bb32b323212c6a market_resolved 2,340 346,527 45-45 7ef757f49852a799dfa01942923b3d99a9cfcc775f0bfc652bb90a4f0e34d6f9 new_market 3,188 323,414 46-46 64bd663ebebd436079e6962426aab65a0af00f8eec4c1caeb0aa58e145309e3d price_change 99,397,498 970,979,641 47-426 0ee4254e2b5a0a191b9b5246c770f9aa8b8cb20987d8fcaaa8f1b00c113b2a1b tick_size_change 2,372 87,795 427-427 641a2167d861735957faebb7d83ba09e73284d87105382e58e13ce35c0eeae3c EVENT MIX count share price_change 99,397,498 89.81% best_bid_ask 10,589,683 9.57% book 633,624 0.57% last_trade_price 46,377 0.04% new_market 3,188 <0.01% tick_size_change 2,372 <0.01% market_resolved 2,340 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,589,723 10,589,683 40 53,207 PARTIAL book 633,742 633,624 118 218,199 PARTIAL last_trade_price 46,377 46,377 0 3,275 PARTIAL market_resolved 2,340 2,340 0 2,155 PARTIAL new_market 3,188 3,188 0 2,096 PARTIAL price_change 99,397,740 99,397,498 242 91,802 PARTIAL tick_size_change 2,372 2,372 0 593 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,103,781 543,381 18ms 49ms 522ms 1.6min 0 transport_latency_assumed best_bid_ask i 10,587,594 425,285 21ms 27ms 163ms 7.7s 0 transport_latency_assumed best_bid_ask k 10,586,723 9,621,017 12ms 20ms 288ms 1.2min 0 transport_latency_assumed book h 586,161 471,539 1.1h 4.1d 34.4d 119.0d 0 book_staleness book i 110,716 20,219 24ms 1.9min 7.3d 100.9d 0 book_staleness book k 210,941 141,866 12.7s 3.0d 34.3d 119.0d 0 book_staleness last_trade_price h 44,251 3,710 20ms 89ms 945ms 59.5s 0 transport_latency_assumed last_trade_price i 46,155 2,979 23ms 64ms 632ms 6.8s 0 transport_latency_assumed last_trade_price k 46,134 39,688 13ms 47ms 507ms 43.8s 0 transport_latency_assumed market_resolved h 2,147 244 19ms 12.4s 55.1s 6.8min 0 transport_latency_assumed market_resolved i 2,155 119 21ms 25.6s 54.0s 55.8s 0 transport_latency_assumed market_resolved k 2,155 1,977 13ms 27.8s 55.1s 55.5s 0 transport_latency_assumed new_market h 2,110 970 224ms 37.5s 2.0min 3.6min 0 transport_latency_assumed new_market i 2,096 1,068 177ms 37.4s 1.8min 2.8min 0 transport_latency_assumed new_market k 2,096 1,150 231ms 38.0s 1.8min 2.8min 0 transport_latency_assumed price_change h 94,604,455 5,643,650 18ms 53ms 576ms 1.7min 0 transport_latency_assumed price_change i 99,349,888 4,529,652 21ms 31ms 230ms 7.8s 0 transport_latency_assumed price_change k 99,351,666 89,224,196 12ms 24ms 323ms 1.3min 0 transport_latency_assumed tick_size_change h 2,292 140 18ms 40ms 69ms 297ms 0 transport_latency_assumed tick_size_change i 2,372 88 21ms 29ms 61ms 92ms 0 transport_latency_assumed tick_size_change k 2,372 2,144 12ms 20ms 56ms 120ms 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-25/22/2026-09-25T22.parquet sha256sum 2026-09-25T22.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.