Hour audit: 2026-08-31T00
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-31T00 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-31T00:00:00.040155613+00:00 · last event 2026-08-31T00:59:59.047106292+00:00
VOLUME 70,343,250 rows · 729,999,072 bytes (696.18 MiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured c: 70,270,953 · h: 70,207,919 · a: 70,067,014 · e: 69,748,123 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 71,343 (0.10%) · h: 484,110 (0.69%) · a: 40,984 (0.06%) · e: 69,746,813 (99.15%) (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 70,343,250 rows exactly, so those pairs supplied none
5 expected (abceh), 1 contributed nothing: b
INTEGRITY sha256 7193728c0e7022325441294ebfb8637024bf3c4c6564195332c79eb8d8fe57d8
the corpus checksum ledger names this file with the same digest
joined 70,344,564 to merged 70,343,250, minus 1,314 (minus 0.0019%)
boundary drops 1,314 · 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-31T01:48:24Z 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 an incident recorded by the venue intersects this hour: Venue in cancel-only mode for about half an hour, 2026-08-31T00:40Z to 2026-08-31T01:12ZThe 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 5,891,892 74,038,786 0-22 a9461e2f375706ba2cbf02dab5e8beb9e05123a9476578b6e070bed1b0f70619 book 207,369 21,276,441 23-23 8639d467937a603239c9adb738309b3e0d84ffd1b51aafa0365b75363b41dd9f last_trade_price 52,367 2,918,056 24-24 241ecf0b35b158412c490a2645e8f4fbf1ede5df6eb303f1e680b2b9d7e689e1 market_resolved 1,441 214,791 25-25 9109226ffde521c393aa19cac794508d9087c166babcccfa2ac92e7141b30f99 new_market 857 89,584 26-26 81a77f0c7dfcbe9c026231c2c30492300b576524bea45880d0e418d779acc5d2 price_change 64,186,716 630,562,196 27-271 38ee1e9b2a24bd51e2559e1bd3e8b942e1180cf5836b965b11a9366a67d31d50 tick_size_change 2,608 93,591 272-272 f909d1258b98edaf5c669dc53cdd89cf237cbb1c8a48d89cb4a816b172014ee8 EVENT MIX count share price_change 64,186,716 91.25% best_bid_ask 5,891,892 8.38% book 207,369 0.29% last_trade_price 52,367 0.07% tick_size_change 2,608 <0.01% market_resolved 1,441 <0.01% new_market 857 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 5,891,990 5,891,892 98 99,627 PARTIAL book 207,371 207,369 2 46,476 PARTIAL last_trade_price 52,367 52,367 0 2,915 PARTIAL market_resolved 1,441 1,441 0 1,345 PARTIAL new_market 857 857 0 577 PARTIAL price_change 64,187,930 64,186,716 1,214 138,492 PARTIAL tick_size_change 2,608 2,608 0 652 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 5,885,556 92 40ms 52ms 334ms 15.4s 0 transport_latency_assumed best_bid_ask c 5,891,579 332 4ms 7ms 59ms 3.9s 0 transport_latency_assumed best_bid_ask e 5,878,210 5,878,112 44ms 105ms 1.3s 22.5s 0 transport_latency_assumed best_bid_ask h 5,891,410 13,356 12ms 18ms 94ms 21.6s 0 transport_latency_assumed book a 147,308 38,146 153ms 14.8min 22.4d 74.6d 0 book_staleness book c 152,928 43,737 9ms 14.9min 22.4d 74.6d 0 book_staleness book e 111,651 111,651 108ms 9.9s 19.3h 32.4d 0 book_staleness book h 116,401 13,835 19ms 282ms 2.9h 93.1d 0 book_staleness last_trade_price a 51,184 5 60ms 2.2s 10.9s 15.4s 0 transport_latency_assumed last_trade_price c 52,348 4 9ms 36ms 160ms 4.8s 0 transport_latency_assumed last_trade_price e 49,811 49,811 76ms 5.3s 14.8s 22.5s 0 transport_latency_assumed last_trade_price h 52,346 2,547 18ms 83ms 531ms 21.3s 0 transport_latency_assumed market_resolved a 1,345 74 40ms 154ms 928ms 57.8s 0 transport_latency_assumed market_resolved c 1,345 20 4ms 7ms 421ms 1.0min 0 transport_latency_assumed market_resolved e 1,344 1,344 45ms 199ms 54.6s 59.5s 0 transport_latency_assumed market_resolved h 1,345 3 13ms 39ms 56.1s 1.0min 0 transport_latency_assumed new_market a 577 61 182ms 12.4s 24.6s 1.1min 0 transport_latency_assumed new_market c 577 90 41ms 12.2s 26.2s 2.7min 0 transport_latency_assumed new_market e 577 577 188ms 14.9s 30.9s 2.1min 0 transport_latency_assumed new_market h 577 129 76ms 18.0s 31.6s 58.5s 0 transport_latency_assumed price_change a 63,978,436 2,606 41ms 77ms 2.8s 15.4s 0 transport_latency_assumed price_change c 64,169,568 27,160 4ms 8ms 79ms 5.7s 0 transport_latency_assumed price_change e 63,703,922 63,702,710 45ms 148ms 6.9s 22.5s 0 transport_latency_assumed price_change h 64,143,232 454,240 12ms 20ms 137ms 21.7s 0 transport_latency_assumed tick_size_change a 2,608 not meas. 40ms 45ms 142ms 366ms 0 transport_latency_assumed tick_size_change c 2,608 not meas. 4ms 7ms 42ms 242ms 0 transport_latency_assumed tick_size_change e 2,608 2,608 45ms 108ms 194ms 654ms 0 transport_latency_assumed tick_size_change h 2,608 not meas. 12ms 19ms 56ms 107ms 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/00/2026-08-31T00.parquet sha256sum 2026-08-31T00.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.