Hour audit: 2026-08-30T23
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: b. 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-08-30T23 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-30T23:00:00.037520714+00:00 · last event 2026-08-30T23:59:59.999952329+00:00
VOLUME 101,711,884 rows · 1,022,528,478 bytes (975.16 MiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured c: 101,682,784 · h: 101,637,986 · a: 101,092,911 · e: 100,486,311 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 29,423 (0.03%) · h: 1,186,452 (1.17%) · a: 11,285 (0.01%) · e: 100,484,724 (98.79%) (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 101,711,884 rows exactly, so those pairs supplied none
5 expected (abceh), 1 contributed nothing: b
INTEGRITY sha256 ad3fc0225e9ef7def6f801c51d34c7ef6b3a5cedb85d82c294b848ae5841ce20
the corpus checksum ledger names this file with the same digest
joined 101,713,479 to merged 101,711,884, minus 1,595 (minus 0.0016%)
boundary drops 1,595 · 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-08-31T00:54:08Z as aceh
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,521,831 96,543,239 0-32 3c99e82b261ab93f66158b3c91d29f79ea6cce9e4f89eff6d7d2910ebad2347a book 190,740 17,426,038 33-33 4568e9339093a978e6391d5a552fae73699e34526de469c193b3c64af7f5948c last_trade_price 80,001 4,395,816 34-34 5a301adf168d31b531cf092aea3b9b70eab8eccb0ce0b27a7c3e71b27a39d61a market_resolved 2,495 389,914 35-35 9fda866be5f893ca7b1bb6a16adda434d7facc798bfb1224954afeef36d77c41 new_market 1,337 131,303 36-36 98629119c5021fe6b119fedaa196faf321bb72d9546c44175eed90b19e66259c price_change 92,911,688 902,344,464 37-391 1d7b1cc7b3e17a83d7bbe9b8db47a3568edb49af8ade704748a546e8bcf5082e tick_size_change 3,792 138,700 392-392 28873106038583d5bc3e7d6ee05568ecf8e82a0a03c209c433bf537b7ab50581 EVENT MIX count share price_change 92,911,688 91.35% best_bid_ask 8,521,831 8.38% book 190,740 0.19% last_trade_price 80,001 0.08% tick_size_change 3,792 <0.01% market_resolved 2,495 <0.01% new_market 1,337 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,521,940 8,521,831 109 74,614 PARTIAL book 190,806 190,740 66 8,799 PARTIAL last_trade_price 80,001 80,001 0 3,652 PARTIAL market_resolved 2,495 2,495 0 2,457 PARTIAL new_market 1,337 1,337 0 844 PARTIAL price_change 92,913,108 92,911,688 1,420 126,194 PARTIAL tick_size_change 3,792 3,792 0 948 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 8,503,721 86 41ms 60ms 476ms 24.3s 0 transport_latency_assumed best_bid_ask c 8,521,423 617 3ms 6ms 72ms 2.9s 0 transport_latency_assumed best_bid_ask e 8,492,602 8,492,493 46ms 128ms 1.7s 24.9s 0 transport_latency_assumed best_bid_ask h 8,520,730 28,635 12ms 20ms 120ms 38.7s 0 transport_latency_assumed book a 162,699 7,878 93ms 5.6s 1.2h 74.5d 0 book_staleness book c 168,396 2,842 5ms 21ms 51.8s 74.5d 0 book_staleness book e 162,784 162,718 129ms 12.6s 4.0h 11.9d 0 book_staleness book h 167,668 17,302 19ms 113ms 6.1s 74.5d 0 book_staleness last_trade_price a 74,919 9 67ms 3.8s 13.2s 24.3s 0 transport_latency_assumed last_trade_price c 79,961 26 8ms 36ms 180ms 5.3s 0 transport_latency_assumed last_trade_price e 72,875 72,875 89ms 6.1s 16.6s 25.0s 0 transport_latency_assumed last_trade_price h 79,899 7,091 19ms 105ms 536ms 7.4s 0 transport_latency_assumed market_resolved a 2,456 15 41ms 110ms 564ms 2.4s 0 transport_latency_assumed market_resolved c 2,457 19 3ms 5ms 214ms 479ms 0 transport_latency_assumed market_resolved e 2,456 2,456 46ms 162ms 6.9s 1.0min 0 transport_latency_assumed market_resolved h 2,457 5 12ms 35ms 276ms 59.6s 0 transport_latency_assumed new_market a 844 58 195ms 17.1s 39.3s 13.8min 0 transport_latency_assumed new_market c 844 106 56ms 18.5s 39.0s 1.2min 0 transport_latency_assumed new_market e 844 844 236ms 23.2s 40.4s 2.5min 0 transport_latency_assumed new_market h 844 329 107ms 23.4s 36.0s 4.8min 0 transport_latency_assumed price_change a 92,344,480 3,239 41ms 94ms 4.3s 24.4s 0 transport_latency_assumed price_change c 92,905,911 25,813 3ms 6ms 99ms 3.1s 0 transport_latency_assumed price_change e 91,750,962 91,749,550 46ms 178ms 7.6s 25.0s 0 transport_latency_assumed price_change h 92,862,596 1,133,086 12ms 23ms 170ms 41.0s 0 transport_latency_assumed tick_size_change a 3,792 not meas. 40ms 48ms 244ms 1.7s 0 transport_latency_assumed tick_size_change c 3,792 not meas. 3ms 7ms 58ms 711ms 0 transport_latency_assumed tick_size_change e 3,788 3,788 46ms 123ms 4.2s 11.8s 0 transport_latency_assumed tick_size_change h 3,792 4 12ms 20ms 156ms 2.6s 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-30/23/2026-08-30T23.parquet sha256sum 2026-08-30T23.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.