statecraft.
Catalog/spec-spine

061-shipped-is-not-the-same-as-working

Shipped is not the same as working

Lifecycle approvedImplementation completeVerification unknownQualification unknown

Two adopters installed spec-spine on the same day and each found a shipped artifact that does not do what it says. A glob form that matches no files reached one by hand and the other through a pre-069 scaffold, where the fix to the default can never arrive and 058's migration note explicitly does not look. `init --with-kit` writes the merge-driver hooks without an executable bit and without the binding that makes them fire. It installs a script the tool absorbed two releases ago, and it will write a second spec at an ordinal the corpus already uses. The session protocol calls a version read a precondition and never schedules it, while the skill beside it still prescribes the stderr ritual that protocol retired. Every one of these shipped for the same reason: the acceptance asserted that a thing exists rather than that it works. This spec closes them together and adds the refusal that would have caught the first one in an adopter's own config.

Read the full pinned specification ↗

Relationships

Claimed units

  • extends
    {
  "nature": "additive",
  "spec": "092-the-engine-ships-governance-not-an-environment",
  "unit": {
    "kind": "file",
    "path": "crates/spec-spine-core/src/scaffold.rs"
  }
}
  • extends
    {
  "nature": "additive",
  "spec": "092-the-engine-ships-governance-not-an-environment",
  "unit": {
    "kind": "file",
    "path": "crates/spec-spine-core/tests/scaffold.rs"
  }
}
  • extends
    {
  "nature": "additive",
  "spec": "003-conformance-lint",
  "unit": {
    "kind": "file",
    "path": "crates/spec-spine-core/src/lint.rs"
  }
}
  • extends
    {
  "nature": "additive",
  "spec": "093-the-harness-this-repository-runs",
  "unit": {
    "kind": "file",
    "path": "crates/spec-spine-core/tests/harness_skills.rs"
  }
}
  • extends
    {
  "nature": "additive",
  "spec": "043-verify-declared-acceptance",
  "unit": {
    "kind": "file",
    "path": "crates/spec-spine-core/tests/verify.rs"
  }
}
  • extends
    {
  "nature": "additive",
  "spec": "057-the-docs-name-what-adopters-derived",
  "unit": {
    "kind": "file",
    "path": "spec-spine.toml"
  }
}
  • extends
    {
  "nature": "additive",
  "spec": "093-the-harness-this-repository-runs",
  "unit": {
    "kind": "file",
    "path": "AGENTS.md"
  }
}
  • extends
    {
  "nature": "additive",
  "spec": "093-the-harness-this-repository-runs",
  "unit": {
    "kind": "file",
    "path": ".claude/skills/"
  }
}
  • extends
    {
  "nature": "additive",
  "spec": "057-the-docs-name-what-adopters-derived",
  "unit": {
    "kind": "file",
    "path": "docs/adoption-guide.md"
  }
}
  • extends
    {
  "nature": "additive",
  "spec": "046-depends-on-ordinal-monotonicity",
  "unit": {
    "kind": "file",
    "path": "crates/spec-spine-core/tests/lint.rs"
  }
}

Source headings

  1. 061: Shipped is not the same as working
  2. 1. Purpose
  3. 2. Territory
  4. 3. Behavior
  5. 3.1 A hashed-input pattern that can match no file is refused
  6. 3.2 The `L-008` message explains the choice it offers (conformance with 057)
  7. 3.3 `--with-kit` writes the binding for the driver it installs (amends 065)
  8. 3.4 A scaffolded executable arrives executable
  9. 3.5 `init` does not create a corpus its own compiler refuses
  10. 3.6 The kit stops shipping what the tool absorbed
  11. 3.7 The protocol schedules the read it calls a precondition
  12. 3.8 This repository pins itself
  13. 3.9 The migration note reaches the cohort that cannot be fixed by upgrading
  14. 3.10 The guards run what was written
  15. 4. Out of scope
  16. 5. Resolved decisions
  17. Verification

Frozen anchors

No frozen anchors declared.