Hour audit: 2026-09-01T07
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-01T07 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-01T07:00:00.026944746+00:00 · last event 2026-09-01T07:59:59.999973948+00:00
VOLUME 83,523,925 rows · 810,619,711 bytes (773.07 MiB) · 7 products, all holding rows
WITNESSES ceh — 3 machines contributed rows
captured c: 83,485,957 · h: 83,429,807 · e: 82,999,911 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 44,594 (0.05%) · h: 480,064 (0.57%) · e: 82,999,267 (99.37%) (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 83,523,925 rows exactly, so those pairs supplied none
4 expected (bceh), 1 contributed nothing: b
INTEGRITY sha256 2e5d335e411fbf3aafd0b8d63494f9406dc20a7bae731b7bf20e68ca78b7ded4
the corpus checksum ledger names this file with the same digest
joined 83,524,571 to merged 83,523,925, minus 646 (minus 0.0008%)
boundary drops 646 · 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-01T13:43:31Z 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 7,738,014 87,475,142 0-29 a593e60d27f62e044ef205bb364a7342ba37231e4371e4bcd83a4a509e8e85dd book 144,550 13,749,108 30-30 78354d969f10ea24824805058a95997b9376b01a70ecbe6712f2ead9102de1c0 last_trade_price 58,089 3,234,356 31-31 36223b0a3463779d3410eb49a31ad3600c30fce3e3256dcbd89722555cddc5a7 market_resolved 515 84,934 32-32 1b598ea17253eb1693a0d01f7dd144fab598e91399b1c3648a49f6d418ee44fb new_market 953 109,785 33-33 00c3cdf3089b70f829a279725383e5e2dfee3463562ffa3674a90007b8ffc3d1 price_change 75,579,788 704,938,089 34-322 3aa670e0bdd87053b1918d67af58633c782000c2109dffbefe94d2179f5acca2 tick_size_change 2,016 74,639 323-323 17658b8830fa4b74a07a54701ed7cde30d1cdac91cebcc4ea14499b8d4352b3a EVENT MIX count share price_change 75,579,788 90.49% best_bid_ask 7,738,014 9.26% book 144,550 0.17% last_trade_price 58,089 0.07% tick_size_change 2,016 <0.01% new_market 953 <0.01% market_resolved 515 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 7,738,074 7,738,014 60 83,296 PARTIAL book 144,552 144,550 2 13,739 PARTIAL last_trade_price 58,089 58,089 0 3,183 PARTIAL market_resolved 515 515 0 511 PARTIAL new_market 953 953 0 728 PARTIAL price_change 75,580,372 75,579,788 584 135,276 PARTIAL tick_size_change 2,016 2,016 0 504 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 7,737,802 2,162 4ms 7ms 91ms 1.8s 0 transport_latency_assumed best_bid_ask e 7,727,460 7,727,400 41ms 102ms 1.2s 22.5s 0 transport_latency_assumed best_bid_ask h 7,733,750 8,452 18ms 25ms 373ms 25.6s 0 transport_latency_assumed book c 125,446 6,343 7ms 69ms 38.2min 75.9d 0 book_staleness book e 131,705 131,705 146ms 23.2s 1.6d 34.6d 0 book_staleness book h 121,131 6,502 40ms 1.3s 2.1min 75.9d 0 book_staleness last_trade_price c 58,064 443 9ms 46ms 258ms 4.6s 0 transport_latency_assumed last_trade_price e 55,772 55,772 87ms 6.1s 18.4s 22.6s 0 transport_latency_assumed last_trade_price h 57,357 1,874 35ms 1.1s 4.0s 9.4s 0 transport_latency_assumed market_resolved c 511 not meas. 4ms 11ms 55.4s 59.8s 0 transport_latency_assumed market_resolved e 508 508 42ms 540ms 56.2s 1.0min 0 transport_latency_assumed market_resolved h 511 7 19ms 106ms 1.0min 1.0min 0 transport_latency_assumed new_market c 728 70 50ms 10.5s 27.1s 27.5s 0 transport_latency_assumed new_market e 728 728 261ms 16.4s 28.2s 1.3min 0 transport_latency_assumed new_market h 728 155 171ms 12.9s 19.9s 2.1min 0 transport_latency_assumed price_change c 75,561,390 35,576 4ms 8ms 164ms 3.2s 0 transport_latency_assumed price_change e 75,081,722 75,081,138 42ms 160ms 6.1s 22.6s 0 transport_latency_assumed price_change h 75,514,314 463,074 18ms 35ms 921ms 26.4s 0 transport_latency_assumed tick_size_change c 2,016 not meas. 4ms 8ms 71ms 427ms 0 transport_latency_assumed tick_size_change e 2,016 2,016 42ms 124ms 4.9s 8.0s 0 transport_latency_assumed tick_size_change h 2,016 not meas. 18ms 36ms 214ms 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/07/2026-09-01T07.parquet sha256sum 2026-09-01T07.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.