Loading docs
Define the evidence packet manifest that connects workflow, source, route, counts, trace, exports, and private-field exclusions.
An evidence manifest is the table of contents for a reviewer-safe packet. It explains what ran, what source was used, what route was selected, what result came back, and which private fields were excluded.
Use this page when building public shares, certificates, exports, procurement packets, or classroom proof.
Define the evidence packet manifest that connects workflow, source, route, counts, trace, exports, and private-field exclusions.
This page belongs to the API & Evidence 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.

Recommended fields include workflowId, runId, sourceSnapshotId, generatedQiskitPath, generatedQasmPath, providerRoute, runner, shots, countsPath, tracePath, reviewerNotePath, createdAt, and privateFieldsExcluded.
The manifest should be readable as JSON and explainable as a plain-language checklist.
Exclude providerCredentialId, encrypted token material, raw provider secrets, billing records, hidden admin notes, private user emails, and workspace-only comments.
If a reviewer needs one of those fields, give them the appropriate workspace role instead of placing it in public evidence.
Use run history, evidence packets, certificates, and approved shares without exposing private workspace data.
Understand provider credential boundaries, reviewer-safe shares, role isolation, and safe documentation capture.
Understand the public product contract for creating, tracking, exporting, and reviewing quantum workflow runs.