105-governed-scope-is-enabled-here

Governed scope is enabled here

Lifecycle approvedImplementation completeVerification unknownQualification unknown

Spec 078 added `[coverage] governed_scope` so a repository can bring its governance files under the ownership ratchet, and the repository that wrote it never turned it on. The measured cost is four unclaimed paths. They are claimed, the scope is declared over exactly the files this repository already folds into its content hash, and what stays exempt is stated rather than implied.

Read the full pinned specification ↗

Relationships

depends on

amends

078-governed-scope-is-declared-not-inferred

Claimed units

establishes

{
  "kind": "file",
  "path": "CLAUDE.md"
}

establishes

{
  "kind": "file",
  "path": "scripts/bump_version.py"
}

establishes

{
  "kind": "file",
  "path": "standards/spec/templates/constitution-template.md"
}

extends

{
  "nature": "additive",
  "spec": "011-index-hash-slices",
  "unit": {
    "kind": "file",
    "path": "crates/spec-spine-types/schemas/build-meta.schema.json"
  }
}

extends

{
  "nature": "additive",
  "spec": "061-shipped-is-not-the-same-as-working",
  "unit": {
    "kind": "file",
    "path": "spec-spine.toml"
  }
}

Source headings

105: Governed scope is enabled here
1. Purpose
1.1 The measured cost, re-measured
2. Territory
3. Behavior
3.1 The scope is declared over what is already hashed
3.2 The four gaps are closed before the switch is thrown
3.3 Bypass semantics are not weakened
3.4 What stays exempt, stated plainly
3.5 `.claude/` is included, and leaves with the harness
3.6 Nothing about the mechanism changes
4. Out of scope
5. Resolved decisions
Verification

Frozen anchors

No frozen anchors declared.