Flowintent / proof
Loading docs
Definitions for common QFlow Studio terms: workflow, block, provider, route, run, trace, evidence, academy, and teacher source.
Use the glossary when a term appears in product UI, docs, or review conversations and needs a stable meaning.
The definitions are written for product teams, not for a physics textbook. They explain how QFlow uses each term operationally.
This page belongs to the Reference 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 saved operating record that keeps the visual design, generated code, route context, run state, and evidence together.
A visual object on the canvas. A block may represent a gate, operation, template, annotation, or workflow component.
A quantum execution or simulation backend available through configured private access and route checks.
The provider decision attached to a workflow: which backend or simulator a run targets, recorded so results can be interpreted later.
A single execution of a workflow under a chosen route and mode (simulation, dry-run, or hardware). A run moves through queued, running, and then completed, failed, or cancelled, and the record is preserved as evidence.
The step-level or measurement detail captured from a run, used alongside counts to explain what actually happened during execution.
Reviewer-safe proof from a run, including circuit/source context, counts or trace data, route decision, and approval state.
The in-product learning space with lessons, modules, a code lab, and a resource library. Progress is personal to the signed-in user; role changes permissions, not the learner view.
An academic source that any signed-in member (teachers included) can submit to the academy review queue. Approval and publishing are handled by permission-holders in the admin console.
Learn the product language behind workflows, blocks, generated code, provider routing, runs, evidence, and learning records.
Follow the first QFlow Studio workflow from canvas setup through provider selection, run feedback, and run history.
Understand provider credential boundaries, reviewer-safe shares, role isolation, and safe documentation capture.