Hour audit: 2026-08-30T03
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-30T03 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-30T03:00:00.039499618+00:00 · last event 2026-08-30T03:59:59.999990313+00:00
VOLUME 109,039,255 rows · 1,113,410,847 bytes (1.04 GiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured c: 108,687,279 · h: 108,595,294 · e: 108,502,260 · a: 104,771,165 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 91,694 (0.08%) · h: 111,149 (0.10%) · e: 108,501,995 (99.51%) · a: 334,417 (0.31%) (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 109,039,255 rows exactly, so those pairs supplied none
5 expected (abceh), 1 contributed nothing: b
INTEGRITY sha256 01232310b62b5f0e2ce7d32b2b0c93b5c691a4ada148b3badd8d57dc83582186
the corpus checksum ledger names this file with the same digest
joined 109,039,716 to merged 109,039,255, minus 461 (minus 0.0004%)
boundary drops 461 · 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-30T06:04:13Z 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 10,090,442 110,402,282 0-38 c12e9d292f4fca091f0f1adfb352ea428678c552abacc39be38ee5397706f354 book 450,756 48,759,716 39-40 66f95b3f4148dc4476fc1411c6d27d3a5ec5b1864798807681ac5fa43c0a5361 last_trade_price 48,572 2,777,600 41-41 d15997f6fbc318f4f3d107cfd505e1f9a93f9d9cc33a8597e2d206a8353a2fa9 market_resolved 2,074 333,006 42-42 ed36c7c4a2ec116aad463cef5119c8420fa3a32aedd55c74359b56ca90905f30 new_market 365 44,345 43-43 c1175086823156c3242845ce25136d25407da10c337d79de576f1f191ec1f7e2 price_change 98,443,894 949,737,141 44-419 1bb42f128aeaea2617073d6a42674553aa36f218941f2576835ddd108d5b9e75 tick_size_change 3,152 115,169 420-420 ec192d54b667c1fdf24622109a6dc325de702ac079aa3670dd5786f6e937301f EVENT MIX count share price_change 98,443,894 90.28% best_bid_ask 10,090,442 9.25% book 450,756 0.41% last_trade_price 48,572 0.04% tick_size_change 3,152 <0.01% market_resolved 2,074 <0.01% new_market 365 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,090,472 10,090,442 30 68,129 PARTIAL book 450,762 450,756 6 169,563 PARTIAL last_trade_price 48,573 48,572 1 3,193 PARTIAL market_resolved 2,074 2,074 0 1,999 PARTIAL new_market 365 365 0 286 PARTIAL price_change 98,444,318 98,443,894 424 125,401 PARTIAL tick_size_change 3,152 3,152 0 788 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 9,707,460 10 38ms 44ms 155ms 9.4s 0 transport_latency_assumed best_bid_ask c 10,090,264 332 4ms 6ms 31ms 4.1s 0 transport_latency_assumed best_bid_ask e 10,083,768 10,083,738 43ms 78ms 1.2s 14.3s 0 transport_latency_assumed best_bid_ask h 10,090,084 6,362 12ms 17ms 67ms 5.6s 0 transport_latency_assumed book a 436,492 333,337 1.2min 7.4h 27.6d 92.2d 0 book_staleness book c 103,704 4,643 6ms 31ms 2.9h 92.2d 0 book_staleness book e 107,564 107,564 68ms 7.1s 7.7h 29.5d 0 book_staleness book h 102,666 5,212 18ms 109ms 37.2min 92.2d 0 book_staleness last_trade_price a 47,191 2 48ms 968ms 5.5s 9.4s 0 transport_latency_assumed last_trade_price c 48,532 6 9ms 35ms 156ms 5.0s 0 transport_latency_assumed last_trade_price e 47,765 47,764 62ms 2.6s 8.3s 14.3s 0 transport_latency_assumed last_trade_price h 48,559 800 18ms 73ms 666ms 5.0s 0 transport_latency_assumed market_resolved a 1,991 63 40ms 170ms 4.0min 6.5min 0 transport_latency_assumed market_resolved c 1,999 3 4ms 7ms 47ms 1.0min 0 transport_latency_assumed market_resolved e 1,999 1,999 44ms 165ms 572ms 1.0min 0 transport_latency_assumed market_resolved h 1,999 9 13ms 43ms 124ms 59.7s 0 transport_latency_assumed new_market a 287 19 112ms 11.0s 4.5min 2.6h 0 transport_latency_assumed new_market c 284 2 34ms 10.0s 16.6s 1.3min 0 transport_latency_assumed new_market e 284 284 170ms 10.2s 56.7s 1.2min 0 transport_latency_assumed new_market h 284 60 55ms 11.6s 17.5s 1.6min 0 transport_latency_assumed price_change a 94,574,740 986 38ms 49ms 326ms 9.4s 0 transport_latency_assumed price_change c 98,439,344 86,708 4ms 6ms 36ms 4.9s 0 transport_latency_assumed price_change e 98,257,728 98,257,494 43ms 108ms 2.2s 14.3s 0 transport_latency_assumed price_change h 98,348,550 98,706 12ms 18ms 76ms 6.3s 0 transport_latency_assumed tick_size_change a 3,004 not meas. 38ms 43ms 81ms 113ms 0 transport_latency_assumed tick_size_change c 3,152 not meas. 4ms 6ms 20ms 228ms 0 transport_latency_assumed tick_size_change e 3,152 3,152 43ms 95ms 1.6s 5.7s 0 transport_latency_assumed tick_size_change h 3,152 not meas. 12ms 14ms 34ms 1.3s 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/03/2026-08-30T03.parquet sha256sum 2026-08-30T03.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.