Hour audit: 2026-08-31T17
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-08-31T17 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-31T17:00:00.037949161+00:00 · last event 2026-08-31T17:59:59.999977534+00:00
VOLUME 91,534,312 rows · 926,252,020 bytes (883.34 MiB) · 7 products, all holding rows
WITNESSES ceh — 3 machines contributed rows
captured c: 91,499,161 · h: 91,297,516 · e: 90,965,114 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 135,575 (0.15%) · h: 435,041 (0.48%) · e: 90,963,696 (99.38%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 91,534,312 rows exactly, so those pairs supplied none
4 expected (bceh), 1 contributed nothing: b
the listing string reads "bche"; the letters above are the machines whose rows are in the file
INTEGRITY sha256 3f9d345d9a3c95fad8e6f6a44be5508d55ca73281648b296a65dd4c248a5938b
the corpus checksum ledger names this file with the same digest
joined 91,535,732 to merged 91,534,312, minus 1,420 (minus 0.0016%)
boundary drops 1,420 · 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-02T03:14:02Z 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 7,779,611 88,969,467 0-29 954e1588ef9239237261403604d1c9a4cd60d34f99195aaaaf6c01fc00cbe0b6 book 236,932 24,456,171 30-30 5017d7416812c394f6315bfd3b4eadea6f7b24e666d8a61e0a02ee61c863299d last_trade_price 72,944 4,106,474 31-31 b09febeb8bafbb109f3fb752704af22b62ca2324a5cd77351b8901cb00d80025 market_resolved 880 143,660 32-32 7d134009e055f81829aff2e283922538ea39f91d21dda417220cb21d82e5768f new_market 2,049 235,775 33-33 a17e2e76149ec7610fbe47d1423c5e4cf68009345b476e8c67d00306ca7ecfd0 price_change 83,437,004 807,119,843 34-352 9a4a627f740d6823b8d7cdf376a7038330364692cd2ea5f5069d62361f146039 tick_size_change 4,892 178,279 353-353 e6f36eb87e6c594cf4e1592bb08d500a3e8cba27e517b6612f378e73ebdffebd EVENT MIX count share price_change 83,437,004 91.15% best_bid_ask 7,779,611 8.50% book 236,932 0.26% last_trade_price 72,944 0.08% tick_size_change 4,892 <0.01% new_market 2,049 <0.01% market_resolved 880 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 7,779,751 7,779,611 140 81,608 PARTIAL book 236,934 236,932 2 43,231 PARTIAL last_trade_price 72,944 72,944 0 4,159 PARTIAL market_resolved 880 880 0 863 PARTIAL new_market 2,049 2,049 0 1,545 PARTIAL price_change 83,438,282 83,437,004 1,278 134,882 PARTIAL tick_size_change 4,892 4,892 0 1,223 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 7,778,713 784 2ms 6ms 176ms 6.6s 0 transport_latency_assumed best_bid_ask e 7,766,215 7,766,075 45ms 120ms 1.8s 34.1s 0 transport_latency_assumed best_bid_ask h 7,778,481 12,752 12ms 23ms 259ms 38.8s 0 transport_latency_assumed book c 210,813 55,734 7ms 8.6min 23.1d 93.8d 0 book_staleness book e 171,346 171,346 148ms 44.5s 16.7d 92.2d 0 book_staleness book h 156,795 9,852 19ms 164ms 7.2min 86.1d 0 book_staleness last_trade_price c 72,887 7 7ms 37ms 217ms 4.9s 0 transport_latency_assumed last_trade_price e 70,402 70,402 86ms 4.7s 12.9s 33.7s 0 transport_latency_assumed last_trade_price h 72,916 2,535 19ms 111ms 478ms 9.4s 0 transport_latency_assumed market_resolved c 863 not meas. 2ms 7ms 49.9s 51.6s 0 transport_latency_assumed market_resolved e 863 863 45ms 336ms 1.0min 1.0min 0 transport_latency_assumed market_resolved h 863 17 13ms 45ms 52.5s 54.5s 0 transport_latency_assumed new_market c 1,545 84 76ms 21.8s 1.4min 1.5min 0 transport_latency_assumed new_market e 1,545 1,545 264ms 25.8s 1.4min 2.3min 0 transport_latency_assumed new_market h 1,545 420 136ms 29.9s 1.4min 1.6min 0 transport_latency_assumed price_change c 83,429,448 78,966 2ms 7ms 207ms 6.7s 0 transport_latency_assumed price_change e 82,949,851 82,948,573 45ms 197ms 6.2s 34.2s 0 transport_latency_assumed price_change h 83,282,024 409,465 12ms 27ms 297ms 38.8s 0 transport_latency_assumed tick_size_change c 4,892 not meas. 2ms 5ms 30ms 230ms 0 transport_latency_assumed tick_size_change e 4,892 4,892 45ms 113ms 226ms 15.7s 0 transport_latency_assumed tick_size_change h 4,892 not meas. 12ms 21ms 101ms 2.8s 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-31/17/2026-08-31T17.parquet sha256sum 2026-08-31T17.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.