Hour audit: 2026-09-21T08
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 5 machines expected to be capturing this hour, 1 contributed no rows: g. The hour is still whole on minutes; it simply rests on 4 machines rather than 5.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-21T08 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-21T08:00:00.000009325+00:00 · last event 2026-09-21T08:59:59.999954674+00:00
VOLUME 115,265,291 rows · 1,178,199,713 bytes (1.10 GiB) · 7 products, all holding rows
WITNESSES cefh — 4 machines contributed rows
captured c: 115,042,706 · h: 114,926,368 · e: 114,518,190 · f: 114,489,400 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 108,915,338 (94.49%) · h: 5,715,632 (4.96%) · e: 415,025 (0.36%) · f: 219,296 (0.19%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 115,265,291 rows exactly, so those pairs supplied none
5 expected (cefgh), 1 contributed nothing: g
INTEGRITY sha256 634987a961ab72d6ea5f938210fca6b9272c3b876332f4951cdc91a380ee0bdf
the corpus checksum ledger names this file with the same digest
joined 115,266,573 to merged 115,265,291, minus 1,282 (minus 0.0011%)
boundary drops 1,282 · 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-21T11:04:03Z as cefh
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 10,206,444 115,169,774 0-38 a7019abf34acff5fe767f4353ae49117ca958b96614060784f1fdddb871a718a book 267,207 26,853,370 39-40 faf1356c15c470ebc58eb4fb46fabc17ffd33b4344272313b3a70a36b8a74dd1 last_trade_price 71,114 3,931,915 41-41 efebd18cebd371d70cf59d41c763efa168a76f1218ad986956d5d627ae9164c6 market_resolved 950 154,025 42-42 53312d608c1b9f90d760a212e3d92757603433e4c6ab4e2e9eb60074154e9b11 new_market 1,708 171,765 43-43 42e203a71826243e41e1fd3bc345ffd2e88e111b8e44c03b71cc39116119c557 price_change 104,714,796 1,030,496,145 44-443 f35a7375454308238edaf2657554da4a193c1cbb56079d2926aaedf4d7cb735d tick_size_change 3,072 111,284 444-444 322c797a2337e09e547e81e387b2b06f998939a8661ffd5d09804bf67974ec49 EVENT MIX count share price_change 104,714,796 90.85% best_bid_ask 10,206,444 8.85% book 267,207 0.23% last_trade_price 71,114 0.06% tick_size_change 3,072 <0.01% new_market 1,708 <0.01% market_resolved 950 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,206,542 10,206,444 98 66,003 PARTIAL book 267,227 267,207 20 52,664 PARTIAL last_trade_price 71,114 71,114 0 3,334 PARTIAL market_resolved 950 950 0 938 PARTIAL new_market 1,708 1,708 0 1,109 PARTIAL price_change 104,715,960 104,714,796 1,164 116,226 PARTIAL tick_size_change 3,072 3,072 0 768 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,205,617 9,700,776 5ms 13ms 103ms 4.2s 0 transport_latency_assumed best_bid_ask e 10,196,655 26,188 40ms 53ms 300ms 23.0s 0 transport_latency_assumed best_bid_ask f 10,194,827 11,269 47ms 63ms 311ms 32.8s 0 transport_latency_assumed best_bid_ask h 10,205,266 468,211 18ms 29ms 147ms 54.1s 0 transport_latency_assumed book c 154,575 144,029 7ms 114ms 2.6d 95.9d 0 book_staleness book e 194,167 52,950 68ms 21.6min 23.6d 114.4d 0 book_staleness book f 189,602 47,176 76ms 20.7min 21.7d 114.4d 0 book_staleness book h 159,848 23,052 23ms 2.7s 8.0d 114.4d 0 book_staleness last_trade_price c 70,957 66,609 6ms 23ms 208ms 2.5s 0 transport_latency_assumed last_trade_price e 68,377 211 43ms 792ms 10.4s 21.1s 0 transport_latency_assumed last_trade_price f 68,002 181 51ms 897ms 11.5s 33.1s 0 transport_latency_assumed last_trade_price h 70,933 4,113 20ms 61ms 502ms 8.5s 0 transport_latency_assumed market_resolved c 938 883 5ms 16.0s 56.0s 1.0min 0 transport_latency_assumed market_resolved e 938 27 41ms 16.2s 56.1s 1.0min 0 transport_latency_assumed market_resolved f 938 not meas. 49ms 16.3s 56.3s 1.0min 0 transport_latency_assumed market_resolved h 938 40 19ms 16.0s 55.6s 57.9s 0 transport_latency_assumed new_market c 1,109 682 118ms 31.7s 1.2min 1.2min 0 transport_latency_assumed new_market e 1,109 199 255ms 29.3s 55.9s 1.4min 0 transport_latency_assumed new_market f 1,109 318 237ms 37.6s 1.2min 1.3min 0 transport_latency_assumed new_market h 1,109 509 189ms 37.7s 1.1min 1.3min 0 transport_latency_assumed price_change c 104,606,438 98,999,418 5ms 16ms 123ms 5.6s 0 transport_latency_assumed price_change e 104,053,872 335,442 40ms 70ms 2.4s 23.0s 0 transport_latency_assumed price_change f 104,031,850 160,344 48ms 80ms 2.1s 33.8s 0 transport_latency_assumed price_change h 104,485,202 5,219,592 19ms 34ms 223ms 54.2s 0 transport_latency_assumed tick_size_change c 3,072 2,941 5ms 12ms 191ms 442ms 0 transport_latency_assumed tick_size_change e 3,072 8 40ms 45ms 418ms 2.1s 0 transport_latency_assumed tick_size_change f 3,072 8 47ms 56ms 379ms 2.5s 0 transport_latency_assumed tick_size_change h 3,072 115 18ms 26ms 190ms 4.9s 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-21/08/2026-09-21T08.parquet sha256sum 2026-09-21T08.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.