Hour audit: 2026-09-11T09
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-11T09 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-11T09:00:00.000987786+00:00 · last event 2026-09-11T09:59:59.999937737+00:00
VOLUME 104,186,608 rows · 1,067,624,159 bytes (1018.17 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 103,748,231 · g: 103,746,478 · h: 103,744,214 · e: 103,737,067 · c: 99,185,888 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 74,599 (0.07%) · g: 11,172 (0.01%) · h: 7,993,940 (7.67%) · e: 297,465 (0.29%) · c: 95,809,432 (91.96%) (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 104,186,608 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 7b5a634eaf352ce1c9d9d760ca52f3376c0cfbca3df7efb073ee454d0af17937
the corpus checksum ledger names this file with the same digest
joined 104,190,213 to merged 104,186,608, minus 3,605 (minus 0.0035%)
boundary drops 3,605 · 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-11T10:57:31Z 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 9,030,402 101,441,436 0-34 94352748156746ac8f5075ee20b127fda2e16d588c19c3e965c87df84150fb94 book 524,089 57,397,886 35-36 2843811d772f5dffe489dc2e82d39702ae5cf5226a75d1201d370d6dfd6827bf last_trade_price 51,081 2,925,801 37-37 387ac6e6e0c9c4fb4fe3a83eaca04d337b34104804b2a3fb2da7c568b002434b market_resolved 485 79,920 38-38 4230d00f0587d1911234c8a164b063a697cd09a453a06dc0316174d125be9769 new_market 437 50,811 39-39 0708ef90748be5fea74b67b118ac4acc8c3c6f8ec75aa1c69c36cd49b786a492 price_change 94,577,854 904,457,732 40-400 394a7d153781abb1fe5d2d1706f73afdb401e22a1d69e8af349bec5f0e594028 tick_size_change 2,260 84,055 401-401 6c9a541b2ad11de0d142c6b409c79d5e993ea49acf80112adea6bdd61dfd9f89 EVENT MIX count share price_change 94,577,854 90.78% best_bid_ask 9,030,402 8.67% book 524,089 0.50% last_trade_price 51,081 0.05% tick_size_change 2,260 <0.01% market_resolved 485 <0.01% new_market 437 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,030,578 9,030,402 176 548 FULL book 524,092 524,089 3 202,946 FULL last_trade_price 51,083 51,081 2 64 FULL market_resolved 485 485 0 11 FULL new_market 437 437 0 0 FULL price_change 94,581,278 94,577,854 3,424 383 FULL tick_size_change 2,260 2,260 0 10 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,583,390 8,298,643 5ms 9ms 81ms 4.2s 0 transport_latency_assumed best_bid_ask e 9,028,882 24,847 37ms 41ms 119ms 2.2s 0 transport_latency_assumed best_bid_ask f 9,028,914 6,420 45ms 51ms 130ms 2.0s 0 transport_latency_assumed best_bid_ask g 9,028,737 638 77ms 92ms 249ms 17.3s 0 transport_latency_assumed best_bid_ask h 9,029,572 699,854 17ms 22ms 87ms 7.5s 0 transport_latency_assumed book c 512,889 506,570 7.8min 23.5h 27.0d 104.5d 0 book_staleness book e 107,340 1,803 39ms 112ms 4.0min 85.9d 0 book_staleness book f 106,768 1,018 47ms 112ms 2.6s 85.8d 0 book_staleness book g 112,643 4,337 79ms 351ms 15.5h 104.5d 0 book_staleness book h 106,560 10,361 21ms 42ms 763ms 40.9d 0 book_staleness last_trade_price c 48,077 46,075 10ms 40ms 182ms 5.0s 0 transport_latency_assumed last_trade_price e 51,006 246 44ms 108ms 781ms 5.0s 0 transport_latency_assumed last_trade_price f 50,984 47 52ms 113ms 433ms 5.0s 0 transport_latency_assumed last_trade_price g 51,049 18 86ms 215ms 1.0s 8.0s 0 transport_latency_assumed last_trade_price h 50,989 4,695 23ms 57ms 209ms 7.3s 0 transport_latency_assumed market_resolved c 459 445 5ms 12ms 6.0min 6.7min 0 transport_latency_assumed market_resolved e 465 14 38ms 187ms 46.1s 50.9s 0 transport_latency_assumed market_resolved f 465 1 47ms 200ms 46.1s 50.9s 0 transport_latency_assumed market_resolved g 465 not meas. 79ms 363ms 59.1s 59.8s 0 transport_latency_assumed market_resolved h 465 25 18ms 62ms 48.6s 53.2s 0 transport_latency_assumed new_market c 337 235 48ms 11.3s 2.8min 2.8min 0 transport_latency_assumed new_market e 328 41 114ms 485ms 43.2s 1.1min 0 transport_latency_assumed new_market f 328 43 139ms 12.0s 18.2s 1.0min 0 transport_latency_assumed new_market g 328 31 269ms 11.0s 17.1s 1.1min 0 transport_latency_assumed new_market h 328 87 79ms 12.1s 19.9s 1.2min 0 transport_latency_assumed price_change c 90,038,512 86,955,276 5ms 10ms 89ms 5.1s 0 transport_latency_assumed price_change e 94,546,786 270,514 37ms 43ms 160ms 2.2s 0 transport_latency_assumed price_change f 94,558,516 67,070 45ms 53ms 166ms 3.3s 0 transport_latency_assumed price_change g 94,550,996 6,148 77ms 96ms 315ms 17.3s 0 transport_latency_assumed price_change h 94,554,040 7,278,846 18ms 23ms 101ms 7.5s 0 transport_latency_assumed tick_size_change c 2,224 2,188 5ms 9ms 23ms 34ms 0 transport_latency_assumed tick_size_change e 2,260 not meas. 37ms 43ms 115ms 185ms 0 transport_latency_assumed tick_size_change f 2,256 not meas. 45ms 49ms 98ms 116ms 0 transport_latency_assumed tick_size_change g 2,260 not meas. 77ms 91ms 174ms 254ms 0 transport_latency_assumed tick_size_change h 2,260 72 18ms 22ms 76ms 305ms 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-11/09/2026-09-11T09.parquet sha256sum 2026-09-11T09.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.