Portfolio · hybrid-execution
Hybrid execution
Systems desk
Hybrid execution runs a classical program and a quantum circuit in a loop. The systems desk uses it for variational schedules, where angles move on the classical side and shots are taken on the quantum side.
The shared object
The shared object is the quantum circuit model: qubits, gates, and the angles that are still free. The classical optimiser proposes those angles. It does not write amplitudes. The quantum side executes the list and returns an estimate from measurement and sampling. It does not see the optimiser’s line search.
A small-n check uses state-vector simulation so the loop can be debugged without a device. A wider circuit may use tensor-network contraction when the bonds allow it. A device run adds noise and error, which the optimiser will treat as part of the cost unless the note says otherwise.
What counts as a result
A finished hybrid study records the gate list, the angle schedule, the shot count, the noise model if a device was used, and the final estimated cost. A plot of angles without those fields is a lab trace, not a finding.
The same contract is how the computation, simulation, measurement, and systems desks pass work to one another. Each concept stays on its own path under /doc/, and the Portfolio index is the map.
Finding from this desk
The systems desk’s finding is a contract: the classical side proposes parameters, the quantum side returns an estimate, and neither side edits the other’s representation. The gate list is the object they share.