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 validation. Use the private workspace for credentials, billing, permissions, and provider setup.
Section 01
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.
Section 02
Approved shares and exports should expose evidence, 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.