Hour audit: 2026-09-02T06
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, 2 contributed no rows: b, c. The hour is still whole on minutes; it simply rests on 2 machines rather than 4.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-02T06 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-02T06:00:00.022753015+00:00 · last event 2026-09-02T06:59:59.999844107+00:00
VOLUME 93,298,957 rows · 916,777,022 bytes (874.31 MiB) · 7 products, all holding rows
WITNESSES eh — 2 machines contributed rows
captured h: 92,957,008 · e: 92,648,046 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 651,753 (0.70%) · e: 92,647,204 (99.30%) (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 93,298,957 rows exactly, so those pairs supplied none
4 expected (bceh), 2 contributed nothing: b, c
INTEGRITY sha256 78a031a8376044e7519f24d4b344e6c8e59ef97c5caaa3c8c1994a56170d7a60
the corpus checksum ledger names this file with the same digest
joined 93,299,799 to merged 93,298,957, minus 842 (minus 0.0009%)
boundary drops 842 · 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-02T08:03:52Z as eh
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 9,678,791 107,132,835 0-36 ec5312f0f07271d4377cf3ab68fdf0b67a31f38edb497cce85a29e03977fa1ac book 481,378 46,622,585 37-38 e15ab90def6916143e94fe458398e2826a4198d0f878b99b65be7f4f38880dd4 last_trade_price 76,465 4,070,092 39-39 17f3fcd5fb0d93745f077b9ffc5c472cec390adff6592e75218e23e4886a2a68 market_resolved 726 119,919 40-40 0093370b9806f420576983a616c0c2c37336dfdf32df4864af41f18525569117 new_market 1,261 156,052 41-41 edf3da61fc634ec96fac016d66558db78700087586cb530f18831801685ad218 price_change 83,058,060 757,535,385 42-358 b1efe93d504f9d12f2f4c9225434da76798413638ab404442634f88dc1d3d790 tick_size_change 2,276 84,004 359-359 88c9a08122692792767ea43fd0c8df24ddd5f8851891847cfd5e2017fac59215 EVENT MIX count share price_change 83,058,060 89.02% best_bid_ask 9,678,791 10.37% book 481,378 0.52% last_trade_price 76,465 0.08% tick_size_change 2,276 <0.01% new_market 1,261 <0.01% market_resolved 726 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,678,860 9,678,791 69 94,136 PARTIAL book 481,392 481,378 14 150,372 PARTIAL last_trade_price 76,472 76,465 7 3,477 PARTIAL market_resolved 726 726 0 726 PARTIAL new_market 1,261 1,261 0 1,071 PARTIAL price_change 83,058,812 83,058,060 752 147,598 PARTIAL tick_size_change 2,276 2,276 0 569 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask e 9,646,826 9,646,757 42ms 98ms 1.2s 31.6s 0 transport_latency_assumed best_bid_ask h 9,678,087 32,034 18ms 27ms 255ms 9.7s 0 transport_latency_assumed book e 464,417 464,403 41.2s 6.4h 24.7d 95.3d 0 book_staleness book h 168,650 16,975 25ms 1.1s 6.7h 76.9d 0 book_staleness last_trade_price e 72,650 72,643 66ms 4.8s 16.8s 29.8s 0 transport_latency_assumed last_trade_price h 76,346 3,822 26ms 450ms 2.0s 6.0s 0 transport_latency_assumed market_resolved e 726 726 43ms 541ms 1.0min 1.0min 0 transport_latency_assumed market_resolved h 726 not meas. 19ms 154ms 1.0min 1.0min 0 transport_latency_assumed new_market e 1,071 1,071 229ms 12.7s 34.9s 1.1min 0 transport_latency_assumed new_market h 1,071 190 129ms 14.6s 28.2s 1.2min 0 transport_latency_assumed price_change e 82,460,080 82,459,328 43ms 155ms 5.1s 31.6s 0 transport_latency_assumed price_change h 83,029,852 598,732 18ms 35ms 475ms 9.7s 0 transport_latency_assumed tick_size_change e 2,276 2,276 43ms 117ms 629ms 28.8s 0 transport_latency_assumed tick_size_change h 2,276 not meas. 18ms 33ms 142ms 267ms 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-02/06/2026-09-02T06.parquet sha256sum 2026-09-02T06.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.