Hour audit: 2026-09-02T07
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-02T07 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-02T07:00:00.021327836+00:00 · last event 2026-09-02T07:59:59.999980521+00:00
VOLUME 90,364,847 rows · 899,709,488 bytes (858.03 MiB) · 7 products, all holding rows
WITNESSES ceh — 3 machines contributed rows
captured h: 89,874,834 · e: 89,701,445 · c: 25,363,635 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 258,000 (0.29%) · e: 89,700,902 (99.27%) · c: 405,945 (0.45%) (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 90,364,847 rows exactly, so those pairs supplied none
4 expected (bceh), 1 contributed nothing: b
INTEGRITY sha256 470b6e5c80dc8f70e6c1dac10d87a491fdfcf8fe6d9f2429b29d623dbdb15035
the corpus checksum ledger names this file with the same digest
joined 90,365,418 to merged 90,364,847, minus 571 (minus 0.0006%)
boundary drops 571 · 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-02T09:24:12Z 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,722,130 97,950,359 0-33 a302ebbac52b77d14fd2596c1b44995fa342d4feea21a5de2350ca359222431c book 505,164 50,565,031 34-35 5dc2da62159ba0d6f94b3843602d3220da03e1dd696a45956d11f8bfede3d69e last_trade_price 54,834 3,117,526 36-36 8ce47f3b57d10bd4d9c5b90b26add06284dc8899e89f1a27c8931147ab9bffdc market_resolved 5,960 842,171 37-37 dd3dff60fe5b23d4445edff2d41e54b5d09f1156e631d024be9675b99ab341d1 new_market 9,475 1,231,395 38-38 3347841a455339968e362dc8c982be7cf5010d610aec294f4612e3aae73cb6f4 price_change 81,065,088 744,890,139 39-348 7243264d354462697cbe92d5c79f1fd26d796583b3c13c48b7d670e14a210d0c tick_size_change 2,196 81,624 349-349 02937e7ff64713ab64714d94b97cacbd8b3bd4fc677565c9b3f38330ef9e2f09 EVENT MIX count share price_change 81,065,088 89.71% best_bid_ask 8,722,130 9.65% book 505,164 0.56% last_trade_price 54,834 0.06% new_market 9,475 0.01% market_resolved 5,960 <0.01% tick_size_change 2,196 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,722,174 8,722,130 44 84,348 PARTIAL book 505,186 505,164 22 185,810 PARTIAL last_trade_price 54,835 54,834 1 3,187 PARTIAL market_resolved 5,960 5,960 0 5,492 PARTIAL new_market 9,481 9,475 6 8,676 PARTIAL price_change 81,065,586 81,065,088 498 144,629 PARTIAL tick_size_change 2,196 2,196 0 549 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 2,366,276 3,306 2ms 5ms 50ms 1.7s 0 transport_latency_assumed best_bid_ask e 8,707,537 8,707,493 40ms 94ms 1.2s 25.4s 0 transport_latency_assumed best_bid_ask h 8,715,592 11,331 18ms 26ms 462ms 44.8s 0 transport_latency_assumed book c 410,127 362,477 3.3min 8.2h 30.8d 95.4d 0 book_staleness book e 133,702 133,702 157ms 3.1min 1.2d 93.8d 0 book_staleness book h 117,873 8,985 31ms 1.6s 31.8min 76.9d 0 book_staleness last_trade_price c 18,103 379 8ms 35ms 161ms 4.4s 0 transport_latency_assumed last_trade_price e 52,661 52,660 74ms 4.8s 16.1s 25.0s 0 transport_latency_assumed last_trade_price h 54,230 1,795 30ms 937ms 6.5s 10.4s 0 transport_latency_assumed market_resolved c 5,449 5,340 4.0h 7.2h 8.0h 8.1h 0 transport_latency_assumed market_resolved e 620 620 40ms 699ms 1.0min 1.0min 0 transport_latency_assumed market_resolved h 620 not meas. 20ms 198ms 1.0min 1.0min 0 transport_latency_assumed new_market c 8,676 8,391 3.6h 8.1h 8.1h 8.6h 0 transport_latency_assumed new_market e 971 971 175ms 12.9s 26.2s 1.2min 0 transport_latency_assumed new_market h 971 113 161ms 15.2s 28.4s 1.5min 0 transport_latency_assumed price_change c 22,554,236 26,052 2ms 5ms 66ms 2.7s 0 transport_latency_assumed price_change e 80,803,758 80,803,260 40ms 126ms 3.9s 25.4s 0 transport_latency_assumed price_change h 80,983,352 235,776 18ms 31ms 719ms 44.9s 0 transport_latency_assumed tick_size_change c 768 not meas. 2ms 4ms 9ms 222ms 0 transport_latency_assumed tick_size_change e 2,196 2,196 40ms 106ms 229ms 6.6s 0 transport_latency_assumed tick_size_change h 2,196 not meas. 18ms 28ms 292ms 2.1s 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/07/2026-09-02T07.parquet sha256sum 2026-09-02T07.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.