Hour audit: 2026-08-30T19
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-30T19 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-30T19:00:00.027445064+00:00 · last event 2026-08-30T19:59:59.999974117+00:00
VOLUME 104,652,783 rows · 1,071,826,619 bytes (1022.17 MiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured c: 104,614,427 · h: 104,525,011 · a: 104,510,436 · e: 104,072,781 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 22,015 (0.02%) · h: 553,267 (0.53%) · a: 5,850 (0.01%) · e: 104,071,651 (99.44%) (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 104,652,783 rows exactly, so those pairs supplied none
5 expected (abceh), 1 contributed nothing: b
INTEGRITY sha256 88ba4afd6abeb7b2815d40610accd0e4cc18258d28f2bc8936f2d2f618d5edbd
the corpus checksum ledger names this file with the same digest
joined 104,653,964 to merged 104,652,783, minus 1,181 (minus 0.0011%)
boundary drops 1,181 · 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-30T20:55: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,110,648 95,012,914 0-30 aacc066155407cafe377069f7be59d5e6a026b25628b770c82f9a629a788fc96 book 159,561 15,468,808 31-31 93fba2492d8205d28bf7ae67329cb336256ff32daf168619aeb2dfabeafade2c last_trade_price 69,809 4,027,297 32-32 6226738238dcb90cc62f25ebc998b97da1fa1c5b13ba0b6374d4ac6dad824e56 market_resolved 2,321 365,361 33-33 46b866222cc2e472ec1d09c0f1a2d153f7a1aa15a1e94788719c8574608c2f65 new_market 3,728 371,498 34-34 4ec3b723731c083d6f84f749de15d715d262d818d20075c8029349f1634fccc7 price_change 96,299,680 955,143,630 35-402 50188e926ed5533b6a2b71d8e6c058077b6546890e5011bca24f68e71086486a tick_size_change 7,036 245,568 403-403 95dc4db7b3957d60f546be72ffd906c75ba7794849ddd7b5d9c6e14228df98ca EVENT MIX count share price_change 96,299,680 92.02% best_bid_ask 8,110,648 7.75% book 159,561 0.15% last_trade_price 69,809 0.07% tick_size_change 7,036 <0.01% new_market 3,728 <0.01% market_resolved 2,321 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,110,777 8,110,648 129 82,214 PARTIAL book 159,565 159,561 4 9,973 PARTIAL last_trade_price 69,809 69,809 0 4,824 PARTIAL market_resolved 2,321 2,321 0 2,263 PARTIAL new_market 3,728 3,728 0 2,416 PARTIAL price_change 96,300,728 96,299,680 1,048 136,803 PARTIAL tick_size_change 7,036 7,036 0 1,759 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 8,105,961 90 40ms 64ms 594ms 33.6s 0 transport_latency_assumed best_bid_ask c 8,109,570 612 5ms 10ms 253ms 9.1s 0 transport_latency_assumed best_bid_ask e 8,084,084 8,083,960 44ms 173ms 3.2s 34.6s 0 transport_latency_assumed best_bid_ask h 8,107,800 25,986 14ms 29ms 515ms 2.3min 0 transport_latency_assumed book a 147,677 2,594 47ms 1.7s 59.9s 92.9d 0 book_staleness book c 147,488 1,081 7ms 40ms 3.5s 74.2d 0 book_staleness book e 149,012 149,008 60ms 3.3s 9.9min 1.4d 0 book_staleness book h 147,636 6,878 21ms 227ms 55.0s 74.3d 0 book_staleness last_trade_price a 69,065 4 51ms 1.1s 8.8s 36.0s 0 transport_latency_assumed last_trade_price c 69,780 8 10ms 44ms 338ms 5.3s 0 transport_latency_assumed last_trade_price e 67,751 67,751 61ms 1.7s 14.8s 37.9s 0 transport_latency_assumed last_trade_price h 69,335 2,046 20ms 130ms 4.2s 2.3min 0 transport_latency_assumed market_resolved a 2,263 24 88ms 431ms 58.5s 2.2min 0 transport_latency_assumed market_resolved c 2,263 not meas. 5ms 59ms 57.4s 1.0min 0 transport_latency_assumed market_resolved e 2,263 2,263 86ms 663ms 58.8s 1.8min 0 transport_latency_assumed market_resolved h 2,263 34 18ms 105ms 51.0s 57.6s 0 transport_latency_assumed new_market a 2,416 172 158ms 31.6s 40.9s 3.7min 0 transport_latency_assumed new_market c 2,416 179 241ms 32.4s 40.9s 1.2min 0 transport_latency_assumed new_market e 2,416 2,416 362ms 31.3s 43.8s 26.6min 0 transport_latency_assumed new_market h 2,416 961 231ms 32.0s 40.5s 4.4min 0 transport_latency_assumed price_change a 96,176,018 2,966 40ms 83ms 1.0s 33.6s 0 transport_latency_assumed price_change c 96,275,874 20,135 5ms 10ms 260ms 9.3s 0 transport_latency_assumed price_change e 95,760,231 95,759,229 44ms 221ms 5.8s 34.7s 0 transport_latency_assumed price_change h 96,188,525 517,350 14ms 31ms 605ms 2.3min 0 transport_latency_assumed tick_size_change a 7,036 not meas. 39ms 44ms 538ms 25.0s 0 transport_latency_assumed tick_size_change c 7,036 not meas. 4ms 7ms 310ms 704ms 0 transport_latency_assumed tick_size_change e 7,024 7,024 44ms 110ms 1.0s 23.3s 0 transport_latency_assumed tick_size_change h 7,036 12 14ms 21ms 365ms 21.1s 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/19/2026-08-30T19.parquet sha256sum 2026-08-30T19.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.