Hour audit: 2026-09-03T04
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-03T04 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-03T04:00:00.034195813+00:00 · last event 2026-09-03T04:59:59.999986116+00:00
VOLUME 92,619,080 rows · 912,949,259 bytes (870.66 MiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured c: 92,484,345 · e: 92,247,442 · h: 91,256,519 · b: 89,893,948 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 39,367 (0.04%) · e: 92,246,447 (99.60%) · h: 278,954 (0.30%) · b: 54,312 (0.06%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 92,619,080 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 1e57fbfd03b9ea4e7edb944335c84f4045af630404c07287a4bfa8da192ea64d
the corpus checksum ledger names this file with the same digest
joined 92,620,353 to merged 92,619,080, minus 1,273 (minus 0.0014%)
boundary drops 1,273 · 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-03T05:51:45Z 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 8,591,298 95,713,495 0-32 0c4334b354d157347a8c3606fcd3663119bd08c54e2ef26b321e5913bdaccb43 book 286,000 27,494,109 33-34 25a1722ba8e8ab5d2c65c5201a141a85330bec0c49e3f97e5945274f00746757 last_trade_price 61,172 3,312,349 35-35 a21d0d613f7e7852c931a771bac8f65b861419b0e6a4a0ae9ab0b5cdd0ead640 market_resolved 1,321 205,368 36-36 af0055f08d3df26b88c3ea78ca8d01998d9f4e85789373fe3369d627f2a41d27 new_market 2,963 308,887 37-37 a8ed27cf4dde9a36ebb388bd3715e6cb446d893d011ef3c9ef989441f9bca035 price_change 83,674,062 784,772,435 38-357 715c334a2600e8e8a9022f6c0c1b4a69bdf7c26d1ba3fccefa62e1d9013fb3ae tick_size_change 2,264 83,671 358-358 1d1a6640d647008553674880b9f247e8438c0e5a3ac4ec8307dcfb233602f00f EVENT MIX count share price_change 83,674,062 90.34% best_bid_ask 8,591,298 9.28% book 286,000 0.31% last_trade_price 61,172 0.07% new_market 2,963 <0.01% tick_size_change 2,264 <0.01% market_resolved 1,321 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,591,396 8,591,298 98 2,924 FULL book 286,006 286,000 6 67,080 FULL last_trade_price 61,173 61,172 1 125 FULL market_resolved 1,321 1,321 0 49 FULL new_market 2,963 2,963 0 0 FULL price_change 83,675,230 83,674,062 1,168 4,773 FULL tick_size_change 2,264 2,264 0 23 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 8,345,786 80 55ms 83ms 643ms 23.9s 0 transport_latency_assumed best_bid_ask c 8,590,750 622 4ms 7ms 203ms 3.1s 0 transport_latency_assumed best_bid_ask e 8,583,046 8,582,966 41ms 98ms 972ms 32.9s 0 transport_latency_assumed best_bid_ask h 8,482,066 7,630 17ms 24ms 370ms 34.0s 0 transport_latency_assumed book b 186,847 53,355 169ms 2.8h 21.6d 94.7d 0 book_staleness book c 162,453 30,846 7ms 11.9min 11.6d 96.3d 0 book_staleness book e 148,769 148,767 80ms 1.5min 3.5d 96.3d 0 book_staleness book h 179,778 53,032 42ms 1.6h 11.6d 77.8d 0 book_staleness last_trade_price b 59,522 2 73ms 939ms 8.8s 24.6s 0 transport_latency_assumed last_trade_price c 61,128 11 10ms 41ms 291ms 5.2s 0 transport_latency_assumed last_trade_price e 60,013 60,012 60ms 2.0s 10.7s 33.1s 0 transport_latency_assumed last_trade_price h 60,846 1,147 24ms 224ms 1.6s 11.2s 0 transport_latency_assumed market_resolved b 1,244 23 56ms 212ms 1.4s 2.5min 0 transport_latency_assumed market_resolved c 1,277 not meas. 4ms 7ms 56.1s 1.0min 0 transport_latency_assumed market_resolved e 1,277 1,277 41ms 183ms 5.9s 1.0min 0 transport_latency_assumed market_resolved h 1,260 21 17ms 88ms 1.0min 2.5min 0 transport_latency_assumed new_market b 2,017 82 297ms 20.5s 1.4min 1.8min 0 transport_latency_assumed new_market c 2,017 428 103ms 20.2s 1.4min 2.4min 0 transport_latency_assumed new_market e 2,017 2,017 247ms 21.7s 1.4min 1.5min 0 transport_latency_assumed new_market h 2,017 436 188ms 21.3s 1.5min 1.6min 0 transport_latency_assumed price_change b 81,296,320 770 55ms 103ms 1.2s 24.6s 0 transport_latency_assumed price_change c 83,664,456 7,460 4ms 7ms 221ms 3.4s 0 transport_latency_assumed price_change e 83,450,056 83,449,144 41ms 129ms 2.8s 33.4s 0 transport_latency_assumed price_change h 82,528,332 216,688 17ms 29ms 455ms 46.1s 0 transport_latency_assumed tick_size_change b 2,212 not meas. 55ms 87ms 690ms 833ms 0 transport_latency_assumed tick_size_change c 2,264 not meas. 4ms 8ms 456ms 590ms 0 transport_latency_assumed tick_size_change e 2,264 2,264 41ms 120ms 877ms 4.4s 0 transport_latency_assumed tick_size_change h 2,220 not meas. 17ms 38ms 558ms 1.2s 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-03/04/2026-09-03T04.parquet sha256sum 2026-09-03T04.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.