Loading docs
Run & Route
Results and Evidence
Use run history, evidence packets, certificates, and approved shares without exposing private workspace data.
Updated May 26, 2026QFlow StudioNormal userTeacher
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.
Purpose
Use run history, evidence packets, certificates, and approved shares without exposing private workspace data.
Where it fits
This page belongs to the Run & Route section and should be read with the related pages listed at the end.
Review boundary
Use screenshots and notes to explain product behavior without exposing private credentials, admin state, or customer data.
What evidence should contain
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.
Workflow
Circuit/source
Provider route
Counts or trace
Review state
Share proof, not secrets
Approved shares and certificates should expose proof, not private workspace internals.
Never include provider tokens, private billing state, admin-only notes, hidden user records, or raw secrets in public result documentation.
Next pages
Security model
Understand provider credential boundaries, reviewer-safe shares, role isolation, and safe documentation capture.
Quickstart
Follow the first QFlow Studio workflow from canvas setup through provider selection, run feedback, and run history.
Providers
Select quantum providers, inspect hardware fit, and keep credentials private while routing workflows.