Hour audit: 2026-09-23T02
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-23T02 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-23T02:00:00.000021001+00:00 · last event 2026-09-23T02:59:59.999502534+00:00
VOLUME 118,500,825 rows · 1,274,361,609 bytes (1.19 GiB) · 7 products, all holding rows
WITNESSES cfhik — 5 machines contributed rows
captured i: 116,963,589 · h: 116,836,275 · f: 112,222,058 · c: 112,047,140 · k: 103,706,268 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 2,882,981 (2.43%) · h: 3,270,303 (2.76%) · f: 239,917 (0.20%) · c: 102,305,415 (86.33%) · k: 9,802,209 (8.27%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 118,500,825 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 bcd0374fe6ec90ac4549ce2bc408f246e210a50530f35d4707018e69f1509770
the corpus checksum ledger names this file with the same digest
joined 118,502,089 to merged 118,500,825, minus 1,264 (minus 0.0011%)
boundary drops 1,264 · 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-23T04:04:42Z as cfhik
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,549,423 134,045,598 0-44 b7ead81154342d50ab96c4a13ecb6c147722bbf71eff8af07c2dc0e9f06f48dd book 1,608,718 82,076,170 45-51 97204b01bb05405ded75afa90c46c4c02e0d3b0e94816d72d248c63faf6de980 last_trade_price 51,692 2,920,216 52-52 dded85d7e3656f13947c363972e10e6a5b2e6c72a54cd30466e561460b1888b7 market_resolved 2,782 304,572 53-53 5665974b65885ee8af799b145a928b75f08f40b3a9a2e8bd0a15af8f4af79980 new_market 1,342 146,863 54-54 e45e1235ec7f8516e8cb62e6e7ecb5d86454e8d121a43a328dde8d9cffe4db30 price_change 105,282,800 1,053,369,848 55-456 385e88727a6b74a4ce1f2ba3cafc51e567cc197f03675c58606f05ac46ede364 tick_size_change 4,068 147,181 457-457 060b926159d4e93cf6d374ba000eccd33ae3744c48dd32c23423ce5c68cef716 EVENT MIX count share price_change 105,282,800 88.85% best_bid_ask 11,549,423 9.75% book 1,608,718 1.36% last_trade_price 51,692 0.04% tick_size_change 4,068 <0.01% market_resolved 2,782 <0.01% new_market 1,342 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,549,570 11,549,423 147 2,573 FULL book 1,608,784 1,608,718 66 192,380 FULL last_trade_price 51,693 51,692 1 231 FULL market_resolved 2,782 2,782 0 13 FULL new_market 1,342 1,342 0 36 FULL price_change 105,283,850 105,282,800 1,050 2,256 FULL tick_size_change 4,068 4,068 0 186 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,025,843 10,196,333 5ms 13ms 120ms 4.6s 0 transport_latency_assumed best_bid_ask f 11,047,618 7,357 48ms 62ms 207ms 6.5s 0 transport_latency_assumed best_bid_ask h 11,542,490 293,677 18ms 40ms 164ms 55.4s 0 transport_latency_assumed best_bid_ask i 11,547,105 261,083 20ms 29ms 110ms 4.1s 0 transport_latency_assumed best_bid_ask k 10,162,138 790,973 12ms 20ms 94ms 10.0s 0 transport_latency_assumed book c 564,023 232,050 6.6min 2.5d 38.5d 116.2d 0 book_staleness book f 550,237 136,138 5.7min 2.4d 38.5d 116.2d 0 book_staleness book h 127,543 19,368 23ms 8.9min 10.5d 97.7d 0 book_staleness book i 143,621 21,718 26ms 29.7min 15.7d 97.7d 0 book_staleness book k 1,315,222 1,199,444 10.1min 3.5d 42.3d 116.2d 0 book_staleness last_trade_price c 48,508 43,313 6ms 25ms 223ms 953ms 0 transport_latency_assumed last_trade_price f 49,716 148 50ms 126ms 2.2s 6.5s 0 transport_latency_assumed last_trade_price h 51,083 1,744 19ms 61ms 339ms 17.9s 0 transport_latency_assumed last_trade_price i 51,410 1,737 21ms 63ms 319ms 1.1s 0 transport_latency_assumed last_trade_price k 43,991 4,750 14ms 32ms 194ms 1.3s 0 transport_latency_assumed market_resolved c 1,871 1,575 5ms 288ms 6.9min 7.0min 0 transport_latency_assumed market_resolved f 1,855 44 49ms 27.0s 3.9min 5.6min 0 transport_latency_assumed market_resolved h 1,845 37 18ms 32.0s 57.8s 1.0min 0 transport_latency_assumed market_resolved i 1,845 310 21ms 32.6s 58.4s 1.0min 0 transport_latency_assumed market_resolved k 2,259 816 20ms 9.0min 11.2min 11.3min 0 transport_latency_assumed new_market c 942 510 101ms 45.4s 1.6h 1.6h 0 transport_latency_assumed new_market f 902 144 188ms 13.5s 52.0s 1.9min 0 transport_latency_assumed new_market h 902 163 168ms 14.2s 51.9s 1.8min 0 transport_latency_assumed new_market i 902 264 114ms 9.8s 51.4s 2.1min 0 transport_latency_assumed new_market k 984 261 124ms 1.5min 6.1min 6.9min 0 transport_latency_assumed price_change c 100,402,185 91,828,029 5ms 17ms 139ms 8.7s 0 transport_latency_assumed price_change f 100,568,098 96,086 49ms 70ms 290ms 6.5s 0 transport_latency_assumed price_change h 105,108,344 2,955,204 18ms 45ms 195ms 56.9s 0 transport_latency_assumed price_change i 105,214,638 2,597,739 20ms 35ms 145ms 4.1s 0 transport_latency_assumed price_change k 92,178,074 7,805,742 13ms 24ms 113ms 10.2s 0 transport_latency_assumed tick_size_change c 3,768 3,605 5ms 8ms 438ms 735ms 0 transport_latency_assumed tick_size_change f 3,632 not meas. 48ms 56ms 364ms 962ms 0 transport_latency_assumed tick_size_change h 4,068 110 18ms 50ms 222ms 571ms 0 transport_latency_assumed tick_size_change i 4,068 130 20ms 29ms 246ms 432ms 0 transport_latency_assumed tick_size_change k 3,600 223 12ms 18ms 254ms 469ms 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-23/02/2026-09-23T02.parquet sha256sum 2026-09-23T02.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.