Hour audit: 2026-09-04T16
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.
No findings
Every check that could be evaluated for this hour passed. That is not the same as the hour being perfect: it means the records this archive keeps about it agree with each other and with the corpus ledger.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-04T16 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-04T16:00:00.032872018+00:00 · last event 2026-09-04T16:59:59.999998627+00:00
VOLUME 113,415,765 rows · 1,182,233,650 bytes (1.10 GiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured c: 112,144,853 · h: 112,120,297 · e: 111,839,207 · b: 98,434,952 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 10,259 (0.01%) · h: 329,484 (0.29%) · e: 111,838,048 (98.61%) · b: 1,237,974 (1.09%) (rows of the merged file that came from it; these partition it)
5 product-machine pairs publish no supplied count; the figures above still sum to the file's 113,415,765 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 229bdbc6787fb6ca497a4b9fc1b79d110878499be14ea6488ba6fe07a4873548
the corpus checksum ledger names this file with the same digest
joined 113,417,058 to merged 113,415,765, minus 1,293 (minus 0.0011%)
boundary drops 1,293 · 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-04T18:40:57Z as bceh
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 8/8 pass
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
PASS every expected machine contributed
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,499,636 118,298,903 0-40 babfacc0b568efa03bd0551518628940674d0a9714cab914247630f27681e06d book 1,304,909 80,382,178 41-45 7cd3c19a271053113b6dbad84f394b83503414ce1af7fe329b0584a492719094 last_trade_price 72,735 4,078,851 46-46 34b5a523780a16b2e94295c09cd54e154a30081ea0f6b8414e2e647c0086898f market_resolved 1,282 201,631 47-47 60a6c69bf083f931066436a65c0f0f50336a22f408db4f980c0e4e0254fb853d new_market 3,929 386,562 48-48 c4eeac6acec2912a05cac2c142063eb8a7510cd7b9cb020a6b0480b53bdc39d3 price_change 101,529,474 977,455,224 49-436 b1e7e516ef0ee0520f28279325d310adbfe2c88840f5adb7ce85318eebf81c2c tick_size_change 3,800 139,043 437-437 a22e1ab2dd81f18f35ccd8e4ab5e9743ac283af66315ced567e2501b26ffb614 EVENT MIX count share price_change 101,529,474 89.52% best_bid_ask 10,499,636 9.26% book 1,304,909 1.15% last_trade_price 72,735 0.06% new_market 3,929 <0.01% tick_size_change 3,800 <0.01% market_resolved 1,282 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,499,743 10,499,636 107 2,055 FULL book 1,304,929 1,304,909 20 186,378 FULL last_trade_price 72,735 72,735 0 252 FULL market_resolved 1,282 1,282 0 100 FULL new_market 3,929 3,929 0 2 FULL price_change 101,530,640 101,529,474 1,166 801 FULL tick_size_change 3,800 3,800 0 113 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 9,170,386 456 48ms 74ms 386ms 11.4s 0 transport_latency_assumed best_bid_ask c 10,497,668 1,541 4ms 10ms 170ms 3.9s 0 transport_latency_assumed best_bid_ask e 10,493,258 10,493,163 44ms 77ms 438ms 23.2s 0 transport_latency_assumed best_bid_ask h 10,496,500 4,476 18ms 32ms 492ms 57.0s 0 transport_latency_assumed book b 1,275,996 1,143,513 2.8min 15.5h 33.2d 97.8d 0 book_staleness book c 154,636 2,066 6ms 35ms 3.4s 79.1d 0 book_staleness book e 155,594 155,594 47ms 410ms 2.7min 78.9d 0 book_staleness book h 154,718 3,736 23ms 102ms 3.9s 79.1d 0 book_staleness last_trade_price b 61,811 4 60ms 298ms 4.2s 11.4s 0 transport_latency_assumed last_trade_price c 72,673 7 9ms 42ms 300ms 5.0s 0 transport_latency_assumed last_trade_price e 72,164 72,164 53ms 276ms 7.8s 23.2s 0 transport_latency_assumed last_trade_price h 72,714 560 24ms 84ms 976ms 53.7s 0 transport_latency_assumed market_resolved b 1,106 118 56ms 611ms 8.0min 9.3min 0 transport_latency_assumed market_resolved c 1,164 not meas. 4ms 23ms 51.1s 54.0s 0 transport_latency_assumed market_resolved e 1,164 1,164 46ms 355ms 56.7s 59.6s 0 transport_latency_assumed market_resolved h 1,164 not meas. 19ms 164ms 52.5s 55.4s 0 transport_latency_assumed new_market b 2,600 429 283ms 4.2min 6.8min 7.1min 0 transport_latency_assumed new_market c 2,520 235 99ms 17.7s 38.5s 25.4d 0 transport_latency_assumed new_market e 2,519 2,519 213ms 18.4s 39.0s 2.1min 0 transport_latency_assumed new_market h 2,519 746 157ms 16.8s 41.3s 25.3d 0 transport_latency_assumed price_change b 87,919,705 93,454 48ms 90ms 580ms 11.4s 0 transport_latency_assumed price_change c 101,412,392 6,410 4ms 11ms 183ms 5.8s 0 transport_latency_assumed price_change e 101,110,708 101,109,644 44ms 103ms 793ms 23.2s 0 transport_latency_assumed price_change h 101,388,882 319,966 18ms 36ms 473ms 57.1s 0 transport_latency_assumed tick_size_change b 3,348 not meas. 49ms 80ms 388ms 755ms 0 transport_latency_assumed tick_size_change c 3,800 not meas. 4ms 9ms 75ms 398ms 0 transport_latency_assumed tick_size_change e 3,800 3,800 44ms 98ms 211ms 685ms 0 transport_latency_assumed tick_size_change h 3,800 not meas. 18ms 36ms 197ms 56.6s 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-04/16/2026-09-04T16.parquet sha256sum 2026-09-04T16.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.