Hour audit: 2026-09-01T02
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 4 machines expected to be capturing this hour, 1 contributed no rows: b. The hour is still whole on minutes; it simply rests on 3 machines rather than 4.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-01T02 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-01T02:00:00.031638193+00:00 · last event 2026-09-01T02:59:59.999982927+00:00
VOLUME 88,755,729 rows · 867,338,255 bytes (827.16 MiB) · 7 products, all holding rows
WITNESSES ceh — 3 machines contributed rows
captured c: 88,593,594 · h: 88,529,652 · e: 88,278,407 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 39,465 (0.04%) · h: 438,675 (0.49%) · e: 88,277,589 (99.46%) (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 88,755,729 rows exactly, so those pairs supplied none
4 expected (bceh), 1 contributed nothing: b
the listing string reads "bche"; the letters above are the machines whose rows are in the file
INTEGRITY sha256 e83321989d91b4d4d210e88998e984f6ceb81eebf05596476f75df0a11daed0d
the corpus checksum ledger names this file with the same digest
joined 88,756,547 to merged 88,755,729, minus 818 (minus 0.0009%)
boundary drops 818 · 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-09-02T04:53:48Z as ceh
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,366,434 90,571,449 0-31 31be6e994f11d4096a89262caaa02a6562acfe73a7d19750345a4761d8902163 book 279,338 29,060,241 32-33 e1ba2d12d7005dcd586c71b1f3d260a0bb601714bd8ed6d04c554ac1502202b3 last_trade_price 56,286 3,137,818 34-34 ff83ed40671d6f9c2816dc9af2f4b55b0d9bb8cbfec18eb752d2d7e27dcd2311 market_resolved 927 151,808 35-35 48ebe9aaf07da5471ac6ed21bff4e5d66fdafc0542b17c169cd92907d3441792 new_market 1,092 123,398 36-36 49607975dc1ddac19c670f3ea3674062fff7582666df636ea9fa1dfb98810208 price_change 80,049,056 743,187,259 37-342 2829ed9dbcb23975252fa6a248e3532a102e1d4f09f5a69bb9360e521c70412c tick_size_change 2,596 93,851 343-343 a3ca06e85361bc217b532a8a55c92589d337570465d076c770d5bfb0e4dc73db EVENT MIX count share price_change 80,049,056 90.19% best_bid_ask 8,366,434 9.43% book 279,338 0.31% last_trade_price 56,286 0.06% tick_size_change 2,596 <0.01% new_market 1,092 <0.01% market_resolved 927 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,366,526 8,366,434 92 66,850 PARTIAL book 279,338 279,338 0 77,355 PARTIAL last_trade_price 56,286 56,286 0 3,154 PARTIAL market_resolved 927 927 0 924 PARTIAL new_market 1,092 1,092 0 797 PARTIAL price_change 80,049,782 80,049,056 726 125,732 PARTIAL tick_size_change 2,596 2,596 0 649 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,366,190 340 4ms 7ms 64ms 1.6s 0 transport_latency_assumed best_bid_ask e 8,347,303 8,347,211 44ms 93ms 875ms 27.1s 0 transport_latency_assumed best_bid_ask h 8,365,994 18,883 12ms 17ms 139ms 8.2s 0 transport_latency_assumed book c 129,579 11,250 7ms 1.8s 10.7h 94.2d 0 book_staleness book e 251,162 251,162 11.4s 1.6h 23.5d 94.2d 0 book_staleness book h 131,340 16,926 21ms 8.5s 1.4d 75.7d 0 book_staleness last_trade_price c 56,258 2 9ms 39ms 208ms 5.0s 0 transport_latency_assumed last_trade_price e 54,367 54,367 96ms 4.9s 14.4s 27.1s 0 transport_latency_assumed last_trade_price h 56,263 1,917 19ms 182ms 644ms 7.5s 0 transport_latency_assumed market_resolved c 924 not meas. 4ms 8ms 160ms 59.2s 0 transport_latency_assumed market_resolved e 924 924 44ms 179ms 665ms 59.9s 0 transport_latency_assumed market_resolved h 924 3 13ms 39ms 140ms 52.4s 0 transport_latency_assumed new_market c 797 133 58ms 12.3s 14.9s 17.6s 0 transport_latency_assumed new_market e 797 797 202ms 11.8s 15.6s 1.1min 0 transport_latency_assumed new_market h 797 162 121ms 12.4s 16.3s 1.0min 0 transport_latency_assumed price_change c 80,037,250 27,740 4ms 7ms 87ms 3.3s 0 transport_latency_assumed price_change e 79,621,258 79,620,532 44ms 124ms 4.4s 27.2s 0 transport_latency_assumed price_change h 79,971,738 400,784 12ms 19ms 217ms 8.3s 0 transport_latency_assumed tick_size_change c 2,596 not meas. 4ms 9ms 49ms 339ms 0 transport_latency_assumed tick_size_change e 2,596 2,596 44ms 110ms 350ms 3.7s 0 transport_latency_assumed tick_size_change h 2,596 not meas. 12ms 22ms 76ms 469ms 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-09-01/02/2026-09-01T02.parquet sha256sum 2026-09-01T02.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.