statecraft.
Catalog/spec-spine

045-couple-names-the-crossing

The coupling gate names the crossing

Lifecycle approvedImplementation completeVerification unknownQualification unknown

The coupling gate has always named the specs that own a drifted path, and has never named the mechanism for crossing into their territory. Its resolution footer offers two doors: edit an owning spec, or waive. For an author who has legitimately touched a unit somebody else owns, both are shut. Editing another spec to clear a refusal is the illegitimate edit the corpus rules forbid, and the waiver is a human instrument that no adopter has ever used and that an unattended session is forbidden on every path. The third door, an `extends` edge declared in the author's own spec, is the corpus's actual answer and the gate never mentions it. This spec makes the refusal name it: three doors in author order, and when the diff edits exactly one spec.md, the concrete `extends` block to paste into that file. It also promotes the owner set from prose into an optional `owners` field on the violation, so an orchestrator reading `couple --json` learns the owner as data instead of by regexing English. No committed artifact and no schema version moves.

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"
  }
}
  • extends
    {
  "nature": "additive",
  "spec": "000-spec-spine-bootstrap",
  "unit": {
    "kind": "file",
    "path": "crates/spec-spine-types/src/registry.rs"
  }
}
  • extends
    {
  "nature": "additive",
  "spec": "001-compile-registry",
  "unit": {
    "kind": "file",
    "path": "crates/spec-spine-core/src/compile.rs"
  }
}
  • extends
    {
  "nature": "additive",
  "spec": "002-registry-query",
  "unit": {
    "kind": "file",
    "path": "crates/spec-spine-core/src/query.rs"
  }
}
  • extends
    {
  "nature": "additive",
  "spec": "003-conformance-lint",
  "unit": {
    "kind": "file",
    "path": "crates/spec-spine-core/src/lint.rs"
  }
}
  • extends
    {
  "nature": "additive",
  "spec": "034-machine-readable-verdicts",
  "unit": {
    "kind": "file",
    "path": "crates/spec-spine-types/src/verdict.rs"
  }
}
  • extends
    {
  "nature": "additive",
  "spec": "043-verify-declared-acceptance",
  "unit": {
    "kind": "file",
    "path": "crates/spec-spine-cli/src/cmd_verify.rs"
  }
}
  • extends
    {
  "nature": "additive",
  "spec": "000-spec-spine-bootstrap",
  "unit": {
    "kind": "file",
    "path": "crates/spec-spine-types/tests/dtos.rs"
  }
}

Source headings

  1. 045: The coupling gate names the crossing
  2. 1. Purpose
  3. 2. Territory
  4. 2.1 Six more files the field's shape forces
  5. 3. Behavior
  6. 3.1 `C-001` carries its owners as data
  7. 3.2 The footer names three doors
  8. 3.3 The guidance is specific when the diff makes it specific
  9. 3.4 Nothing committed moves
  10. 3.5 The JSON form carries data, not prose
  11. 4. Out of scope
  12. 5. Verification

Frozen anchors

No frozen anchors declared.