Hour audit: 2026-09-15T09
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-15T09 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-15T09:00:00.000046978+00:00 · last event 2026-09-15T09:59:59.999983234+00:00
VOLUME 114,787,224 rows · 1,225,702,321 bytes (1.14 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 113,849,478 · g: 113,745,153 · e: 112,560,822 · f: 112,553,450 · c: 105,954,531 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 12,134,345 (10.57%) · g: 38,516 (0.03%) · e: 1,055,847 (0.92%) · f: 278,618 (0.24%) · c: 101,279,898 (88.23%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 114,787,224 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 43894d4f42ca22c682b95f00197474e09672ab600ad113858d78c84d6a655f87
the corpus checksum ledger names this file with the same digest
joined 114,790,324 to merged 114,787,224, minus 3,100 (minus 0.0027%)
boundary drops 3,100 · 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-15T11:36:17Z 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,347,852 127,981,753 0-43 f7b961fabc156ee944bfafd79069859e1e9746068c9a2297ef1b719d28fe1009 book 985,675 73,657,498 44-47 794a8d02eb754f721feb3a9d166c45055f7608b424f048c900f1602476db5163 last_trade_price 53,779 3,136,052 48-48 b71d49db0cbf4952dc57bc66f41a69a3c948908397ae64cb8e16b712280657d1 market_resolved 710 110,344 49-49 d61e42e6a45560f68365d35b9099bab4030267444ae0b60fadc64899af813631 new_market 754 84,231 50-50 d9b3802b30c4c00724d620ab7e5188397b1c80d42a60d18710375d019b4a2af2 price_change 102,395,362 1,019,313,683 51-441 c579420d9c53d5e1009d008e5ec17916ab6e647b0ad46459209488de583a1297 tick_size_change 3,092 112,099 442-442 4212cc1aad84d1adeb03a00c4f52a4c160bbbe589d365f99ea705234a02bb2c3 EVENT MIX count share price_change 102,395,362 89.20% best_bid_ask 11,347,852 9.89% book 985,675 0.86% last_trade_price 53,779 0.05% tick_size_change 3,092 <0.01% new_market 754 <0.01% market_resolved 710 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,348,068 11,347,852 216 813 FULL book 985,817 985,675 142 169,136 FULL last_trade_price 53,781 53,779 2 209 FULL market_resolved 710 710 0 44 FULL new_market 754 754 0 16 FULL price_change 102,398,102 102,395,362 2,740 544 FULL tick_size_change 3,092 3,092 0 45 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,459,592 10,014,364 5ms 11ms 74ms 1.6s 0 transport_latency_assumed best_bid_ask e 11,191,161 88,528 40ms 46ms 145ms 8.9s 0 transport_latency_assumed best_bid_ask f 11,191,533 14,754 48ms 57ms 172ms 8.2s 0 transport_latency_assumed best_bid_ask g 11,342,148 920 80ms 104ms 334ms 25.9s 0 transport_latency_assumed best_bid_ask h 11,346,734 1,229,286 18ms 26ms 96ms 9.5s 0 transport_latency_assumed book c 794,129 722,329 6.8min 2.2d 34.6d 108.5d 0 book_staleness book e 459,731 121,765 2.7min 23.0h 33.8d 108.5d 0 book_staleness book f 459,064 106,079 2.7min 1.1d 33.8d 108.5d 0 book_staleness book g 148,045 21,927 94ms 31.8min 9.8d 90.0d 0 book_staleness book h 113,868 13,575 22ms 78ms 6.1min 108.4d 0 book_staleness last_trade_price c 48,931 46,472 11ms 47ms 223ms 5.0s 0 transport_latency_assumed last_trade_price e 52,920 972 47ms 133ms 757ms 5.0s 0 transport_latency_assumed last_trade_price f 52,945 265 57ms 186ms 1.6s 6.7s 0 transport_latency_assumed last_trade_price g 53,238 26 94ms 320ms 3.1s 26.0s 0 transport_latency_assumed last_trade_price h 53,618 6,044 24ms 87ms 411ms 5.5s 0 transport_latency_assumed market_resolved c 636 618 5ms 14ms 5.1min 5.7min 0 transport_latency_assumed market_resolved e 672 28 41ms 130ms 47.5s 1.1min 0 transport_latency_assumed market_resolved f 672 1 49ms 139ms 54.2s 2.2min 0 transport_latency_assumed market_resolved g 672 not meas. 85ms 340ms 52.0s 1.0min 0 transport_latency_assumed market_resolved h 672 63 19ms 69ms 47.4s 1.1min 0 transport_latency_assumed new_market c 529 357 57ms 13.6s 35.0s 1.6min 0 transport_latency_assumed new_market e 542 111 148ms 18.6s 33.9s 2.2min 0 transport_latency_assumed new_market f 542 57 146ms 14.5s 29.8s 58.7s 0 transport_latency_assumed new_market g 542 59 241ms 17.7s 32.5s 57.8s 0 transport_latency_assumed new_market h 542 170 78ms 14.8s 32.7s 1.0min 0 transport_latency_assumed price_change c 94,647,802 90,492,950 5ms 13ms 84ms 3.0s 0 transport_latency_assumed price_change e 100,852,704 844,416 40ms 50ms 243ms 8.9s 0 transport_latency_assumed price_change f 100,845,602 157,462 49ms 63ms 305ms 8.8s 0 transport_latency_assumed price_change g 102,197,416 15,584 82ms 121ms 582ms 26.2s 0 transport_latency_assumed price_change h 102,330,952 10,884,950 18ms 29ms 142ms 9.5s 0 transport_latency_assumed tick_size_change c 2,912 2,808 5ms 11ms 54ms 107ms 0 transport_latency_assumed tick_size_change e 3,092 27 40ms 44ms 133ms 253ms 0 transport_latency_assumed tick_size_change f 3,092 not meas. 49ms 55ms 120ms 287ms 0 transport_latency_assumed tick_size_change g 3,092 not meas. 81ms 159ms 331ms 4.0s 0 transport_latency_assumed tick_size_change h 3,092 257 18ms 30ms 142ms 1.0s 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-15/09/2026-09-15T09.parquet sha256sum 2026-09-15T09.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.