Hour audit: 2026-09-02T01
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-02T01 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-02T01:00:00.003139691+00:00 · last event 2026-09-02T01:59:59.206344341+00:00
VOLUME 38,438,499 rows · 403,949,470 bytes (385.24 MiB) · 7 products, all holding rows
WITNESSES eh — 2 machines contributed rows
captured h: 38,422,954 · e: 36,991,282 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 1,448,109 (3.77%) · e: 36,990,390 (96.23%) (rows of the merged file that came from it; these partition it)
4 expected (bceh), 2 contributed nothing: b, c
INTEGRITY sha256 10798e2cdefe2d67f1cd274cadc4abd773e96ebd34a0457abbaea4f07cacbd73
the corpus checksum ledger names this file with the same digest
joined 38,439,443 to merged 38,438,499, minus 944 (minus 0.0025%)
boundary drops 944 · 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-02T05:31:11Z 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 an incident recorded by the venue intersects this hour: Venue restart, then a paused database migration, 2026-09-01T22:30Z to 2026-09-02T04:58ZThe 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 3,734,124 45,475,825 0-14 3ff0490cf21b44e765f68f6d79f51de70ab53428be593493a5e90cb4df4ad681 book 283,106 26,237,627 15-16 42be1ff698471c9e1db08613a49da9c1f75cf0a1eef97be22ed7a90b0dc2351d last_trade_price 33,466 1,879,177 17-17 a53fcef165341045610f82bb9adf22648f92cfa552bb7101bb0efc1351dabd74 market_resolved 673 110,461 18-18 8873b92fdbed9575a0385453da7b2847689df0638ca7c5a20c04c45be7e7b6c0 new_market 748 98,238 19-19 4ad5d855c9af3a24bdfc5e5c7c7320cf178b20bd53b683bc5cbdede4b97f9857 price_change 34,384,882 329,643,416 20-151 4ab33054548b6b4c16ef29e0470c38230c00ee342f18f62a028f4970abe77de9 tick_size_change 1,500 54,774 152-152 0678eb80c730b33f5b261cdca59623491797e86bbab83c294ba4c989af3796af EVENT MIX count share price_change 34,384,882 89.45% best_bid_ask 3,734,124 9.71% book 283,106 0.74% last_trade_price 33,466 0.09% tick_size_change 1,500 <0.01% new_market 748 <0.01% market_resolved 673 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 3,734,172 3,734,124 48 70,051 PARTIAL book 283,164 283,106 58 84,341 PARTIAL last_trade_price 33,466 33,466 0 1,984 PARTIAL market_resolved 673 673 0 667 PARTIAL new_market 748 748 0 641 PARTIAL price_change 34,385,720 34,384,882 838 126,592 PARTIAL tick_size_change 1,500 1,500 0 375 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask e 3,627,876 3,627,828 42ms 87ms 1.5s 22.2s 0 transport_latency_assumed best_bid_ask h 3,733,640 106,296 18ms 34ms 255ms 5.7s 0 transport_latency_assumed book e 74,498 74,492 125ms 6.5min 2.3h 76.6d 0 book_staleness book h 276,238 208,614 15.6min 2.2h 29.2d 95.2d 0 book_staleness last_trade_price e 31,312 31,312 74ms 5.3s 16.6s 22.2s 0 transport_latency_assumed last_trade_price h 33,348 2,154 35ms 650ms 2.2s 4.9s 0 transport_latency_assumed market_resolved e 647 647 42ms 459ms 1.0min 2.4min 0 transport_latency_assumed market_resolved h 667 26 19ms 139ms 57.9s 1.0min 0 transport_latency_assumed new_market e 641 641 183ms 9.6s 39.1s 1.2min 0 transport_latency_assumed new_market h 641 107 94ms 369ms 50.1s 1.2min 0 transport_latency_assumed price_change e 33,254,860 33,254,022 42ms 184ms 6.7s 22.2s 0 transport_latency_assumed price_change h 34,376,920 1,130,860 18ms 48ms 646ms 7.3s 0 transport_latency_assumed tick_size_change e 1,448 1,448 42ms 57ms 218ms 598ms 0 transport_latency_assumed tick_size_change h 1,500 52 18ms 25ms 88ms 136ms 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/01/2026-09-02T01.parquet sha256sum 2026-09-02T01.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.