You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Persist audit, provenance, and signoff as exportable evidence bundles #13
The public site emphasizes lab-facing prototype evidence. Studio currently keeps run output and audit trail lines in memory with a capped ring buffer. That is useful for the UI, but it is not enough for reviewable design evidence, reproducible experiment handoff, or lab/pre-hardware signoff.
Proposed Solution
Add an evidence bundle export:
circuit document,
runtime input JSON,
run output JSON,
trace metadata/checksum,
foundry profile id/version/hash,
KPI policy id/version,
audit trail with actor/action/timestamp/before-after summary,
bosonic signoff summary,
environment/tool versions,
optional PDF report.
Use a deterministic folder or archive layout and include a manifest checksum.
Acceptance Criteria
Exporting an evidence bundle creates a self-contained review artifact.
Audit entries are structured objects, not only display strings.
Bundle replay command is printed and documented.
Tests verify manifest contents and checksum stability for a seeded example.
Sensitive material such as signing keys is never included.
Validation
bash scripts/swift-test.sh
swift run schrosim-cli run docs/examples/runtime_default_foundry.json --backend hybrid
Activity