statecraft.
Catalog/spec-spine

008-coupling-floor-claim-precedence

Coupling gate: explicit unit claims take precedence over the bypass floor

Lifecycle approvedImplementation completeVerification unknownQualification unknown

Amends 005 §3.5: a path covered by an explicit unit claim (a file, section, or symbol declared in some spec's ownership-bearing edge and resolved into the index) is NEVER bypassed, even when it matches the hardcoded floor or an adopter's additive bypass list. Implicit path-level ownership (manifest floors, comment headers) keeps deferring to bypass. Closes the silent- weakening hole where an adopter who governs workflow YAML or specific docs by explicit claim would have those claims ignored because `.github/` and `docs/` sit on the immutable floor.

Read the full pinned specification ↗

Relationships

Claimed units

  • extends
    {
  "nature": "additive",
  "spec": "005-coupling-gate",
  "unit": {
    "kind": "file",
    "path": "crates/spec-spine-core/src/couple.rs"
  }
}
  • extends
    {
  "nature": "additive",
  "spec": "005-coupling-gate",
  "unit": {
    "kind": "file",
    "path": "crates/spec-spine-core/tests/couple.rs"
  }
}
  • extends
    {
  "nature": "additive",
  "spec": "005-coupling-gate",
  "unit": {
    "kind": "file",
    "path": "crates/spec-spine-cli/src/cmd_couple.rs"
  }
}
  • extends
    {
  "nature": "additive",
  "spec": "005-coupling-gate",
  "unit": {
    "kind": "file",
    "path": "crates/spec-spine-cli/tests/couple.rs"
  }
}

Source headings

  1. 008: Explicit unit claims take precedence over the bypass floor
  2. 1. Purpose
  3. 2. Territory
  4. 3. Behavior
  5. 3.1 The precedence rule
  6. 3.2 What does NOT override bypass
  7. 3.3 Precedence over adopter additions too
  8. 3.4 Effect on this repo's own corpus
  9. 3.5 Determinism and report shape
  10. 3.6 Tests (minimum)
  11. 4. Out of scope

Frozen anchors

No frozen anchors declared.