002-environment-lifecycle

Project registration and the Statecraft-managed environment: one global home, one project area, one initialization flow, and where authority comes from

Lifecycle approvedImplementation completeVerification unknownQualification unknown

Defines repository registration, initialization, the global and per-project environment, ownership classes, manifests, configuration provenance, upgrade, removal, transfer, and setup-profile rendering. Harness delivery, governance-producer adoption, and managed-session evidence are separated into specs 008, 009, and 015.

Read the full pinned specification ↗

Relationships

Claimed units

  • establishes
    {
      "kind": "directory",
      "path": "crates/statecraft-environment/"
    }
  • establishes
    {
      "kind": "directory",
      "path": "crates/statecraft-home/"
    }
  • establishes
    {
      "kind": "file",
      "path": "scripts/acceptance/managed-session.sh"
    }
  • extends
    {
      "nature": "additive",
      "spec": "006-command-surface",
      "unit": {
        "kind": "directory",
        "path": "crates/statecraft-cli/"
      }
    }
  • extends
    {
      "nature": "corrective",
      "spec": "001-boundaries-and-authority",
      "unit": {
        "kind": "file",
        "path": "scripts/check-authored-content.sh"
      }
    }
  • extends
    {
      "nature": "corrective",
      "spec": "004-execution-adapter",
      "unit": {
        "kind": "directory",
        "path": "crates/statecraft-adapter-claude-code/"
      }
    }
  • extends
    {
      "nature": "additive",
      "spec": "004-execution-adapter",
      "unit": {
        "kind": "directory",
        "path": "crates/statecraft-adapter/"
      }
    }

Source headings

  1. 002: Project registration and the Statecraft-managed environment
  2. 1. Purpose
  3. 2. Territory
  4. 3. Behavior
  5. 3.1 Registration and qualification
  6. 3.2 The three ownership classes
  7. 3.3 The manifest
  8. 3.4 Install, plan, upgrade
  9. 3.5 Drift, and what `doctor` reports
  10. 3.6 Removal
  11. 3.7 The transition contract with `spec-spine init --with-kit` (withdrawn)
  12. 3.8 User instructions are preserved
  13. 3.10 Observable negative cases
  14. 3.11 One Statecraft-managed global environment
  15. 3.12 One per-project area
  16. 3.13 The root instruction bridge
  17. 3.16 Configuration authority
  18. 3.17 Initialization, and the verbs
  19. 3.18 Solo and team
  20. 3.19 The one-time relocation of the compiled artifacts
  21. 3.20 The operation boundary a dashboard uses
  22. 3.21 What replaces the kit transition contract
  23. 3.35 Per-path ownership transfer, as an operator's act
  24. 4. Out of scope
  25. 5. Resolved decisions
  26. Verification

Frozen anchors

No frozen anchors declared.