Hour audit: 2026-09-04T09
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-04T09 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-04T09:00:00.001330482+00:00 · last event 2026-09-04T09:59:59.999986374+00:00
VOLUME 101,689,624 rows · 985,084,043 bytes (939.45 MiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured c: 101,585,808 · e: 81,807,811 · h: 79,194,055 · b: 74,838,742 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 9,378,583 (9.22%) · e: 81,807,077 (80.45%) · h: 10,462,048 (10.29%) · b: 41,916 (0.04%) (rows of the merged file that came from it; these partition it)
6 product-machine pairs publish no supplied count; the figures above still sum to the file's 101,689,624 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 cad04e53d96a7e2a735559145f80b7f50e1d85f43f960b8df8f501f1e25ed55a
the corpus checksum ledger names this file with the same digest
joined 101,690,540 to merged 101,689,624, minus 916 (minus 0.0009%)
boundary drops 916 · 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-04T10:51:26Z 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,951,262 97,499,472 0-34 9f4bde740a88a84688cbc4570e7b7bc5b72b515d63de112d45b748b0c053b2dc book 254,005 26,463,956 35-35 6adfece2551f145549a445778e127548c3e29eff9bfef06cb03120a854debc63 last_trade_price 70,090 3,822,060 36-36 5b4b0378e8bf49d7470da01d8c1c846ff9796078d0700c22badef9aa12b53382 market_resolved 576 95,084 37-37 59b755acd7720deeeb1b55fc9b60e7ac278cb93955e8bdfa1b0f562ac7f69573 new_market 786 94,349 38-38 3c657230062af09e7be439653c1bc0d55086954d2f20b54d3f5caf267b9c67d9 price_change 92,410,381 855,856,313 39-391 da5a1252802dc00a6d6b0c93b2bb1369c112ee257c0a79f361113b84b5bf3c3d tick_size_change 2,524 93,295 392-392 37af794d7914aae196204eaef3af3193f23453d8511c2ab57ff6c2c5ec71bd0a EVENT MIX count share price_change 92,410,381 90.87% best_bid_ask 8,951,262 8.80% book 254,005 0.25% last_trade_price 70,090 0.07% tick_size_change 2,524 <0.01% new_market 786 <0.01% market_resolved 576 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,951,358 8,951,262 96 64 FULL book 254,011 254,005 6 50,336 FULL last_trade_price 70,090 70,090 0 0 FULL market_resolved 576 576 0 0 FULL new_market 786 786 0 0 FULL price_change 92,411,195 92,410,381 814 86,338 FULL tick_size_change 2,524 2,524 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 8,949,018 not meas. 48ms 61ms 170ms 2.7s 0 transport_latency_assumed best_bid_ask c 8,951,130 480 4ms 8ms 56ms 1.9s 0 transport_latency_assumed best_bid_ask e 8,948,998 8,948,916 41ms 50ms 210ms 3.7s 0 transport_latency_assumed best_bid_ask h 8,950,048 1,866 18ms 24ms 104ms 8.3s 0 transport_latency_assumed book b 190,208 40,211 57ms 12.1min 12.8d 97.5d 0 book_staleness book c 165,964 18,325 7ms 28.8s 22.3h 97.5d 0 book_staleness book e 180,438 180,436 45ms 5.6min 12.8d 97.5d 0 book_staleness book h 160,802 15,033 23ms 1.0s 14.3h 79.0d 0 book_staleness last_trade_price b 69,989 2 56ms 137ms 623ms 5.0s 0 transport_latency_assumed last_trade_price c 70,053 8 9ms 38ms 214ms 5.0s 0 transport_latency_assumed last_trade_price e 69,890 69,890 48ms 160ms 1.6s 5.0s 0 transport_latency_assumed last_trade_price h 69,906 190 24ms 73ms 440ms 7.9s 0 transport_latency_assumed market_resolved b 568 not meas. 50ms 370ms 1.0min 1.0min 0 transport_latency_assumed market_resolved c 568 8 4ms 12ms 56.9s 57.0s 0 transport_latency_assumed market_resolved e 568 568 41ms 363ms 1.0min 1.0min 0 transport_latency_assumed market_resolved h 568 not meas. 18ms 154ms 1.0min 1.0min 0 transport_latency_assumed new_market b 642 3 174ms 491ms 57.6s 1.1min 0 transport_latency_assumed new_market c 642 51 47ms 183ms 48.5s 1.6min 0 transport_latency_assumed new_market e 642 642 148ms 19.1s 57.4s 1.9min 0 transport_latency_assumed new_market h 642 90 90ms 37.0s 1.3min 1.9min 0 transport_latency_assumed price_change b 65,625,793 1,700 48ms 63ms 224ms 2.8s 0 transport_latency_assumed price_change c 92,394,927 9,359,711 4ms 8ms 63ms 2.1s 0 transport_latency_assumed price_change e 72,604,751 72,604,101 41ms 62ms 287ms 3.7s 0 transport_latency_assumed price_change h 70,009,565 10,444,869 18ms 27ms 130ms 8.3s 0 transport_latency_assumed tick_size_change b 2,524 not meas. 48ms 67ms 149ms 282ms 0 transport_latency_assumed tick_size_change c 2,524 not meas. 4ms 9ms 154ms 205ms 0 transport_latency_assumed tick_size_change e 2,524 2,524 40ms 81ms 123ms 201ms 0 transport_latency_assumed tick_size_change h 2,524 not meas. 18ms 22ms 82ms 225ms 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/09/2026-09-04T09.parquet sha256sum 2026-09-04T09.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.