statecraft.
Catalog/spec-spine

115-bindings-are-designed-not-shipped

Bindings are designed, not shipped

Lifecycle approvedImplementation n-aVerification unknownQualification unknown

`docs/bindings-plan.md` designs napi, pyo3 and cgo bindings and says no binding code belongs in this repository. That mandate lived only in a document header. This records it in the corpus as a policy, and states the obligations the JSON facade keeps so that a binding remains buildable elsewhere, each as it measurably holds today. It builds nothing, endorses no external binding, and is reviewable rather than enforced. Its implementation is `n-a`: there is no binding to implement, and this spec is the decision not to.

Read the full pinned specification ↗

Relationships

Claimed units

  • establishes
    {
  "kind": "file",
  "path": "docs/bindings-plan.md"
}
  • extends
    {
  "nature": "additive",
  "spec": "092-the-engine-ships-governance-not-an-environment",
  "unit": {
    "kind": "file",
    "path": "spec-spine.toml"
  }
}

Source headings

  1. 115: Bindings are designed, not shipped
  2. 1. Purpose
  3. 1.1 Why the dependency is spec 001
  4. 2. Territory
  5. 3. Behavior
  6. 3.1 No binding code in this repository
  7. 3.2 The facade is the seam, and what that obliges
  8. 3.3 The mandate is reviewable, not enforced
  9. 3.4 What this establishes, and what it does not
  10. 4. Out of scope
  11. 5. Resolved decisions
  12. Verification

Frozen anchors

No frozen anchors declared.