Hour audit: 2026-08-31T22
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-08-31T22 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-31T22:00:00.035068849+00:00 · last event 2026-08-31T22:59:59.999976472+00:00
VOLUME 82,220,563 rows · 823,648,510 bytes (785.49 MiB) · 7 products, all holding rows
WITNESSES ceh — 3 machines contributed rows
captured c: 82,208,470 · h: 82,123,110 · e: 81,898,264 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 40,945 (0.05%) · h: 282,004 (0.34%) · e: 81,897,614 (99.61%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 82,220,563 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 7cadfded2b05b067f4874e25d57ca96552586c6447d2f4828b808184469114b1
the corpus checksum ledger names this file with the same digest
joined 82,221,213 to merged 82,220,563, minus 650 (minus 0.0008%)
boundary drops 650 · 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:22:04Z 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 7,188,427 90,634,216 0-27 de6cdfff5c546f9dc4df6bfc8947141659b9f7cbc512b9349991256e5db50252 book 121,732 11,166,847 28-28 938bdce5a7775a95cf500f379fd8dedb0c1463e62f73dc12fbb31e8874d5b10f last_trade_price 54,874 3,119,159 29-29 5814f957db5d83af15d77b887a9524d52630e67316387ecadc6aa2f4602f1f47 market_resolved 1,409 229,090 30-30 88a1476656d77ac81213a23638b194099e251ca785904d68f8ad427f477cef0b new_market 1,163 134,981 31-31 01f8dcc4b5930886da0fde25ef4f1e80c08cea1c53786fe85bb84d0d58c6a624 price_change 74,850,818 717,346,081 32-317 a6f999697e5d599b789ad9c4445c6c2a120bc1578f60582f6841d2baa9e24c61 tick_size_change 2,140 78,687 318-318 f9196daa3438d75bcd431af7d3e189779839d1e2bb6425c11b52ae85bafc75e6 EVENT MIX count share price_change 74,850,818 91.04% best_bid_ask 7,188,427 8.74% book 121,732 0.15% last_trade_price 54,874 0.07% tick_size_change 2,140 <0.01% market_resolved 1,409 <0.01% new_market 1,163 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 7,188,477 7,188,427 50 119,375 PARTIAL book 121,732 121,732 0 7,717 PARTIAL last_trade_price 54,874 54,874 0 3,482 PARTIAL market_resolved 1,409 1,409 0 1,407 PARTIAL new_market 1,163 1,163 0 861 PARTIAL price_change 74,851,418 74,850,818 600 151,321 PARTIAL tick_size_change 2,140 2,140 0 535 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 7,188,295 306 4ms 7ms 104ms 6.6s 0 transport_latency_assumed best_bid_ask e 7,186,704 7,186,654 43ms 104ms 824ms 17.9s 0 transport_latency_assumed best_bid_ask h 7,187,965 1,467 12ms 17ms 137ms 7.1s 0 transport_latency_assumed book c 118,552 5,102 7ms 45ms 9.6min 94.0d 0 book_staleness book e 115,728 115,728 89ms 4.3s 1.2min 2.0d 0 book_staleness book h 114,142 902 19ms 128ms 2.2s 75.5d 0 book_staleness last_trade_price c 54,857 10 10ms 39ms 217ms 4.8s 0 transport_latency_assumed last_trade_price e 54,837 54,837 80ms 3.5s 10.4s 17.9s 0 transport_latency_assumed last_trade_price h 54,848 27 18ms 108ms 596ms 5.4s 0 transport_latency_assumed market_resolved c 1,407 2 4ms 7ms 219ms 1.0min 0 transport_latency_assumed market_resolved e 1,406 1,406 44ms 255ms 671ms 8.2s 0 transport_latency_assumed market_resolved h 1,407 1 12ms 25ms 155ms 3.4s 0 transport_latency_assumed new_market c 861 92 56ms 12.6s 35.9s 1.8min 0 transport_latency_assumed new_market e 861 861 201ms 12.3s 29.8s 2.1min 0 transport_latency_assumed new_market h 861 210 105ms 14.7s 31.8s 55.1s 0 transport_latency_assumed price_change c 74,842,358 35,433 4ms 8ms 177ms 6.7s 0 transport_latency_assumed price_change e 74,536,588 74,535,988 43ms 144ms 2.6s 19.2s 0 transport_latency_assumed price_change h 74,761,747 279,397 12ms 20ms 224ms 8.1s 0 transport_latency_assumed tick_size_change c 2,140 not meas. 4ms 7ms 26ms 154ms 0 transport_latency_assumed tick_size_change e 2,140 2,140 43ms 68ms 426ms 7.2s 0 transport_latency_assumed tick_size_change h 2,140 not meas. 12ms 15ms 49ms 85ms 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/22/2026-08-31T22.parquet sha256sum 2026-08-31T22.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.