Hour audit: 2026-09-08T06
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.
No findings
Every check that could be evaluated for this hour passed. That is not the same as the hour being perfect: it means the records this archive keeps about it agree with each other and with the corpus ledger.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-08T06 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-08T06:00:00.000109363+00:00 · last event 2026-09-08T06:59:59.999868417+00:00
VOLUME 85,041,027 rows · 840,999,346 bytes (802.04 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 85,011,172 · h: 84,998,401 · e: 84,961,321 · g: 84,951,052 · f: 84,950,077 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 82,416,215 (96.91%) · h: 2,330,132 (2.74%) · e: 206,994 (0.24%) · g: 18,925 (0.02%) · f: 68,761 (0.08%) (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 85,041,027 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 e990cfa81e269a3dc8234bdfc0f3dc6be22e0576a21f7965997cd97094b42d7f
the corpus checksum ledger names this file with the same digest
joined 85,044,497 to merged 85,041,027, minus 3,470 (minus 0.0041%)
boundary drops 3,470 · 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-08T07:53:16Z as cefgh
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 8/8 pass
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
PASS every expected machine contributed
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 7,591,540 84,428,554 0-28 f6cada7cdf0a1bff5fcaf9c9469905cc467f23e72b44e9ad9934bbf2cf691141 book 164,556 16,085,528 29-29 6d0a2141680bc8fedc5cd60078fdbd5253d3bf6107b428471f90c6e7a3724185 last_trade_price 69,875 3,811,776 30-30 8ab788e11507e481a47ee0bfef5377186e2b1ad78fd62f040d0b542606fdb93c market_resolved 606 100,025 31-31 9c5ad5789857868b650dfbf5776950b2b46f7ed156af5b948b35adf6d79bc0b5 new_market 738 75,084 32-32 210ac9e833e18cb1d99f6f67929e1e73a6543b912a21d35a1f35994c50079b1d price_change 77,211,884 735,459,789 33-327 4147ff4779cde5efeed35fb3555e320e4c3d8fb94beb7d8e282afc409d4f138b tick_size_change 1,828 67,548 328-328 2fdf967abdc578fb45afbc4b3b709d97c68e42108283fb8d36da9e14d0f5b3b8 EVENT MIX count share price_change 77,211,884 90.79% best_bid_ask 7,591,540 8.93% book 164,556 0.19% last_trade_price 69,875 0.08% tick_size_change 1,828 <0.01% new_market 738 <0.01% market_resolved 606 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 7,591,693 7,591,540 153 113 FULL book 164,558 164,556 2 8,790 FULL last_trade_price 69,876 69,875 1 0 FULL market_resolved 606 606 0 0 FULL new_market 738 738 0 0 FULL price_change 77,215,198 77,211,884 3,314 246 FULL tick_size_change 1,828 1,828 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 7,591,370 7,380,630 5ms 9ms 63ms 3.3s 0 transport_latency_assumed best_bid_ask e 7,590,103 13,580 39ms 43ms 126ms 2.7s 0 transport_latency_assumed best_bid_ask f 7,590,006 3,920 47ms 53ms 144ms 3.3s 0 transport_latency_assumed best_bid_ask g 7,589,409 434 79ms 100ms 262ms 13.2s 0 transport_latency_assumed best_bid_ask h 7,590,738 192,976 17ms 22ms 87ms 17.2s 0 transport_latency_assumed book c 147,226 140,595 7ms 19ms 10.7min 82.8d 0 book_staleness book e 146,914 3,341 41ms 106ms 18.8min 82.7d 0 book_staleness book f 146,995 2,968 49ms 113ms 11.2min 82.8d 0 book_staleness book g 155,169 10,929 85ms 345ms 16.7h 101.3d 0 book_staleness book h 145,571 6,723 20ms 45ms 1.3s 30.9d 0 book_staleness last_trade_price c 69,823 67,170 10ms 37ms 164ms 5.0s 0 transport_latency_assumed last_trade_price e 69,731 222 44ms 91ms 600ms 5.0s 0 transport_latency_assumed last_trade_price f 69,723 71 53ms 100ms 474ms 5.0s 0 transport_latency_assumed last_trade_price g 69,711 9 91ms 174ms 1.5s 13.2s 0 transport_latency_assumed last_trade_price h 69,745 2,403 22ms 55ms 222ms 5.0s 0 transport_latency_assumed market_resolved c 597 588 5ms 9ms 64ms 257ms 0 transport_latency_assumed market_resolved e 597 9 41ms 191ms 1.0min 1.0min 0 transport_latency_assumed market_resolved f 597 not meas. 48ms 206ms 1.0min 1.0min 0 transport_latency_assumed market_resolved g 597 not meas. 85ms 343ms 808ms 1.4s 0 transport_latency_assumed market_resolved h 597 9 18ms 82ms 162ms 659ms 0 transport_latency_assumed new_market c 484 298 67ms 14.7s 52.0s 1.1min 0 transport_latency_assumed new_market e 484 126 118ms 19.7s 40.2s 1.0min 0 transport_latency_assumed new_market f 484 56 143ms 22.1s 41.8s 1.2min 0 transport_latency_assumed new_market g 484 31 214ms 20.4s 41.2s 54.3s 0 transport_latency_assumed new_market h 484 227 85ms 25.2s 45.8s 1.1min 0 transport_latency_assumed price_change c 77,199,844 74,825,138 5ms 10ms 86ms 5.0s 0 transport_latency_assumed price_change e 77,151,664 189,716 39ms 46ms 181ms 2.7s 0 transport_latency_assumed price_change f 77,140,444 61,742 47ms 56ms 206ms 3.5s 0 transport_latency_assumed price_change g 77,133,854 7,522 80ms 108ms 351ms 13.2s 0 transport_latency_assumed price_change h 77,189,438 2,127,766 17ms 24ms 121ms 17.2s 0 transport_latency_assumed tick_size_change c 1,828 1,796 5ms 8ms 27ms 66ms 0 transport_latency_assumed tick_size_change e 1,828 not meas. 39ms 43ms 112ms 415ms 0 transport_latency_assumed tick_size_change f 1,828 4 47ms 51ms 111ms 129ms 0 transport_latency_assumed tick_size_change g 1,828 not meas. 79ms 96ms 186ms 5.3s 0 transport_latency_assumed tick_size_change h 1,828 28 17ms 19ms 43ms 162ms 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-08/06/2026-09-08T06.parquet sha256sum 2026-09-08T06.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.