Hour audit: 2026-09-02T14
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-02T14 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-02T14:00:00.033491018+00:00 · last event 2026-09-02T14:59:59.999960313+00:00
VOLUME 113,067,794 rows · 1,183,935,379 bytes (1.10 GiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured h: 112,198,144 · c: 112,185,967 · e: 111,639,774 · b: 102,714,289 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 665,672 (0.59%) · c: 74,603 (0.07%) · e: 111,637,876 (98.74%) · b: 689,643 (0.61%) (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 113,067,794 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 df0c44ad5ed3a166d4e52c72ae302abe08f4b05f03b5dda445803f773fc8cc8d
the corpus checksum ledger names this file with the same digest
joined 113,070,334 to merged 113,067,794, minus 2,540 (minus 0.0022%)
boundary drops 2,540 · 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-02T17:03:59Z as bceh
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 9,857,797 111,513,559 0-37 385c197319a3c773fe2787916cbf21898d8b81104f319b4f919b4e3144ae965b book 1,124,482 74,863,610 38-42 7e4b088a8c07cb6f3f5845d4c96eafe31a7a4476e7a557646a5c9f9cc62ebcd2 last_trade_price 80,085 4,468,777 43-43 28bc757065cd253e109d1a6a7ad97b9ca747350d7275cac29061c36c6cf68775 market_resolved 1,333 182,920 44-44 2a0148c178e9e934f5d1d3c75d02cadcbaed7db59ff5f0a33a2394f822d63482 new_market 1,771 178,777 45-45 df2319a5234ba1b411cb2efdaedb108d509f16e238d92ebba6823c160088840c price_change 101,999,334 991,328,250 46-435 82761d1216c4dce833426f98d7040978e121277e67a5cc55020dbaf2c1289bf5 tick_size_change 2,992 110,192 436-436 af92bf484a2c72d03828ee1fa5ae253647e43e56e339e804c5e1b1a5419f39cf EVENT MIX count share price_change 101,999,334 90.21% best_bid_ask 9,857,797 8.72% book 1,124,482 0.99% last_trade_price 80,085 0.07% tick_size_change 2,992 <0.01% new_market 1,771 <0.01% market_resolved 1,333 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,857,873 9,857,797 76 1,151 FULL book 1,125,078 1,124,482 596 175,830 FULL last_trade_price 80,085 80,085 0 136 FULL market_resolved 1,333 1,333 0 32 FULL new_market 1,771 1,771 0 0 FULL price_change 102,001,202 101,999,334 1,868 286 FULL tick_size_change 2,992 2,992 0 60 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 8,994,324 30 52ms 81ms 674ms 27.5s 0 transport_latency_assumed best_bid_ask c 9,857,205 507 5ms 10ms 94ms 2.8s 0 transport_latency_assumed best_bid_ask e 9,839,824 9,839,756 45ms 88ms 966ms 41.5s 0 transport_latency_assumed best_bid_ask h 9,856,239 17,504 18ms 34ms 197ms 39.9s 0 transport_latency_assumed book b 945,987 689,200 2.0min 8.4h 31.1d 95.7d 0 book_staleness book c 252,514 69,610 10ms 57.5min 21.8d 95.7d 0 book_staleness book e 262,432 262,378 1.3s 1.9h 25.0d 95.7d 0 book_staleness book h 273,307 103,294 76ms 2.0h 25.0d 95.7d 0 book_staleness last_trade_price b 71,394 5 82ms 3.1s 18.0s 27.5s 0 transport_latency_assumed last_trade_price c 80,036 10 10ms 39ms 206ms 5.0s 0 transport_latency_assumed last_trade_price e 76,840 76,840 75ms 4.8s 16.4s 41.2s 0 transport_latency_assumed last_trade_price h 80,016 3,230 26ms 162ms 1.1s 20.4s 0 transport_latency_assumed market_resolved b 1,253 213 55ms 6.3min 10.2min 11.6min 0 transport_latency_assumed market_resolved c 1,120 not meas. 5ms 10ms 364ms 51.8s 0 transport_latency_assumed market_resolved e 1,120 1,120 45ms 189ms 717ms 56.9s 0 transport_latency_assumed market_resolved h 1,120 not meas. 18ms 81ms 387ms 51.5s 0 transport_latency_assumed new_market b 1,208 115 339ms 1.6min 8.4min 8.4min 0 transport_latency_assumed new_market c 1,140 172 104ms 1.3min 1.7min 2.4min 0 transport_latency_assumed new_market e 1,140 1,140 283ms 1.3min 1.6min 1.7min 0 transport_latency_assumed new_market h 1,140 344 178ms 1.2min 1.8min 1.9min 0 transport_latency_assumed price_change b 92,697,359 80 53ms 108ms 3.2s 27.5s 0 transport_latency_assumed price_change c 101,990,960 4,304 5ms 10ms 101ms 3.9s 0 transport_latency_assumed price_change e 101,455,438 101,453,662 45ms 128ms 5.8s 41.5s 0 transport_latency_assumed price_change h 101,983,330 541,288 18ms 38ms 266ms 40.0s 0 transport_latency_assumed tick_size_change b 2,764 not meas. 52ms 87ms 690ms 8.3s 0 transport_latency_assumed tick_size_change c 2,992 not meas. 5ms 10ms 72ms 255ms 0 transport_latency_assumed tick_size_change e 2,980 2,980 45ms 106ms 681ms 6.1s 0 transport_latency_assumed tick_size_change h 2,992 12 18ms 37ms 191ms 1.1s 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/14/2026-09-02T14.parquet sha256sum 2026-09-02T14.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.