← Writing
Hardware · 2026

96 qubits, nine hours: the contract holds native drift

Fifty of fifty cycles on ibm_kingston through the public cloud, decision SUPPORTED under the registered rule. Drifting qubits gained 25.7 points of usable output; residual held at 0.27x drift; downtime was zero.

The useful question is not whether one optimizer is universally better. It is which information the loop receives, what each acquisition costs, and whether the method can make a complete decision before the operating point moves.

The measurement is part of the algorithm.

On physical hardware, an objective evaluation is not a free function call. It can be a batch of quantum shots, an optical scan, a cloud task, or minutes of instrument time. Methods that look similar in iteration count separate when their acquisition bill is made explicit.

TrueLoop uses one parallel acquisition for a complete multichannel update in its supported regime.

The complete loop must fit inside the deadline.

The configuration is not disposable. Carrying it forward preserves useful context between rounds. The IQM campaign validated the resulting advantage against hypotheses fixed before the run.

Fit is decided on the real interface.

Readout structure, timing, and target visibility determine whether the layer fits. The final answer comes from a fair race on the actual plant.