Flowintent / proof
Loading docs
Use QFlow Studio components, gates, and reusable workflow blueprints without leaving the build context.
The component library is where users add gates, reusable workflow pieces, and task-specific components to the current record.
Use components when a workflow should remain visual and explainable rather than hidden inside custom source files.
This page belongs to the Build Workflows section and should be read with the related pages listed at the end.
Use screenshots and notes to explain product behavior without exposing private credentials, admin state, or customer data.
A new user may not remember every gate label. Teach them to search for the operation they want and inspect the component before adding it.
After adding a component, return to the canvas and confirm that the block sits in the expected place in the workflow.
For repeatable work, start from library blueprints rather than rebuilding a workflow from memory.
Blueprints are especially useful for lessons, demos, provider readiness tests, and onboarding new team members.
Every block in this palette executes. Each gate, channel, and composite runs in the local state-vector/trajectory simulator and survives the full roundtrip — canvas blocks to operations to generated Qiskit, Cirq, and OpenQASM and back — so the canvas never shows an operation that cannot run.
The gate-model surface tracks 2026 hardware natives: superconducting fractional and echoed cross-resonance gates (RZZ, RZX, ECR on IBM Heron), trapped-ion Mølmer–Sørensen rotations (RXX on IonQ and Quantinuum), neutral-atom digital gate mode (Rydberg-blockade CZ-style entanglers), and discrete-variable photonic gate circuits. Dynamic circuits — mid-circuit measurement, RESET, classically conditioned blocks, and bounded repeats — execute per-shot in the trajectory engine and on hardware as if/else feed-forward, and the noise channels (depolarizing, amplitude/phase damping, bit/phase flip) sample real per-shot Kraus trajectories.
We deliberately do not fake what a 2^n gate-model state vector cannot execute. Continuous-variable photonic qumode operations (squeezing, displacement, Kerr — Xanadu) live in infinite-dimensional Fock space, not qubits. Analog Hamiltonian drives (QuEra Aquila, Pasqal) are a different program type entirely — an atom register plus Ω/Δ waveforms, not gates. Annealing QUBO embedding (D-Wave) is a problem model with no circuit decomposition. Pulse-level control was retired industry-wide in February 2025; its replacement — fractional gates — is already in this palette. None of these appear here as decorative blocks.
Where those live instead: the provider catalog and hardware targets mark analog and annealing devices honestly (analog-only / annealing-model, no gate-circuit submission), and CV-photonic SDKs are confined to isolated research runner profiles. The honest gate-model bridges are in the composites library — the Trotterized Ising/Rydberg step digitally approximates analog evolution, and the QAOA QUBO step attacks the same problems annealers take natively. Error suppression (dynamical decoupling, twirling, readout mitigation) is a hardware submit-time run option, not circuit content; unbounded while/switch and subroutine calls are warned on import, never silently faked.
Start from reusable workflow blueprints, starter circuits, and patterns before building a workflow from scratch.
Use the QFlow Studio canvas to understand visual workflow blocks, connections, workflow switching, and responsive behavior.
Follow the first QFlow Studio workflow from canvas setup through provider selection, run feedback, and run history.