034-boundary-read-acceptance
Protected boundary acceptance preserves read-only checkout access
Lifecycle approvedImplementation completeVerification unknownQualification unknown
Corrects the self-test and hostile-fixture acceptance of spec 004 section 3.18 to preserve rule 2: the operator checkout and other attempt workspaces remain readable, and mutations are refused. Product home and launch records remain inaccessible except for the existing explicit exceptions.
Read the full pinned specification ↗Relationships
depends on
Claimed units
- extends
{ "nature": "corrective", "spec": "002-environment-lifecycle", "unit": { "kind": "directory", "path": "crates/statecraft-home/" } } - extends
{ "nature": "corrective", "spec": "006-command-surface", "unit": { "kind": "directory", "path": "crates/statecraft-cli/" } }
Source headings
- 034: Protected boundary read acceptance
- 1. Purpose
- 2. Boundaries
- 3. Required behavior
- 3.1 Self-test
- 3.2 Hostile-fixture acceptance
- 3.3 Confined capture project binding
- 4. Acceptance criteria
- 5. Resolved decisions
- Verification
Frozen anchors
No frozen anchors declared.