Flowintent / proof
Loading docs
Use the QFlow Studio canvas to understand visual workflow blocks, connections, workflow switching, and responsive behavior.
The Studio canvas is where a workflow becomes visible. It shows the current record, visual blocks, and editing controls, with a top bar that holds the Code and Analyze tabs alongside the provider selector and Run action — routing is a control, not a separate tab.
Keep the canvas simple when teaching a team. Name the workflow clearly, keep block labels readable, and move into the inspector when a property needs precision.
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.
Start with the workflow title and the active top-bar tab (Design, Code, or Analyze). The canvas has its own CANVAS and 3D VIEW switch, separate from those page-level tabs. Then read the blocks and connections as the operational story of the circuit.
Use the canvas to explain intent. Use the inspector and code tab to explain exact behavior.
The workflow switcher is useful when a team has multiple experiments, lessons, or provider tests in progress.
Before editing, confirm you are in the intended workflow record. This reduces accidental changes to the wrong experiment.
The mobile Studio capture confirms the surface remains readable on small screens. Heavy design work is still best on desktop, but mobile review should not overflow or hide the main workflow state.
Use mobile for checking status, reviewing learning context, or confirming a workflow record while away from a workstation.
Inspect and explain QFlow Studio block properties, diagnostics, history, generated code context, and safe edits.
Use QFlow Studio components, gates, and reusable workflow blueprints without leaving the build context.
Review generated Qiskit, Cirq, and OpenQASM output beside the visual workflow before routing or exporting.