Hour audit: 2026-09-01T09
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-09-01T09 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-01T09:00:00.037184371+00:00 · last event 2026-09-01T09:59:59.999995559+00:00
VOLUME 90,146,633 rows · 886,875,825 bytes (845.79 MiB) · 7 products, all holding rows
WITNESSES ceh — 3 machines contributed rows
captured c: 90,120,999 · h: 90,041,097 · e: 89,740,650 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 38,642 (0.04%) · h: 369,739 (0.41%) · e: 89,738,252 (99.55%) (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 90,146,633 rows exactly, so those pairs supplied none
4 expected (bceh), 1 contributed nothing: b
INTEGRITY sha256 ee800bcf02295e03b0d9820785688c57e4494f16fb9468ca536d980936385487
the corpus checksum ledger names this file with the same digest
joined 90,149,113 to merged 90,146,633, minus 2,480 (minus 0.0028%)
boundary drops 2,480 · 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-01T14:12:51Z 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 an incident recorded by the venue intersects this hour: Venue maintenance on a market this archive does not record, 2026-09-01T07:30Z to 2026-09-01T09:30ZThe 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 6,913,166 79,303,521 0-26 eb19af8dac019ed6052c50a181f2ad2b261db3ff37cb8765d45504efa5460fe1 book 175,005 17,107,189 27-27 db764d0c7e2fb229e19105f1e59d7251993e133cb88c0558fba8b7ed39267e89 last_trade_price 65,957 3,661,720 28-28 9fb5139d795b83e5528afb4cfac217b061e8abf9ee27e6c7efc80f91d0c10352 market_resolved 924 145,611 29-29 0ddbe5ebe7a3f0ab7cb7f86c3a163da761497be123e105c4ff761c906376fdb8 new_market 817 93,195 30-30 860b6ed0c315165872510ee04d7a7b3073171e56635e455a6ae6c1f32ce4142c price_change 82,988,268 785,445,689 31-347 1baf516537bb37beec88e12c39ea34b916899d89d8117f1605513200d4fb03b6 tick_size_change 2,496 91,275 348-348 3b6129b9ad99528efe4027c883423e87ba5cec5f77510f8713b49b0d55581ea8 EVENT MIX count share price_change 82,988,268 92.06% best_bid_ask 6,913,166 7.67% book 175,005 0.19% last_trade_price 65,957 0.07% tick_size_change 2,496 <0.01% market_resolved 924 <0.01% new_market 817 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 6,913,289 6,913,166 123 76,106 PARTIAL book 175,013 175,005 8 19,887 PARTIAL last_trade_price 65,958 65,957 1 3,366 PARTIAL market_resolved 924 924 0 884 PARTIAL new_market 817 817 0 628 PARTIAL price_change 82,990,616 82,988,268 2,348 135,162 PARTIAL tick_size_change 2,496 2,496 0 624 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 6,912,650 1,230 0ms 3ms 64ms 1.7s 0 transport_latency_assumed best_bid_ask e 6,900,870 6,900,757 44ms 83ms 964ms 20.1s 0 transport_latency_assumed best_bid_ask h 6,908,977 11,179 18ms 26ms 257ms 39.7s 0 transport_latency_assumed book c 155,287 19,118 3ms 22.4s 4.1d 94.5d 0 book_staleness book e 147,916 147,912 110ms 14.3s 5.6h 75.9d 0 book_staleness book h 138,139 7,975 26ms 569ms 2.9min 75.9d 0 book_staleness last_trade_price c 65,914 97 5ms 37ms 205ms 4.9s 0 transport_latency_assumed last_trade_price e 63,513 63,512 75ms 4.2s 12.4s 20.1s 0 transport_latency_assumed last_trade_price h 65,375 2,348 27ms 488ms 1.8s 6.3s 0 transport_latency_assumed market_resolved c 884 not meas. 0ms 3ms 104ms 1.0min 0 transport_latency_assumed market_resolved e 883 883 44ms 199ms 1.0min 1.0min 0 transport_latency_assumed market_resolved h 884 41 18ms 48ms 197ms 1.0min 0 transport_latency_assumed new_market c 628 87 73ms 18.0s 27.3s 1.3min 0 transport_latency_assumed new_market e 628 628 242ms 10.5s 27.4s 1.1min 0 transport_latency_assumed new_market h 628 102 133ms 426ms 26.9s 1.6min 0 transport_latency_assumed price_change c 82,983,140 18,110 0ms 4ms 102ms 2.6s 0 transport_latency_assumed price_change e 82,624,348 82,622,068 44ms 118ms 3.7s 20.1s 0 transport_latency_assumed price_change h 82,924,598 348,090 18ms 31ms 432ms 40.0s 0 transport_latency_assumed tick_size_change c 2,496 not meas. 0ms 4ms 43ms 224ms 0 transport_latency_assumed tick_size_change e 2,492 2,492 43ms 88ms 267ms 1.2s 0 transport_latency_assumed tick_size_change h 2,496 4 18ms 28ms 128ms 1.7s 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-01/09/2026-09-01T09.parquet sha256sum 2026-09-01T09.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.