Hour audit: 2026-09-18T13
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-18T13 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-18T13:00:00.000092477+00:00 · last event 2026-09-18T13:59:59.999977941+00:00
VOLUME 124,890,864 rows · 1,368,660,832 bytes (1.27 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 123,847,261 · e: 123,794,876 · g: 123,769,915 · f: 119,331,149 · c: 114,528,526 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 15,233,377 (12.20%) · e: 1,094,329 (0.88%) · g: 53,179 (0.04%) · f: 421,260 (0.34%) · c: 108,088,719 (86.55%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 124,890,864 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 81929414e758c377161a7243a51ffd5947ef7d9773eb66efe2e147dc2eb1195c
the corpus checksum ledger names this file with the same digest
joined 124,893,343 to merged 124,890,864, minus 2,479 (minus 0.0020%)
boundary drops 2,479 · 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-18T15:39:00Z 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 13,306,970 157,345,977 0-50 99940053f5f172ff62178b2d97aef96d8858635ec1b6f6792012177d4ad42b96 book 1,047,617 81,199,863 51-54 cef592a857f7c00768cbca392195906cef67523b375cc11e179349a3df6343e9 last_trade_price 73,021 4,265,962 55-55 c44dce67cf6c434fb881a23ff61a1daf91f81eb51bd61edeec280555d0bf8d61 market_resolved 769 121,600 56-56 f1cfd6dae93740f28bad2c2dad33c45a315d18ae6f3d7ab80c46b5d7d0198388 new_market 1,437 152,166 57-57 d5a8e1c7d390409fc70321be5e14967e9e81a57f5a19329345bce0b9d30940ac price_change 110,455,026 1,123,935,465 58-479 f6d57ec768da168dc52862ac104c07b6eec09c5fef085924a9165d052901859b tick_size_change 6,024 220,918 480-480 f8bd08c6ec3f0d703b08c9075d8b0718324f27a10c4fa53267912e709ea03c4b EVENT MIX count share price_change 110,455,026 88.44% best_bid_ask 13,306,970 10.65% book 1,047,617 0.84% last_trade_price 73,021 0.06% tick_size_change 6,024 <0.01% new_market 1,437 <0.01% market_resolved 769 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,307,270 13,306,970 300 1,304 FULL book 1,047,959 1,047,617 342 196,177 FULL last_trade_price 73,022 73,021 1 303 FULL market_resolved 769 769 0 21 FULL new_market 1,437 1,437 0 0 FULL price_change 110,456,862 110,455,026 1,836 878 FULL tick_size_change 6,024 6,024 0 79 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 12,178,026 11,515,832 5ms 15ms 134ms 13.8s 0 transport_latency_assumed best_bid_ask e 13,302,898 109,128 43ms 54ms 203ms 14.9s 0 transport_latency_assumed best_bid_ask f 12,721,942 31,776 48ms 60ms 220ms 19.5s 0 transport_latency_assumed best_bid_ask g 13,302,124 4,220 81ms 100ms 350ms 31.5s 0 transport_latency_assumed best_bid_ask h 13,304,897 1,646,014 18ms 40ms 173ms 34.9s 0 transport_latency_assumed book c 949,566 935,971 2.6min 9.4h 36.8d 111.6d 0 book_staleness book e 154,284 5,574 46ms 276ms 4.4min 93.0d 0 book_staleness book f 553,682 77,430 1.5min 5.8h 27.0d 111.6d 0 book_staleness book g 158,264 6,130 88ms 864ms 26.6min 93.1d 0 book_staleness book h 155,976 22,512 23ms 102ms 6.3min 93.1d 0 book_staleness last_trade_price c 66,720 62,613 11ms 47ms 254ms 5.0s 0 transport_latency_assumed last_trade_price e 72,377 840 52ms 194ms 6.2s 14.9s 0 transport_latency_assumed last_trade_price f 70,127 304 57ms 191ms 4.7s 19.5s 0 transport_latency_assumed last_trade_price g 72,158 95 95ms 303ms 9.1s 31.3s 0 transport_latency_assumed last_trade_price h 72,791 9,169 25ms 89ms 440ms 8.6s 0 transport_latency_assumed market_resolved c 696 664 6ms 31.2s 6.0min 6.0min 0 transport_latency_assumed market_resolved e 686 20 44ms 187ms 57.7s 58.1s 0 transport_latency_assumed market_resolved f 690 12 49ms 218ms 3.9min 5.6min 0 transport_latency_assumed market_resolved g 686 2 85ms 245ms 675ms 1.3s 0 transport_latency_assumed market_resolved h 686 71 19ms 78ms 58.5s 58.5s 0 transport_latency_assumed new_market c 986 602 84ms 455ms 4.1min 5.3min 0 transport_latency_assumed new_market e 984 208 175ms 17.1s 43.7s 1.7min 0 transport_latency_assumed new_market f 986 155 180ms 14.7s 48.9s 4.7min 0 transport_latency_assumed new_market g 984 110 263ms 16.5s 33.8s 1.1min 0 transport_latency_assumed new_market h 984 362 140ms 20.2s 46.2s 1.1min 0 transport_latency_assumed price_change c 101,326,784 95,567,417 6ms 17ms 148ms 13.8s 0 transport_latency_assumed price_change e 110,257,623 978,547 44ms 63ms 399ms 14.9s 0 transport_latency_assumed price_change f 105,977,866 311,583 48ms 69ms 404ms 19.6s 0 transport_latency_assumed price_change g 110,229,675 42,622 81ms 112ms 805ms 31.5s 0 transport_latency_assumed price_change h 110,305,903 13,554,857 18ms 45ms 227ms 35.0s 0 transport_latency_assumed tick_size_change c 5,748 5,620 5ms 10ms 32ms 4.0s 0 transport_latency_assumed tick_size_change e 6,024 12 43ms 52ms 121ms 1.9s 0 transport_latency_assumed tick_size_change f 5,856 not meas. 48ms 57ms 353ms 604ms 0 transport_latency_assumed tick_size_change g 6,024 not meas. 80ms 95ms 202ms 889ms 0 transport_latency_assumed tick_size_change h 6,024 392 18ms 32ms 114ms 1.8s 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-18/13/2026-09-18T13.parquet sha256sum 2026-09-18T13.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.