015-managed-session-evidence
Managed-session evidence and admission
Lifecycle approvedImplementation in-progressVerification unknownQualification unknown
Carries the live-observation, control, startup-record, launch-state, managed-trial, trailer, and confinement requirements relocated from spec 002. It separates runtime evidence from installation and harness delivery.
Read the full pinned specification ↗Relationships
Claimed units
- extends
{ "nature": "additive", "spec": "002-environment-lifecycle", "unit": { "kind": "directory", "path": "crates/statecraft-home/" } } - extends
{ "nature": "additive", "spec": "004-execution-adapter", "unit": { "kind": "directory", "path": "crates/statecraft-adapter-claude-code/" } }
Source headings
- 015: Managed-session evidence and admission
- 1. Purpose
- 2. Territory
- 3. Behavior
- 3.29 What admits a live observation
- 3.30 What each control must demonstrate, and what binds a capture to its launch
- 3.31 The startup record a run writes, and the harness revision that answered
- 3.32 Launch states, the correlated acknowledgment, per-invocation startup delivery, and when governed work is released
- 3.33 The managed-startup trial, and why it is not the permission experiment
- 3.34 One allowlisted event after the terminal event
- 3.37 Where an attempt's launch records live, and what the child is given
- 4. Out of scope
- 5. Resolved decisions
- Verification
Frozen anchors
No frozen anchors declared.