sopherapps · ch-ahindura · Aug 16, 2026 · Aug 10, 2026 · Aug 10, 2026 · Aug 10, 2026
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
@@ -116,6 +116,11 @@ jobs:
         cache-dependency-glob: "qpi-driver/py/pyproject.toml"
 
     - name: Run Tests for '${{ matrix.extra }}'
+      # Benchmarks thoroughly rather than just correctly: more circuits per depth, so the
+      # two RB fidelities are precise as well as resolved. Off by default so a local run
+      # is quick; on here, which covers every pull request and every tag.
+      env:
+        QPI_SLOW_BENCHMARKS: '1'
       run: |
         make test-py-loop EXECUTOR=${{ matrix.extra }}
 

diff --git a/.gitignore b/.gitignore
@@ -33,6 +33,7 @@ quantify.config.yml
 quantify.device.yml
 quantify.config.yaml
 quantify.device.yaml
+calibration.yml
 !**/fixtures/**.json
 !**/fixtures/**.yaml
 !**/fixtures/**.yml

diff --git a/CHANGELOG.md b/CHANGELOG.md
diff --git a/Makefile b/Makefile
@@ -1,4 +1,4 @@
-VERSION ?= 0.4.1
+VERSION ?= 0.4.2
 UV := $(shell command -v uv 2> /dev/null || echo "$$HOME/.local/bin/uv")
 EXECUTOR ?= mock
 EXECUTORS := mock aer quantify qblox

diff --git a/README.md b/README.md
@@ -77,12 +77,12 @@ The server is available as a single executable binary, as well as native OS pack
 #### Standalone Binary (macOS & Linux)
 Download the binary for your platform, make it executable, and run:
 ```bash
-# macOS (replace 0.4.1 with the version you wish to install)
-curl -LO https://github.com/sopherapps/qpi/releases/download/v0.4.1/qpi-0.4.1-darwin-amd64
-chmod +x qpi-0.4.1-darwin-amd64 && mv qpi-0.4.1-darwin-amd64 qpi
+# macOS (replace 0.4.2 with the version you wish to install)
+curl -LO https://github.com/sopherapps/qpi/releases/download/v0.4.2/qpi-0.4.2-darwin-amd64
+chmod +x qpi-0.4.2-darwin-amd64 && mv qpi-0.4.2-darwin-amd64 qpi
 
 # Linux (standalone binary)
-curl -L https://github.com/sopherapps/qpi/releases/download/v0.4.1/qpi-0.4.1-linux-amd64.tar.gz | tar -xz
+curl -L https://github.com/sopherapps/qpi/releases/download/v0.4.2/qpi-0.4.2-linux-amd64.tar.gz | tar -xz
 
 # Start the server
 ./qpi serve
@@ -91,8 +91,8 @@ curl -L https://github.com/sopherapps/qpi/releases/download/v0.4.1/qpi-0.4.1-lin
 #### Native Linux Packages (Ubuntu, Debian, Fedora, Alpine)
 For Debian/Ubuntu, download and install the `.deb` package:
 ```bash
-wget https://github.com/sopherapps/qpi/releases/download/v0.4.1/qpi_0.4.1_amd64.deb
-sudo apt install ./qpi_0.4.1_amd64.deb
+wget https://github.com/sopherapps/qpi/releases/download/v0.4.2/qpi_0.4.2_amd64.deb
+sudo apt install ./qpi_0.4.2_amd64.deb
 ```
 *(Note: Installing the package automatically registers and starts `qpi.service` under systemd (or OpenRC on Alpine) to run the server in the background on port `8090`)*
 

diff --git a/docs/rfcs/0007-calibration-without-priors.md b/docs/rfcs/0007-calibration-without-priors.md
diff --git a/docs/rfcs/0008-parameter-provenance.md b/docs/rfcs/0008-parameter-provenance.md
diff --git a/docs/rfcs/README.md b/docs/rfcs/README.md
@@ -14,9 +14,14 @@ holds both the system design and its phased implementation plan, so a contributo
 | [0004](./0004-calibration-tuners.md) | Calibration Tuners | Implemented |
 | [0005](./0005-calibration-graph-completion.md) | Calibration Graph Completion | Implemented |
 | [0006](./0006-calibration-graph-in-the-dashboard.md) | The Calibration Graph in the Dashboard | Draft |
+| [0007](./0007-calibration-without-priors.md) | Calibration Without Priors | Implemented (§11.5 open) |
+| [0008](./0008-parameter-provenance.md) | Parameter Provenance | Implemented |
 
-Neither calibration RFC has been verified against physical hardware; both say so
-where it matters.
+RFCs 0004 and 0005 were written before the graph had run on a chip, and say so where it
+matters. RFCs 0007 and 0008 are the opposite case: they exist because of what running it
+on one found. 0008 was the piece 0007 deferred; both are now implemented, and each records
+where building it corrected what it had claimed. 0007 §11.1 was added after both were
+closed, because hardware found it — a gap the RFC's own mechanism was meant to cover.
 
 ## Conventions
 

diff --git a/qpi-client/js/package-lock.json b/qpi-client/js/package-lock.json
diff --git a/qpi-client/js/package.json b/qpi-client/js/package.json
@@ -1,6 +1,6 @@
 {
   "name": "qpi-client",
-  "version": "0.4.1",
+  "version": "0.4.2",
   "description": "JavaScript/TypeScript client SDK for the QPI quantum computing platform",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",

diff --git a/qpi-client/py/pyproject.toml b/qpi-client/py/pyproject.toml
@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "qpi-client"
-version = "0.4.1"
+version = "0.4.2"
 description = "Python client SDK for the QPI quantum computing platform"
 readme = "README.md"
 license = {text = "MIT"}

diff --git a/qpi-client/py/qpi_client/__init__.py b/qpi-client/py/qpi_client/__init__.py
@@ -30,7 +30,7 @@
 try:
     __version__ = importlib.metadata.version("qpi-client")
 except importlib.metadata.PackageNotFoundError:
-    __version__ = "0.4.1"
+    __version__ = "0.4.2"
 
 from qpi_client.client import QPIClient
 from qpi_client.provider import QPIBackend, QPIJob

diff --git a/qpi-client/py/uv.lock b/qpi-client/py/uv.lock
diff --git a/qpi-driver/go/cli/cli.go b/qpi-driver/go/cli/cli.go
@@ -27,7 +27,7 @@ import (
 
 // Version is the CLI version; overridable at build time with
 // -ldflags "-X github.com/sopherapps/qpi/qpi-driver/go/cli.Version=…".
-var Version = "0.4.1"
+var Version = "0.4.2"
 
 // commonFlags are the universal options `start` shares across every operation,
 // mirroring the Python CLI. A device's own settings go through -o instead.

diff --git a/qpi-driver/js/package-lock.json b/qpi-driver/js/package-lock.json
diff --git a/qpi-driver/js/package.json b/qpi-driver/js/package.json
@@ -1,6 +1,6 @@
 {
   "name": "qpi-driver",
-  "version": "0.4.1",
+  "version": "0.4.2",
   "description": "TypeScript/JavaScript SDK for building QPI quantum platform drivers",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",

diff --git a/qpi-driver/py/calibration.example.yml b/qpi-driver/py/calibration.example.yml
@@ -6,12 +6,31 @@
 # working default — so the shortest useful file is just `target_qubits`. A
 # routine name that matches no routine is a startup error, not a silent no-op,
 # so a typo here is caught before any hardware is touched.
+#
+# Prefer leaving a sweep out to writing its default down. Several routines widen or
+# refine their own sweep when the fit says the window was wrong (RFC 0007 §5), and
+# naming an axis here switches that off for it deliberately: an operator who states a
+# range has made a claim about the chip, and the driver will not overrule it with a
+# default. Everything below is therefore an illustration of the *shape* of each config,
+# not a recommendation to paste.
+#
+# Write exponents as `20.0e+6` — decimal point *and* a signed exponent. PyYAML needs
+# both: `20e6`, `20.0e6` and `7.183e9` all parse as *strings*, while `20.0e+6` and
+# `4.0e-9` are numbers. The three forms are indistinguishable on the page. The driver
+# converts numeric strings on the way in, for configs and device files alike, so every
+# form works — but only one of them is a number in the file you are reading.
 
 target_qubits: [q0, q1, q2]
 target_edges: [q0_q1, q1_q2]
 
 # Wall-clock ceiling for one routine on one target. A routine that hangs on an
 # instrument would otherwise hang the worker for the life of the driver.
+#
+# Any routine may override it with its own `timeout_s`, and on a real chip several want to.
+# The cost of a single global number is that it has to be set for the slowest node, which
+# makes it no ceiling at all for the fast ones: `qubit_spectroscopy` pays for a wide search
+# and then a fine confirm at several drive powers, and has been measured at 299 s, while a
+# Rabi that takes more than a few seconds is hung.
 routine_timeout_s: 900
 
 routines:
@@ -20,44 +39,86 @@ routines:
     # Either an explicit list of frequencies, or a span about the value
     # currently in quantify.device.yml — the latter being what a
     # recalibration wants, since it only has to find where the peak moved to.
-    span: 20e6
+    #
+    # Leave `span` out on a bring-up. Left to itself this node widens and re-runs when
+    # the resonator turns out to be outside the window, and samples harder when the line
+    # is thinner than the grid; naming a span here means a resonator a few MHz away fails
+    # the run instead. `points` is safe to set — it is the resolution, not the reach.
+    span: 20.0e+6
     points: 51
     shots: 1024
 
   resonator_punchout:
-    amplitudes: [0.01, 0.05, 0.1, 0.2, 0.3, 0.4, 0.5]
-    span: 20e6
+    # Reaching 1.0 matters: punch-through is by definition the high-power end, and a grid
+    # stopping at half scale cannot find it on a line carrying any real attenuation — with
+    # 20 dB of `output_att` it is some 26 dB short. Spaced log-ish, since punch-through is
+    # a log-power effect, so the points sit where the transition is.
+    #
+    # Watch the cost. This sweeps frequency *and* power, and a frequency sweep costs about
+    # 15 Q1ASM instructions per point against a QRM ceiling of 12288 — so amplitudes x
+    # points must stay under roughly 800.
+    amplitudes: [0.02, 0.08, 0.25, 0.6, 1.0]
+    span: 20.0e+6
     points: 31
 
   qubit_spectroscopy:
-    span: 40e6
+    # Its own ceiling, because this is the expensive node: a search across everything the
+    # port can reach, then a confirming sweep at each drive power. Raising the global limit
+    # to suit it would stop it catching a hang anywhere else.
+    timeout_s: 900
+    # Two passes. `span`/`points` is the narrow sweep about the configured f01; if no line
+    # is there, `search_*` looks across everything the drive port can reach and the narrow
+    # sweep is repeated where it found one. Both are trimmed to the port's +/-500 MHz of
+    # its LO, so a search wider than that simply covers the whole band.
+    span: 40.0e+6
     points: 51
-    # Deliberately weak: saturating the transition broadens the line and hides
-    # the centre this routine exists to find.
-    drive_amp: 0.01
+    search_span: 600.0e+6
+    search_points: 301
+    # A geometric *range*, not one power. Weak is right in principle — saturating the
+    # transition broadens the line and pulls the centre this routine exists to find — but
+    # too weak is a line under the noise, which is a failed run rather than a cautious one.
+    # `fit_spectroscopy_power` keeps the narrowest credible line of the set, so a wide
+    # bracket costs acquisitions rather than accuracy, and geometric spacing is what covers
+    # an unknown scale. Each power multiplies the acquisition count, so watch the ceiling.
+    #
+    # `search_amp` is deliberately absent: the widening pass drives at the strongest of
+    # these by default, which is the pass that has to see a line at all.
+    drive_amps: [0.01, 0.03, 0.1, 0.3]
 
   # --- Single-qubit gates ---
   rabi:
+    # Half scale, because a strongly driven transmon stops being the cosine this fits.
+    # Left unset, `rabi` starts here and reaches further when the fit says the pi pulse is
+    # above the sweep — which naming the axis here turns off.
     amplitudes: [0.0, 0.05, 0.1, 0.15, 0.2, 0.25, 0.3, 0.35, 0.4, 0.45, 0.5]
 
   ramsey:
-    delays: [4e-9, 1e-6, 2e-6, 3e-6, 4e-6, 5e-6, 7e-6, 10e-6]
-    artificial_detuning: 1e6
+    delays: [4.0e-9, 1.0e-6, 2.0e-6, 3.0e-6, 4.0e-6, 5.0e-6, 7.0e-6, 10.0e-6]
+    artificial_detuning: 1.0e+6
 
   t1:
-    delays: [0, 10e-6, 20e-6, 30e-6, 40e-6, 60e-6, 80e-6, 100e-6]
+    delays: [0.0, 10.0e-6, 20.0e-6, 30.0e-6, 40.0e-6, 60.0e-6, 80.0e-6, 100.0e-6]
 
   t2_echo:
-    delays: [0, 10e-6, 20e-6, 30e-6, 40e-6, 60e-6, 80e-6, 100e-6]
+    delays: [0.0, 10.0e-6, 20.0e-6, 30.0e-6, 40.0e-6, 60.0e-6, 80.0e-6, 100.0e-6]
 
   drag:
-    motzois: [-1.0, -0.75, -0.5, -0.25, 0.0, 0.25, 0.5, 0.75, 1.0]
+    # Seconds, not a dimensionless amplitude: the DRAG parameter scales a time derivative
+    # of the envelope, so a 56 ns gate wants values of order 1e-11. At a dimensionless
+    # scale the derivative term dwarfs the carrier and the waveform exceeds full scale.
+    motzois: [-2.0e-10, -1.0e-10, -5.0e-11, 0.0, 5.0e-11, 1.0e-10, 2.0e-10]
 
   allxy: {}
 
   fine_amplitude:
     repetitions: [1, 3, 5, 7, 9, 11, 13, 15, 17, 19, 21, 23, 25]
 
+  # Every fourth count, and not by preference: only after 4k+1 quarter turns does
+  # the accumulated error lie along the axis being measured. The fit refuses any
+  # other spacing rather than fitting three quarters noise.
+  fine_amplitude_90:
+    repetitions: [1, 5, 9, 13]
+
   # --- Benchmarks: measured, never written back ---
   rb:
     depths: [1, 2, 4, 8, 16, 32, 64]
@@ -77,7 +138,7 @@ routines:
   cz_chevron:
     enabled: false
     amplitudes: [0.1, 0.2, 0.3, 0.4, 0.5]
-    durations: [20e-9, 60e-9, 100e-9, 140e-9, 180e-9]
+    durations: [20.0e-9, 60.0e-9, 100.0e-9, 140.0e-9, 180.0e-9]
 
   conditional_phase:
     enabled: false

diff --git a/qpi-driver/py/pyproject.toml b/qpi-driver/py/pyproject.toml
@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "qpi-driver"
-version = "0.4.1"
+version = "0.4.2"
 description = "Quantum Processing Interface (QPI) QPU Driver"
 readme = "README.md"
 requires-python = ">=3.12,<3.13"

diff --git a/qpi-driver/py/qpi_driver/__init__.py b/qpi-driver/py/qpi_driver/__init__.py
@@ -3,7 +3,7 @@
 try:
     __version__ = importlib.metadata.version("qpi-driver")
 except importlib.metadata.PackageNotFoundError:
-    __version__ = "0.4.1"
+    __version__ = "0.4.2"
 
 from qpi_driver.builtins import (
     DeviceBuilder,