Flowintent / proof
Loading docs
Use run history, evidence packets, approved shares, and JSON/CSV exports without exposing private workspace data.
Evidence is the public-safe part of execution. It lets reviewers understand the circuit, counts, traces, and result context without entering the private workspace.
Use evidence pages for review and proof. Use the private workspace for credentials, billing, permissions, and provider setup.
This page belongs to the Run & Route 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 good evidence packet answers four questions: what was the workflow, what code or circuit was run, what route was selected, and what result came back.
If a reviewer cannot understand those four points, the evidence is incomplete.
Approved shares and exports should expose proof, not private workspace internals. (Completion certificates are a separate, learning-only artifact and are not produced by a run.)
Never include provider tokens, private billing state, admin-only notes, hidden user records, or raw secrets in public result documentation.
Understand provider credential boundaries, reviewer-safe shares, role isolation, and safe documentation capture.
Follow the first QFlow Studio workflow from canvas setup through provider selection, run feedback, and run history.
Select quantum providers, inspect hardware fit, and keep credentials private while routing workflows.