Hour audit: 2026-09-06T13
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-06T13 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-06T13:00:00.067730777+00:00 · last event 2026-09-06T13:59:59.999970815+00:00
VOLUME 124,626,079 rows · 1,344,567,353 bytes (1.25 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 122,436,746 · h: 122,372,900 · g: 122,354,739 · e: 122,277,687 · c: 95,863,137 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 349,927 (0.28%) · h: 30,803,644 (24.72%) · g: 38,883 (0.03%) · e: 1,836,639 (1.47%) · c: 91,596,986 (73.50%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 9f3592c0dd3634c552d4e25465eb82b2ae483099e40e6394bf251be2d5eb07f9
the corpus checksum ledger names this file with the same digest
joined 124,628,231 to merged 124,626,079, minus 2,152 (minus 0.0017%)
boundary drops 2,152 · 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-06T22:34:39Z 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 11,281,912 127,997,357 0-43 de8081693c99a77d92fe7ebe363f93c2a8fb652320eb0ff7caeab7b360c127c4 book 2,261,954 92,290,952 44-52 0b963697d287e00898d61982739fef83d5cb7eb582cf6ae269d574b472204976 last_trade_price 68,703 3,991,326 53-53 3b7385428fdf7213099ff0a93e9c8ed60a9e050bfb5f469221872552975d88aa market_resolved 2,687 292,374 54-54 68519d9a51fe65d645a70cf0e6997d9998c2fd9dead2dfe25858bf78e7fe1f38 new_market 2,706 261,423 55-55 91fd82db3bed93a7165502029fbb8f2e5b510926e43e3c32f83b5d6172cd3df7 price_change 111,000,101 1,118,022,832 56-479 3d9ecb414d42fe982ac407cc1f485848ae0e670da145f7e47502d7ab31660b7d tick_size_change 8,016 292,208 480-480 55e25ad61b1d8a748c9df388e0bb0e25d44d141ea6f6fb49d0a12cb6332df978 EVENT MIX count share price_change 111,000,101 89.07% best_bid_ask 11,281,912 9.05% book 2,261,954 1.81% last_trade_price 68,703 0.06% tick_size_change 8,016 <0.01% new_market 2,706 <0.01% market_resolved 2,687 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,282,120 11,281,912 208 4,063 FULL book 2,261,984 2,261,954 30 172,024 FULL last_trade_price 68,707 68,703 4 511 FULL market_resolved 2,687 2,687 0 182 FULL new_market 2,706 2,706 0 0 FULL price_change 111,002,011 111,000,101 1,910 2,194 FULL tick_size_change 8,016 8,016 0 422 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,610,383 8,240,071 5ms 12ms 147ms 5.6s 0 transport_latency_assumed best_bid_ask e 11,279,614 164,667 39ms 48ms 201ms 5.9s 0 transport_latency_assumed best_bid_ask f 11,279,946 28,617 49ms 60ms 215ms 3.6s 0 transport_latency_assumed best_bid_ask g 11,278,049 2,371 81ms 105ms 424ms 21.1s 0 transport_latency_assumed best_bid_ask h 11,280,056 2,846,186 18ms 32ms 241ms 34.3s 0 transport_latency_assumed book c 2,223,481 2,215,450 4.5min 22.3h 35.1d 99.6d 0 book_staleness book e 143,747 5,557 42ms 149ms 3.0s 33.9d 0 book_staleness book f 143,603 1,864 51ms 151ms 2.5s 81.0d 0 book_staleness book g 147,249 3,080 87ms 494ms 2.0h 81.1d 0 book_staleness book h 144,273 36,003 24ms 75ms 3.5s 81.0d 0 book_staleness last_trade_price c 52,037 49,237 10ms 45ms 335ms 5.0s 0 transport_latency_assumed last_trade_price e 68,623 1,630 46ms 129ms 1.4s 5.9s 0 transport_latency_assumed last_trade_price f 68,686 265 55ms 133ms 1.4s 5.0s 0 transport_latency_assumed last_trade_price g 68,405 32 94ms 265ms 11.3s 21.1s 0 transport_latency_assumed last_trade_price h 68,579 17,539 25ms 71ms 513ms 11.3s 0 transport_latency_assumed market_resolved c 2,206 2,104 8ms 13.2min 18.6min 19.7min 0 transport_latency_assumed market_resolved e 1,757 82 41ms 180ms 55.2s 59.5s 0 transport_latency_assumed market_resolved f 1,759 4 50ms 181ms 55.2s 59.5s 0 transport_latency_assumed market_resolved g 1,759 2 86ms 247ms 903ms 1.9s 0 transport_latency_assumed market_resolved h 1,759 495 20ms 60ms 375ms 1.9s 0 transport_latency_assumed new_market c 1,765 1,176 99ms 50.8s 2.3h 8.6h 0 transport_latency_assumed new_market e 1,662 400 149ms 22.6s 1.2min 4.0h 0 transport_latency_assumed new_market f 1,662 316 183ms 26.4s 1.3min 3.4h 0 transport_latency_assumed new_market g 1,662 172 277ms 21.4s 1.3min 2.4h 0 transport_latency_assumed new_market h 1,662 642 138ms 24.0s 1.3min 1.9h 0 transport_latency_assumed price_change c 84,966,937 81,083,009 5ms 13ms 172ms 7.6s 0 transport_latency_assumed price_change e 110,774,268 1,664,177 40ms 52ms 254ms 6.0s 0 transport_latency_assumed price_change f 110,933,074 318,813 49ms 65ms 252ms 3.7s 0 transport_latency_assumed price_change g 110,849,599 33,218 82ms 117ms 534ms 21.1s 0 transport_latency_assumed price_change h 110,868,555 27,900,884 19ms 34ms 260ms 34.7s 0 transport_latency_assumed tick_size_change c 6,328 5,939 5ms 13ms 484ms 2.8s 0 transport_latency_assumed tick_size_change e 8,016 126 40ms 49ms 343ms 747ms 0 transport_latency_assumed tick_size_change f 8,016 48 48ms 59ms 438ms 1.4s 0 transport_latency_assumed tick_size_change g 8,016 8 81ms 101ms 730ms 1.5s 0 transport_latency_assumed tick_size_change h 8,016 1,895 18ms 29ms 561ms 5.6s 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-06/13/2026-09-06T13.parquet sha256sum 2026-09-06T13.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.