Hour audit: 2026-08-30T15
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-30T15 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-30T15:00:00.036962193+00:00 · last event 2026-08-30T15:59:59.999915934+00:00
VOLUME 105,452,156 rows · 1,130,612,906 bytes (1.05 GiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured c: 105,081,846 · h: 105,046,911 · e: 104,454,097 · a: 100,843,144 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 23,003 (0.02%) · h: 623,361 (0.59%) · e: 104,453,224 (99.05%) · a: 352,568 (0.33%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 105,452,156 rows exactly, so those pairs supplied none
5 expected (abceh), 1 contributed nothing: b
INTEGRITY sha256 828038c41f9b1d75ab27b78c8b64a96719047f8b6bb54b3134e8f87a61cb20dc
the corpus checksum ledger names this file with the same digest
joined 105,453,053 to merged 105,452,156, minus 897 (minus 0.0009%)
boundary drops 897 · 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-30T17:55:16Z 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,466,960 101,772,635 0-32 791b9eb9731735b56b19c2aa7d3d52c611a27dff32df568a0cc0611be996268c book 521,462 54,355,158 33-34 f472527306f3f6d1b9cc2a9b0c02917e4453985f4a1e8837b4dfeb07b2869108 last_trade_price 80,005 4,584,758 35-35 96a725b0e2649f2084a29db1ef1888c04ab2bfb86f5843f366156be68aa26310 market_resolved 2,143 313,894 36-36 8d5e805e86374ca4c67e9b8ee958c29e2499491e0251d472e7e8eeed991b4caa new_market 894 96,017 37-37 58084cda72514fe381a8abb7c1f126a32c7ac58a21b35a32efe77da3bcdff1a6 price_change 96,372,244 967,981,290 38-405 1c28efe94350109ecffae5abd7d38f046c537bbfe7a94290faacfbabb1828ff4 tick_size_change 8,448 308,220 406-406 08dbf15abbd37fce72dd07faa0a73b9e02cac9b2e2b2dc7a8abc128776aaeeb1 EVENT MIX count share price_change 96,372,244 91.39% best_bid_ask 8,466,960 8.03% book 521,462 0.49% last_trade_price 80,005 0.08% tick_size_change 8,448 <0.01% market_resolved 2,143 <0.01% new_market 894 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,467,033 8,466,960 73 96,573 PARTIAL book 521,482 521,462 20 174,379 PARTIAL last_trade_price 80,005 80,005 0 5,200 PARTIAL market_resolved 2,143 2,143 0 1,948 PARTIAL new_market 894 894 0 622 PARTIAL price_change 96,373,048 96,372,244 804 137,732 PARTIAL tick_size_change 8,448 8,448 0 2,112 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 8,093,148 54 40ms 52ms 350ms 13.1s 0 transport_latency_assumed best_bid_ask c 8,466,675 518 4ms 8ms 68ms 8.1s 0 transport_latency_assumed best_bid_ask e 8,445,743 8,445,670 43ms 115ms 1.9s 19.7s 0 transport_latency_assumed best_bid_ask h 8,466,194 20,718 12ms 20ms 115ms 28.8s 0 transport_latency_assumed book a 505,801 346,945 40.4s 6.6h 26.1d 92.7d 0 book_staleness book c 165,986 2,047 7ms 27ms 3.7s 74.1d 0 book_staleness book e 164,328 164,326 88ms 7.3s 1.3h 32.3d 0 book_staleness book h 164,774 8,144 21ms 126ms 965ms 74.1d 0 book_staleness last_trade_price a 76,508 5 56ms 2.3s 9.4s 13.1s 0 transport_latency_assumed last_trade_price c 79,955 5 9ms 37ms 193ms 5.1s 0 transport_latency_assumed last_trade_price e 76,508 76,508 70ms 5.4s 14.1s 19.8s 0 transport_latency_assumed last_trade_price h 79,977 3,487 18ms 115ms 723ms 6.4s 0 transport_latency_assumed market_resolved a 1,984 194 41ms 363ms 5.1min 5.2min 0 transport_latency_assumed market_resolved c 1,948 not meas. 4ms 8ms 45.0s 1.0min 0 transport_latency_assumed market_resolved e 1,948 1,948 43ms 208ms 44.7s 1.0min 0 transport_latency_assumed market_resolved h 1,948 1 13ms 42ms 44.6s 1.0min 0 transport_latency_assumed new_market a 624 38 173ms 14.3s 22.3s 5.9min 0 transport_latency_assumed new_market c 622 39 51ms 15.4s 21.7s 2.8min 0 transport_latency_assumed new_market e 622 622 194ms 16.0s 22.8s 2.8min 0 transport_latency_assumed new_market h 622 195 78ms 13.1s 19.6s 1.4min 0 transport_latency_assumed price_change a 92,156,731 5,332 40ms 77ms 1.8s 13.1s 0 transport_latency_assumed price_change c 96,358,212 20,394 4ms 8ms 94ms 9.4s 0 transport_latency_assumed price_change e 95,756,500 95,755,702 44ms 178ms 5.9s 19.8s 0 transport_latency_assumed price_change h 96,324,948 590,816 13ms 22ms 167ms 28.8s 0 transport_latency_assumed tick_size_change a 8,348 not meas. 39ms 45ms 116ms 845ms 0 transport_latency_assumed tick_size_change c 8,448 not meas. 4ms 7ms 23ms 250ms 0 transport_latency_assumed tick_size_change e 8,448 8,448 43ms 112ms 234ms 19.6s 0 transport_latency_assumed tick_size_change h 8,448 not meas. 12ms 17ms 53ms 265ms 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/15/2026-08-30T15.parquet sha256sum 2026-08-30T15.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.