Hour audit: 2026-08-31T19
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-31T19 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-31T19:00:00.032248891+00:00 · last event 2026-08-31T19:59:59.999869844+00:00
VOLUME 100,997,978 rows · 1,018,181,999 bytes (971.01 MiB) · 7 products, all holding rows
WITNESSES ceh — 3 machines contributed rows
captured c: 100,981,074 · h: 100,852,352 · e: 100,383,410 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 68,626 (0.07%) · h: 547,134 (0.54%) · e: 100,382,218 (99.39%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 100,997,978 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 7656acf09670ad036dfb506024344dc0bf0c3d934efbf68c335ebd2af30a2a71
the corpus checksum ledger names this file with the same digest
joined 101,000,646 to merged 100,997,978, minus 2,668 (minus 0.0026%)
boundary drops 2,668 · 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-02T03:45:31Z 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,466,595 98,364,487 0-32 d869a7a25f7617b63ea926ee100b11ba7ca8c09c4cb1dee157cecb9a8538ff05 book 164,831 16,025,335 33-33 790afc5b6f8b69eaa911f708e7f433127e23ad63bf9197b95fd751f8fb1a6504 last_trade_price 71,580 4,004,468 34-34 5619dd9807f7392c97e0484f7208d57537b107d524f30cbaf8951cdcfdbc19e6 market_resolved 1,476 240,359 35-35 b5dd269b010bbb4098658030788e6240640d0ce7216a0d93de88a801ee6e8f46 new_market 4,960 533,780 36-36 e5d936bff2686e6cfa37f1a01218219b8481b1de9cdd54f4268a147c44a4a29a price_change 92,284,344 897,708,701 37-389 f3dbfdf20b9746a72bda3b56591cc51ff617a9c4bb25f5089116ac2d25ad976d tick_size_change 4,192 153,807 390-390 1a70c8ddecb0b382c1641432f171a6bd701465756428861af3e66eb5d5a66ecd EVENT MIX count share price_change 92,284,344 91.37% best_bid_ask 8,466,595 8.38% book 164,831 0.16% last_trade_price 71,580 0.07% new_market 4,960 <0.01% tick_size_change 4,192 <0.01% market_resolved 1,476 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,466,883 8,466,595 288 90,611 PARTIAL book 164,839 164,831 8 9,971 PARTIAL last_trade_price 71,582 71,580 2 3,849 PARTIAL market_resolved 1,476 1,476 0 1,458 PARTIAL new_market 4,960 4,960 0 3,434 PARTIAL price_change 92,286,714 92,284,344 2,370 135,950 PARTIAL tick_size_change 4,192 4,192 0 1,048 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,466,221 595 5ms 12ms 227ms 5.7s 0 transport_latency_assumed best_bid_ask e 8,451,306 8,451,190 45ms 161ms 2.7s 39.3s 0 transport_latency_assumed best_bid_ask h 8,465,588 14,810 13ms 30ms 722ms 1.6min 0 transport_latency_assumed book c 154,899 2,197 8ms 73ms 19.3s 75.3d 0 book_staleness book e 155,049 155,045 104ms 8.5s 1.0h 4.4d 0 book_staleness book h 154,071 7,589 22ms 405ms 41.1s 75.4d 0 book_staleness last_trade_price c 71,566 12 10ms 49ms 317ms 5.0s 0 transport_latency_assumed last_trade_price e 68,812 68,812 79ms 5.3s 17.0s 39.3s 0 transport_latency_assumed last_trade_price h 71,556 2,756 21ms 223ms 19.1s 1.6min 0 transport_latency_assumed market_resolved c 1,458 4 5ms 12ms 46.9s 1.0min 0 transport_latency_assumed market_resolved e 1,457 1,457 45ms 285ms 39.6s 1.1min 0 transport_latency_assumed market_resolved h 1,458 15 14ms 55ms 513ms 44.0s 0 transport_latency_assumed new_market c 3,434 534 191ms 2.1min 3.5min 3.8min 0 transport_latency_assumed new_market e 3,433 3,433 146ms 2.1min 3.4min 3.9min 0 transport_latency_assumed new_market h 3,433 993 210ms 2.1min 3.7min 45.1min 0 transport_latency_assumed price_change c 92,279,304 65,284 5ms 14ms 243ms 7.3s 0 transport_latency_assumed price_change e 91,699,173 91,698,101 45ms 277ms 8.0s 39.4s 0 transport_latency_assumed price_change h 92,152,054 520,959 14ms 40ms 2.1s 1.6min 0 transport_latency_assumed tick_size_change c 4,192 not meas. 5ms 12ms 179ms 521ms 0 transport_latency_assumed tick_size_change e 4,180 4,180 45ms 122ms 910ms 16.3s 0 transport_latency_assumed tick_size_change h 4,192 12 14ms 29ms 468ms 30.3s 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/19/2026-08-31T19.parquet sha256sum 2026-08-31T19.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.