Hour audit: 2026-09-02T04
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-02T04 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-02T04:00:00.046041653+00:00 · last event 2026-09-02T04:59:59.999980672+00:00
VOLUME 6,482,726 rows · 106,680,562 bytes (101.74 MiB) · 7 products, all holding rows
WITNESSES eh — 2 machines contributed rows
captured h: 6,413,145 · e: 6,293,191 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 189,539 (2.92%) · e: 6,293,187 (97.08%) (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 6,482,726 rows exactly, so those pairs supplied none
4 expected (bceh), 2 contributed nothing: b, c
INTEGRITY sha256 e3d80fe7da86444addec4c1c09f18a31966e9b58e09152b0c2337981cf1caf8d
the corpus checksum ledger names this file with the same digest
joined 6,482,766 to merged 6,482,726, minus 40 (minus 0.0006%)
boundary drops 40 · 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-02T06:14:31Z 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 877,708 18,732,764 0-3 85bcea4f423b9b8395cc6de5325a1889a19d37dd2a8699f4673487c00c9f63b5 book 181,935 17,401,723 4-4 837f0f8abc46db878ab992eb3654b128032d8b665a38aa8f860b2247ba1bee00 last_trade_price 6,452 457,228 5-5 f05001de0ed7ac817c3b33415d06fd4c9fd246988984428a26aab666de2f2430 market_resolved 754 122,712 6-6 82e67f06ba3ef732ef122f7a56f09a6325e1b86e6926f807384a27db48603324 new_market 1,814 220,431 7-7 3a2a842aef39190691fd381761298925cd5935104fdb24643349fd4496b56bc0 price_change 5,413,183 69,624,826 8-28 783eaaa0aafb00b2c1794a916c3ab41b178a794dc94764f648fce4e33d8ac01f tick_size_change 880 31,187 29-29 5b22d0697007e5e22a6fb83a188a45abe3bab93595e0a99ee678d3d14c117dc6 EVENT MIX count share price_change 5,413,183 83.50% best_bid_ask 877,708 13.54% book 181,935 2.81% last_trade_price 6,452 0.10% new_market 1,814 0.03% tick_size_change 880 0.01% market_resolved 754 0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 877,708 877,708 0 77,461 PARTIAL book 181,975 181,935 40 76,427 PARTIAL last_trade_price 6,452 6,452 0 1,366 PARTIAL market_resolved 754 754 0 754 PARTIAL new_market 1,814 1,814 0 1,534 PARTIAL price_change 5,413,183 5,413,183 0 128,265 PARTIAL tick_size_change 880 880 0 220 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask e 875,498 875,498 47ms 861ms 8.3s 21.4s 0 transport_latency_assumed best_bid_ask h 877,610 2,210 17ms 32ms 834ms 14.0s 0 transport_latency_assumed book e 95,512 95,508 2.4h 5.2h 32.6d 95.3d 0 book_staleness book h 113,795 86,427 2.6h 5.0h 30.7d 95.2d 0 book_staleness last_trade_price e 6,212 6,212 231ms 5.9s 15.2s 21.4s 0 transport_latency_assumed last_trade_price h 6,449 240 23ms 80ms 2.0s 9.1s 0 transport_latency_assumed market_resolved e 754 754 46ms 117ms 2.5s 59.2s 0 transport_latency_assumed market_resolved h 754 not meas. 18ms 22ms 347ms 59.1s 0 transport_latency_assumed new_market e 1,534 1,534 298ms 18.4s 33.1s 53.6s 0 transport_latency_assumed new_market h 1,534 280 191ms 17.2s 28.3s 1.7min 0 transport_latency_assumed price_change e 5,312,801 5,312,801 48ms 1.0s 10.8s 30.5s 0 transport_latency_assumed price_change h 5,412,123 100,382 17ms 63ms 813ms 14.3s 0 transport_latency_assumed tick_size_change e 880 880 43ms 95ms 178ms 220ms 0 transport_latency_assumed tick_size_change h 880 not meas. 17ms 18ms 26ms 52ms 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/04/2026-09-02T04.parquet sha256sum 2026-09-02T04.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.