statecraft.
Catalog/spec-spine

101-readiness-is-scheduling-not-approval

Readiness is scheduling, not approval

Lifecycle approvedImplementation completeVerification unknownQualification unknown

`registry plan` partitions by `implementation` and `depends_on` and never by `status`, so a draft appears on the ready set by design. The layering is deliberate and stays; what is missing is a governed sentence saying so, which a consumer reading the document directly has no way to infer.

Read the full pinned specification ↗

Relationships

Claimed units

  • extends
    {
  "nature": "additive",
  "spec": "057-the-docs-name-what-adopters-derived",
  "unit": {
    "kind": "file",
    "path": "docs/api.md"
  }
}
  • extends
    {
  "nature": "additive",
  "spec": "061-shipped-is-not-the-same-as-working",
  "unit": {
    "kind": "file",
    "path": "spec-spine.toml"
  }
}

Source headings

  1. 101: Readiness is scheduling, not approval
  2. 1. Purpose
  3. 1.1 The layering is deliberate and is not reopened
  4. 1.2 What is wrong today, precisely
  5. 2. Territory
  6. 3. Behavior
  7. 3.1 The documentation states what membership means
  8. 3.2 It is a documentation requirement and nothing else
  9. 3.3 The claimed file is hashed
  10. 4. Out of scope
  11. 5. Resolved decisions
  12. Verification

Frozen anchors

No frozen anchors declared.