Hour audit: 2026-08-31T02
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-31T02 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-31T02:00:00.038414285+00:00 · last event 2026-08-31T02:59:59.999984796+00:00
VOLUME 76,726,719 rows · 750,685,894 bytes (715.91 MiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured c: 76,711,076 · h: 76,658,923 · a: 76,573,432 · e: 76,146,816 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 30,431 (0.04%) · h: 546,159 (0.71%) · a: 3,895 (0.01%) · e: 76,146,234 (99.24%) (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 76,726,719 rows exactly, so those pairs supplied none
5 expected (abceh), 1 contributed nothing: b
INTEGRITY sha256 943032e90fdb701ecde86e2c80d6e62e8dbbb9723c5cf9ee8f39742f9cf87788
the corpus checksum ledger names this file with the same digest
joined 76,727,303 to merged 76,726,719, minus 584 (minus 0.0008%)
boundary drops 584 · 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-31T03:49:44Z 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 7,571,624 83,226,145 0-28 e75e37c26b687bf9dd56ce1afdcf4bc3868b44f47262218c060c6723319d6544 book 140,039 12,670,412 29-29 1b8f0e0ff1f8f28d2ecc7488d1a715a0acdf7a163bf36e10cc289d1f3d1f4ed5 last_trade_price 61,327 3,370,578 30-30 8376f18abce36753f448123fcf087dedbacdf9d913550909528fba1e386090b3 market_resolved 1,224 197,207 31-31 38171c2238cd3b5d9e540417f4ac8f4e406014cbc803197eb9e9bc956e76645d new_market 525 56,738 32-32 42c68d9a4fe7a98d79b2a03a2d5cd2db13c39dfe61496051416a477ab085e0a2 price_change 68,950,092 650,216,694 33-296 227cb9ddb1e111bda22c0709c7561cfe7aa689809a3945e86525cf4a349fedfd tick_size_change 1,888 69,481 297-297 279577dee73d96645a40d6f841052c7c8ff5d57b5147c399815549778ca0abe7 EVENT MIX count share price_change 68,950,092 89.86% best_bid_ask 7,571,624 9.87% book 140,039 0.18% last_trade_price 61,327 0.08% tick_size_change 1,888 <0.01% market_resolved 1,224 <0.01% new_market 525 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 7,571,680 7,571,624 56 65,115 PARTIAL book 140,039 140,039 0 7,128 PARTIAL last_trade_price 61,327 61,327 0 2,880 PARTIAL market_resolved 1,224 1,224 0 1,220 PARTIAL new_market 525 525 0 368 PARTIAL price_change 68,950,620 68,950,092 528 118,252 PARTIAL tick_size_change 1,888 1,888 0 472 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 7,567,204 22 39ms 48ms 321ms 18.5s 0 transport_latency_assumed best_bid_ask c 7,571,476 358 4ms 6ms 40ms 1.5s 0 transport_latency_assumed best_bid_ask e 7,549,333 7,549,277 42ms 84ms 1.9s 22.1s 0 transport_latency_assumed best_bid_ask h 7,571,174 21,967 12ms 16ms 82ms 6.2s 0 transport_latency_assumed book a 125,964 2,386 75ms 3.5s 2.6min 74.5d 0 book_staleness book c 129,124 3,328 6ms 24ms 12.2min 74.6d 0 book_staleness book e 127,323 127,323 127ms 9.4s 1.2h 3.3d 0 book_staleness book h 126,696 7,002 18ms 116ms 993ms 30.8d 0 book_staleness last_trade_price a 60,254 3 64ms 3.0s 10.8s 17.8s 0 transport_latency_assumed last_trade_price c 61,305 8 9ms 38ms 161ms 5.0s 0 transport_latency_assumed last_trade_price e 58,392 58,392 89ms 6.1s 14.7s 22.0s 0 transport_latency_assumed last_trade_price h 61,285 2,924 18ms 115ms 592ms 5.0s 0 transport_latency_assumed market_resolved a 1,220 4 40ms 221ms 508ms 1.0s 0 transport_latency_assumed market_resolved c 1,220 not meas. 4ms 6ms 39ms 182ms 0 transport_latency_assumed market_resolved e 1,216 1,216 42ms 191ms 601ms 4.5s 0 transport_latency_assumed market_resolved h 1,220 4 12ms 39ms 130ms 267ms 0 transport_latency_assumed new_market a 368 25 157ms 14.5s 27.4s 1.2min 0 transport_latency_assumed new_market c 368 44 48ms 15.3s 35.3s 59.1s 0 transport_latency_assumed new_market e 368 368 187ms 14.5s 26.7s 1.4min 0 transport_latency_assumed new_market h 368 88 72ms 12.8s 37.6s 1.3min 0 transport_latency_assumed price_change a 68,816,534 1,455 40ms 72ms 3.4s 18.6s 0 transport_latency_assumed price_change c 68,945,695 26,693 4ms 7ms 72ms 1.9s 0 transport_latency_assumed price_change e 68,408,308 68,407,782 43ms 147ms 7.9s 22.1s 0 transport_latency_assumed price_change h 68,896,292 514,162 12ms 19ms 162ms 6.2s 0 transport_latency_assumed tick_size_change a 1,888 not meas. 39ms 42ms 127ms 167ms 0 transport_latency_assumed tick_size_change c 1,888 not meas. 4ms 5ms 21ms 137ms 0 transport_latency_assumed tick_size_change e 1,876 1,876 43ms 93ms 255ms 4.4s 0 transport_latency_assumed tick_size_change h 1,888 12 12ms 14ms 28ms 109ms 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/02/2026-08-31T02.parquet sha256sum 2026-08-31T02.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.