Hour audit: 2026-08-31T21
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-31T21 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-31T21:00:00.039286118+00:00 · last event 2026-08-31T21:59:59.999982061+00:00
VOLUME 63,084,264 rows · 651,520,200 bytes (621.34 MiB) · 7 products, all holding rows
WITNESSES ceh — 3 machines contributed rows
captured c: 63,057,164 · h: 62,923,349 · e: 62,533,637 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 90,014 (0.14%) · h: 461,460 (0.73%) · e: 62,532,790 (99.13%) (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 63,084,264 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 d3b3959726e1dc5245e5a0d51b709171dd08a7b6d99214cd547de404687baeec
the corpus checksum ledger names this file with the same digest
joined 63,085,113 to merged 63,084,264, minus 849 (minus 0.0013%)
boundary drops 849 · 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:08:22Z 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 5,104,778 66,960,791 0-19 b015f667d77f33c689c27783cdee19b8c3745622747f162a5539bd1097347dbb book 202,763 20,638,968 20-20 729671495f94d9ff75b894566eba7c520bb96d08049d47d11e74609a0f37dce7 last_trade_price 56,857 3,246,616 21-21 b4ede5b53d354e8c7a4c05ac17793b95c2ef6a9d7ec836e8ff247a6c3170c180 market_resolved 1,487 239,713 22-22 fa57397a4cc93cb19d9642cabdabc6d66c9ddd3eed27de38702ea01178d7fed3 new_market 599 69,017 23-23 6d5b9324acbc04286d8474e8f06debf8fd603dcc7d5f4cbd765a95982df9ea46 price_change 57,715,064 559,543,049 24-244 eddbc9b2803fee75af0d58b921d66963fa48b664b1b581f4e59e325ff2b3e8dc tick_size_change 2,716 97,226 245-245 2135ff9a4ba75850e5a169959ef717a249114e58b880d922c52dbe5a23bc9757 EVENT MIX count share price_change 57,715,064 91.49% best_bid_ask 5,104,778 8.09% book 202,763 0.32% last_trade_price 56,857 0.09% tick_size_change 2,716 <0.01% market_resolved 1,487 <0.01% new_market 599 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 5,104,877 5,104,778 99 117,064 PARTIAL book 202,767 202,763 4 42,518 PARTIAL last_trade_price 56,857 56,857 0 3,577 PARTIAL market_resolved 1,487 1,487 0 1,487 PARTIAL new_market 599 599 0 452 PARTIAL price_change 57,715,810 57,715,064 746 150,687 PARTIAL tick_size_change 2,716 2,716 0 679 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 5,104,370 260 4ms 8ms 86ms 1.6s 0 transport_latency_assumed best_bid_ask e 5,093,586 5,093,487 43ms 107ms 1.6s 23.2s 0 transport_latency_assumed best_bid_ask h 5,104,290 11,031 13ms 18ms 143ms 5.4s 0 transport_latency_assumed book c 183,910 65,359 12ms 15.2min 23.3d 94.0d 0 book_staleness book e 128,649 128,647 128ms 31.9s 13.3h 33.3d 0 book_staleness book h 120,787 8,757 22ms 282ms 9.3min 75.5d 0 book_staleness last_trade_price c 56,841 10 10ms 39ms 228ms 5.0s 0 transport_latency_assumed last_trade_price e 54,632 54,632 81ms 4.4s 15.4s 22.9s 0 transport_latency_assumed last_trade_price h 56,830 2,215 19ms 166ms 1.2s 5.2s 0 transport_latency_assumed market_resolved c 1,487 not meas. 4ms 7ms 53.0s 55.5s 0 transport_latency_assumed market_resolved e 1,487 1,487 44ms 283ms 53.6s 56.1s 0 transport_latency_assumed market_resolved h 1,487 not meas. 13ms 48ms 58.2s 1.0min 0 transport_latency_assumed new_market c 452 24 42ms 11.6s 18.9s 1.3min 0 transport_latency_assumed new_market e 452 452 189ms 13.4s 18.3s 45.1s 0 transport_latency_assumed new_market h 452 123 80ms 14.6s 21.6s 5.1min 0 transport_latency_assumed price_change c 57,707,388 24,361 4ms 9ms 182ms 3.0s 0 transport_latency_assumed price_change e 57,252,155 57,251,409 44ms 175ms 6.2s 23.2s 0 transport_latency_assumed price_change h 57,636,787 439,294 13ms 23ms 257ms 6.7s 0 transport_latency_assumed tick_size_change c 2,716 not meas. 4ms 7ms 38ms 227ms 0 transport_latency_assumed tick_size_change e 2,676 2,676 44ms 114ms 539ms 8.9s 0 transport_latency_assumed tick_size_change h 2,716 40 13ms 15ms 97ms 292ms 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/21/2026-08-31T21.parquet sha256sum 2026-08-31T21.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.