Hour audit: 2026-09-18T15
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-18T15 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-18T15:00:00.000246314+00:00 · last event 2026-09-18T15:59:59.999982444+00:00
VOLUME 134,057,313 rows · 1,506,837,009 bytes (1.40 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 131,040,746 · e: 130,778,525 · g: 117,231,256 · f: 115,340,775 · c: 98,854,737 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 35,397,372 (26.40%) · e: 4,106,675 (3.06%) · g: 302,596 (0.23%) · f: 1,328,592 (0.99%) · c: 92,922,078 (69.32%) (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 134,057,313 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 38ef1b14bbb5dab430505e6480540c77b31a426d1b5a82a66287f369ad5baf2d
the corpus checksum ledger names this file with the same digest
joined 134,074,350 to merged 134,057,313, minus 17,037 (minus 0.0127%)
boundary drops 17,037 · 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-18T17:02:11Z 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 14,536,352 171,054,431 0-55 c839b6cb45e615522ebf67e9b640d0ad126ac199708907cb9c832c3076510362 book 3,052,938 132,336,646 56-67 1233b90d52ab40710157a8edbf856f3a74fb9ae4da21a5aa9ba75e0deea3e215 last_trade_price 72,454 4,240,131 68-68 41461464208501b3126b1efa56e7524fe6af89cf77f4e335d5b253983f8e1bf1 market_resolved 2,035 186,120 69-69 8f2d22c96dcb5eac62e7910e0ea4bcaccd52f8578cca39f4ddb2da61ab22e34a new_market 2,082 141,060 70-70 2d42d75594697b84f8322829a2c0d4812a5ce5c59e49dd1834a0cb399036ba96 price_change 116,386,476 1,197,173,437 71-514 640ad85cf93b4a4838532b9791adadff510435da726ebe02cd7dd5bd5670c910 tick_size_change 4,976 183,546 515-515 38ed1cef2e4f4bbe3865f421cec4e239bbe5ced3111c25f36ff57fc7047ec96e EVENT MIX count share price_change 116,386,476 86.82% best_bid_ask 14,536,352 10.84% book 3,052,938 2.28% last_trade_price 72,454 0.05% tick_size_change 4,976 <0.01% new_market 2,082 <0.01% market_resolved 2,035 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 14,536,679 14,536,352 327 11,366 FULL book 3,066,698 3,052,938 13,760 197,133 FULL last_trade_price 72,456 72,454 2 1,527 FULL market_resolved 2,046 2,035 11 288 FULL new_market 2,093 2,082 11 34 FULL price_change 116,389,402 116,386,476 2,926 19,693 FULL tick_size_change 4,976 4,976 0 512 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,696,763 10,094,925 6ms 16ms 115ms 4.4s 0 transport_latency_assumed best_bid_ask e 14,530,189 451,289 43ms 57ms 255ms 20.1s 0 transport_latency_assumed best_bid_ask f 12,723,486 75,027 48ms 64ms 253ms 23.9s 0 transport_latency_assumed best_bid_ask g 13,034,598 10,797 81ms 106ms 442ms 27.2s 0 transport_latency_assumed best_bid_ask h 14,534,291 3,904,314 18ms 44ms 173ms 9.1s 0 transport_latency_assumed book c 2,551,149 2,268,621 4.9min 13.9h 37.9d 111.7d 0 book_staleness book e 155,973 8,831 48ms 2.8s 41.0min 93.2d 0 book_staleness book f 1,369,183 583,770 4.3min 10.5h 37.0d 111.7d 0 book_staleness book g 565,087 148,207 1.9min 7.3h 29.4d 111.7d 0 book_staleness book h 156,460 43,509 23ms 105ms 14.3min 104.0d 0 book_staleness last_trade_price c 52,167 49,298 12ms 47ms 272ms 5.3s 0 transport_latency_assumed last_trade_price e 71,338 1,858 64ms 1.5s 9.7s 19.9s 0 transport_latency_assumed last_trade_price f 61,153 554 66ms 850ms 10.7s 23.9s 0 transport_latency_assumed last_trade_price g 63,057 241 104ms 2.3s 11.7s 27.0s 0 transport_latency_assumed last_trade_price h 72,250 20,503 27ms 99ms 512ms 6.0s 0 transport_latency_assumed market_resolved c 1,787 1,689 6.6min 21.7min 23.7min 26.0min 0 transport_latency_assumed market_resolved e 860 8 45ms 176ms 437ms 1.1s 0 transport_latency_assumed market_resolved f 839 72 49ms 363ms 3.3min 4.6min 0 transport_latency_assumed market_resolved g 858 73 87ms 894ms 8.8min 8.8min 0 transport_latency_assumed market_resolved h 860 193 19ms 68ms 195ms 1.2s 0 transport_latency_assumed new_market c 1,688 1,284 5.4min 13.8min 19.2min 22.3min 0 transport_latency_assumed new_market e 811 183 170ms 19.4s 57.3s 1.2min 0 transport_latency_assumed new_market f 811 209 144ms 40.1s 4.3min 4.9min 0 transport_latency_assumed new_market g 812 100 291ms 5.6min 5.9min 7.1min 0 transport_latency_assumed new_market h 811 306 120ms 19.1s 1.1min 1.3min 0 transport_latency_assumed price_change c 85,547,735 80,502,974 6ms 18ms 139ms 4.4s 0 transport_latency_assumed price_change e 116,014,378 3,644,388 44ms 84ms 2.7s 20.1s 0 transport_latency_assumed price_change f 101,180,827 668,928 48ms 87ms 2.3s 23.9s 0 transport_latency_assumed price_change g 103,562,340 143,178 82ms 160ms 6.0s 27.3s 0 transport_latency_assumed price_change h 116,271,098 31,427,008 19ms 50ms 268ms 9.1s 0 transport_latency_assumed tick_size_change c 3,448 3,287 6ms 12ms 59ms 241ms 0 transport_latency_assumed tick_size_change e 4,976 118 43ms 55ms 268ms 646ms 0 transport_latency_assumed tick_size_change f 4,476 32 48ms 59ms 134ms 502ms 0 transport_latency_assumed tick_size_change g 4,504 not meas. 81ms 100ms 1.3s 2.2s 0 transport_latency_assumed tick_size_change h 4,976 1,539 19ms 40ms 170ms 512ms 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/15/2026-09-18T15.parquet sha256sum 2026-09-18T15.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.