Hour audit: 2026-09-02T09
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-02T09 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-02T09:00:00.027930027+00:00 · last event 2026-09-02T09:59:59.999872699+00:00
VOLUME 95,653,585 rows · 977,724,683 bytes (932.43 MiB) · 7 products, all holding rows
WITNESSES ceh — 3 machines contributed rows
captured h: 95,278,055 · c: 95,274,415 · e: 95,051,892 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 464,153 (0.49%) · c: 138,608 (0.14%) · e: 95,050,824 (99.37%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 95,653,585 rows exactly, so those pairs supplied none
4 expected (bceh), 1 contributed nothing: b
INTEGRITY sha256 9956086a7959c0d3c625022ba2004e50373562d0f021d9274528615c5f06975b
the corpus checksum ledger names this file with the same digest
joined 95,654,661 to merged 95,653,585, minus 1,076 (minus 0.0011%)
boundary drops 1,076 · 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-02T10:49:27Z 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,466,486 96,112,014 0-32 11bc1723d49f036a7848dfc15a61be38a76d2be1e045c6ec5fcf5e8dbc3a5026 book 714,826 59,694,304 33-35 94d7e38bba3445219d1229d8eba78b34fbb950416e1bb1fb0bf9f3eb747edf27 last_trade_price 65,389 3,612,114 36-36 8f80af14ece4b02e457c1906fe07f3671d11f128d86c93ac417daa6b7efc3269 market_resolved 964 157,177 37-37 90c247d3ac99c399c37710be4dba3b979f0bd9c8671973c483111c40e5aa549b new_market 280 35,245 38-38 e580fb4dc2ee1464d0a139e6b154d225e91f15bd28e02e8c383a8e00514080b8 price_change 86,402,322 816,904,503 39-368 eb60ef16907e84195b3fa1ba3aac9e093c1e477e394e319e9021cd9ada9717f9 tick_size_change 3,318 120,154 369-369 e7d2fa8e42196aa54007342ee87887aade1201fff42d885dc63df32d4953f800 EVENT MIX count share price_change 86,402,322 90.33% best_bid_ask 8,466,486 8.85% book 714,826 0.75% last_trade_price 65,389 0.07% tick_size_change 3,318 <0.01% market_resolved 964 <0.01% new_market 280 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,466,574 8,466,486 88 81,447 PARTIAL book 714,846 714,826 20 171,468 PARTIAL last_trade_price 65,389 65,389 0 3,579 PARTIAL market_resolved 964 964 0 964 PARTIAL new_market 280 280 0 232 PARTIAL price_change 86,403,290 86,402,322 968 144,617 PARTIAL tick_size_change 3,318 3,318 0 830 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,465,462 377 13ms 17ms 45ms 1.5s 0 transport_latency_assumed best_bid_ask e 8,454,206 8,454,118 43ms 67ms 551ms 21.0s 0 transport_latency_assumed best_bid_ask h 8,464,090 11,991 17ms 23ms 99ms 3.5s 0 transport_latency_assumed book c 348,561 133,067 28.0s 2.9h 24.8d 95.5d 0 book_staleness book e 385,897 385,885 44.8s 4.5h 24.8d 95.5d 0 book_staleness book h 392,159 195,874 42.1s 3.9h 24.8d 95.5d 0 book_staleness last_trade_price c 65,350 6 19ms 43ms 146ms 4.9s 0 transport_latency_assumed last_trade_price e 63,975 63,975 59ms 2.1s 12.0s 21.0s 0 transport_latency_assumed last_trade_price h 65,276 1,408 25ms 258ms 1.5s 5.0s 0 transport_latency_assumed market_resolved c 964 not meas. 13ms 18ms 47ms 239ms 0 transport_latency_assumed market_resolved e 964 964 43ms 191ms 696ms 1.3s 0 transport_latency_assumed market_resolved h 964 not meas. 18ms 68ms 190ms 451ms 0 transport_latency_assumed new_market c 232 6 37ms 297ms 18.6s 1.8min 0 transport_latency_assumed new_market e 232 232 69ms 602ms 1.0min 3.3min 0 transport_latency_assumed new_market h 232 42 44ms 11.2s 17.2s 54.1s 0 transport_latency_assumed price_change c 86,390,528 5,152 13ms 18ms 59ms 1.6s 0 transport_latency_assumed price_change e 86,143,300 86,142,332 43ms 98ms 2.9s 21.0s 0 transport_latency_assumed price_change h 86,352,016 254,838 18ms 27ms 255ms 3.8s 0 transport_latency_assumed tick_size_change c 3,318 not meas. 13ms 19ms 57ms 525ms 0 transport_latency_assumed tick_size_change e 3,318 3,318 44ms 110ms 192ms 397ms 0 transport_latency_assumed tick_size_change h 3,318 not meas. 18ms 32ms 62ms 293ms 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/09/2026-09-02T09.parquet sha256sum 2026-09-02T09.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.