Hour audit: 2026-09-02T05
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-02T05 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-02T05:00:00.002368202+00:00 · last event 2026-09-02T05:59:59.999973536+00:00
VOLUME 84,016,893 rows · 801,857,609 bytes (764.71 MiB) · 7 products, all holding rows
WITNESSES eh — 2 machines contributed rows
captured h: 83,983,805 · e: 83,531,895 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 485,771 (0.58%) · e: 83,531,122 (99.42%) (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 84,016,893 rows exactly, so those pairs supplied none
4 expected (bceh), 2 contributed nothing: b, c
INTEGRITY sha256 72a06032c573637c1e63b9491eefd0cfccc6ea6e468752d3f7a380009da407b4
the corpus checksum ledger names this file with the same digest
joined 84,017,678 to merged 84,016,893, minus 785 (minus 0.0009%)
boundary drops 785 · 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-02T07:22:27Z 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 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 11,104,250 119,224,452 0-42 0d3771acc879eb76cc73669d2dc78695fa82d965df8307812d4acc41c9ca9024 book 209,883 14,907,125 43-43 c7f35fcdf0f3ed386a726b70bd7cab90e181c1834b8ba5072ba4a9e951bec59c last_trade_price 86,451 4,548,704 44-44 4e78ea4c84570c809515cb6908441964cd8cf3d21554edc2d07d9e5ae3d767d7 market_resolved 662 108,277 45-45 ac28e345e86eeb18126cb99de299f1750101924fde3a6f13b092877636643e0e new_market 1,428 163,123 46-46 5503392d73d9577f3b896ca6ac035b0a311e6a5b3485291a137e72fedca96f10 price_change 72,611,379 661,846,715 47-323 e4d6441516b80f10dea62558fcee5a714963577d7809218c626d39b1348d986c tick_size_change 2,840 104,186 324-324 53ffb24d85dbdba55aa3da73099dafc5cdb78ebcbc4b059aa53b99d43cf8e220 EVENT MIX count share price_change 72,611,379 86.42% best_bid_ask 11,104,250 13.22% book 209,883 0.25% last_trade_price 86,451 0.10% tick_size_change 2,840 <0.01% new_market 1,428 <0.01% market_resolved 662 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,104,306 11,104,250 56 92,104 PARTIAL book 209,958 209,883 75 18,488 PARTIAL last_trade_price 86,451 86,451 0 4,053 PARTIAL market_resolved 662 662 0 662 PARTIAL new_market 1,428 1,428 0 1,081 PARTIAL price_change 72,612,033 72,611,379 654 137,581 PARTIAL tick_size_change 2,840 2,840 0 710 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask e 11,088,106 11,088,050 41ms 75ms 1.1s 31.7s 0 transport_latency_assumed best_bid_ask h 11,104,076 16,200 18ms 24ms 211ms 36.5s 0 transport_latency_assumed book e 197,597 197,534 49ms 42.9s 8.9h 76.8d 0 book_staleness book h 184,954 12,349 21ms 477ms 12.6min 95.3d 0 book_staleness last_trade_price e 83,686 83,686 56ms 3.5s 13.9s 33.0s 0 transport_latency_assumed last_trade_price h 86,427 2,765 24ms 240ms 1.7s 7.5s 0 transport_latency_assumed market_resolved e 662 662 41ms 367ms 743ms 6.4s 0 transport_latency_assumed market_resolved h 662 not meas. 19ms 121ms 294ms 1.3s 0 transport_latency_assumed new_market e 1,081 1,081 247ms 45.3s 1.2min 1.2min 0 transport_latency_assumed new_market h 1,081 347 152ms 29.9s 1.3min 1.4min 0 transport_latency_assumed price_change e 72,157,923 72,157,269 41ms 127ms 5.5s 33.1s 0 transport_latency_assumed price_change h 72,603,765 454,110 18ms 29ms 390ms 45.9s 0 transport_latency_assumed tick_size_change e 2,840 2,840 41ms 111ms 420ms 1.2s 0 transport_latency_assumed tick_size_change h 2,840 not meas. 18ms 24ms 383ms 790ms 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/05/2026-09-02T05.parquet sha256sum 2026-09-02T05.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.