Core Concepts

QFlow uses a small vocabulary on purpose. A workflow record contains the visual design, generated source, provider route, run state, and evidence artifacts.

If you understand the concepts on this page, the rest of the docs read like a connected operating path instead of a collection of unrelated screens.

A workflow record is the durable unit of work. It gives a quantum task a name, owner, design state, code view, route decision, and review history.

Use records when you want repeatable work. Avoid treating a workflow as a disposable canvas if the output will be reviewed, taught, or run again.

Blocks represent the visual pieces on the canvas. Some blocks map directly to gates, while others represent workflow structure, templates, annotations, or handoff steps.

The block inspector turns a visual object into something precise: parameters, diagnostics, notes, history, and generated code context.

Evidence is the reviewable output of a run: counts, traces, source, route context, and public-safe proof pages.

Good evidence answers what ran, where it ran, what came back, and what remains private. It should not expose workspace credentials or admin-only information.