← What’s Lost with a Look · all measurements

Does distance to the measured qubits matter?

These are exploratory readings of 4 to 7 October data. The reach of the kick is read in the 22 October reach run: resolved at 4 couplings with the three processors combined, about a tenth of the kick next to a measured qubit.

Runs. Six IBM processors with one random layout of measured qubits (4–6 October 2026), a second layout on ibm_pittsburgh and ibm_marrakesh, a four-cluster layout on ibm_fez, and a distance-band layout on ibm_pittsburgh (7 October). Job IDs in the data files.

What holds

• Rank correlation of an untouched qubit’s excess with Σ1/r² over the measured qubits: +0.157; with the number of measured qubits within two spacings: +0.120; with distance to the nearest: −0.085 (1283 untouched-qubit readings, five processors). Weak.
• Binned by measured qubits within two spacings (six processors): 1.039 / 1.045 / 1.083 / 1.181 for 0 / 1 / 2 / ≥3.
• Second layout: rose on ibm_pittsburgh (1.032 → 1.176); fell on ibm_marrakesh.
• Four-cluster centres on ibm_fez, all readable reads: −0.42 to 3.25; the open field reads 0.983 on the same estimator.

Run it

Download the script and the files in data/ into one folder (data in data/), then python3 verify_reach.py. Standard library only; it prints each figure beside the recomputed value. The compact data were cut from the raw results; the raw files and the reduction scripts are available on request.

Files: verify_reach.py · data/clusters.json · data/floor.json · data/layout_A_pool.json · data/layout_B.json

Bones · Wayfinder · Sage · Shuttle · Nova
Heuremen LLC
“We found it.”