030-no-provider-directories
A governed project needs no provider-specific directory, and this product writes none
Makes the absence of provider-specific project directories (`.claude/`, `.codex/`, `.agents/`, `.agent/` and their equivalents) a supported and tested operating condition. No adapter declares a managed or adopted path inside one. The Claude Code adapter's owned instructions file moves out of `.claude/statecraft/` into content this product already manages, and its pointer, where one is still needed, imports `.statecraft/AGENTS.md` directly. A project that already holds the old file converges through the ordinary upgrade and removal rules. A qualification case starts with every provider directory absent and proves initialization, the governed verbs and context delivery work and recreate none of them. Brings the adapter into line with spec 002 section 3.12 and spec 008 section 3.14, and amends the adapter declaration of spec 004.
Read the full pinned specification ↗Relationships
Claimed units
- extends
{ "nature": "corrective", "spec": "004-execution-adapter", "unit": { "kind": "directory", "path": "crates/statecraft-adapter-claude-code/" } } - extends
{ "nature": "corrective", "spec": "002-environment-lifecycle", "unit": { "kind": "directory", "path": "crates/statecraft-home/" } } - extends
{ "nature": "additive", "spec": "002-environment-lifecycle", "unit": { "kind": "directory", "path": "crates/statecraft-environment/" } } - extends
{ "nature": "additive", "spec": "006-command-surface", "unit": { "kind": "directory", "path": "crates/statecraft-cli/" } }
Source headings
- 030: No provider directories
- 1. Purpose
- 2. Territory
- 3. Behavior
- 3.1 No provider directory in a target
- 3.2 Where the adapter's content goes
- 3.3 Convergence of existing projects
- 3.4 Observable negative cases
- 4. Out of scope
- 5. Resolved decisions
- Verification
Frozen anchors
No frozen anchors declared.