Private
Operational data stays inside authenticated workspaces.
Evidence
QFlow evidence packets keep the circuit, generated Qiskit/OpenQASM source, provider route, run result, trace, and reviewer-safe manifest together in one workflow record.

QF-SAMPLE-BELL
Local Qiskit Aer simulator, no provider token required
Qiskit and OpenQASM stay attached to the visual workflow record.
Counts JSON, CSV rows, and probabilities are visible without provider credentials.
Queued, running, completed, failed, and retry states become part of review.
Reviewer-safe links show the artifact, not private workspace operations.
One workflow record
The reviewer sees a connected chain instead of screenshots from notebooks, provider consoles, and reports.
intent, owner, success criteria
editable circuit blocks
generated Qiskit and OpenQASM
credentials, device fit, route rationale
simulator or submit-capable provider path
counts, probabilities, trace, failure state
JSON, CSV, manifest, reviewer note
public-safe result or certificate link
Sample packet
This Bell State sample shows the shape of a packet: source, OpenQASM, counts, and manifest. Provider tokens, billing records, raw credentials, and admin notes are excluded.
generated-qiskit.py
from qiskit import QuantumCircuit
qc = QuantumCircuit(2, 2)
qc.h(0)
qc.cx(0, 1)
qc.measure([0, 1], [0, 1])generated-openqasm.qasm
OPENQASM 3;
include "stdgates.inc";
bit[2] c;
qubit[2] q;
h q[0];
cx q[0], q[1];
c[0] = measure q[0];
c[1] = measure q[1];evidence-manifest.json
{
"workflowId": "QF-SAMPLE-BELL",
"runner": "qiskit-aer",
"artifacts": [
"generated-qiskit.py",
"generated-openqasm.qasm",
"counts.json",
"counts.csv",
"trace.json"
],
"privateFieldsExcluded": [
"providerCredentialId",
"userEmail",
"billingState",
"adminNotes"
]
}Private/public boundary
Evidence is useful only when it is explicit about what reviewers can see and what remains role-gated.
Operational data stays inside authenticated workspaces.
Reviewers receive only the proof needed to inspect a result.
Next step