statecraft.
Catalog/spec-spine

056-the-contract-records-the-lifecycle-table

The contract records the lifecycle table and the extra keys

Lifecycle approvedImplementation completeVerification unknownQualification unknown

`status` and `implementation` are the two keys every adopter reasons about daily, and the contract mentions `status` once, in a list of required frontmatter, and `implementation` not at all. The mechanical consequences are spread across four specs: 041 makes a `complete` claim checkable, 044 defines the in-flight window, 045 says an absent key takes its answer from `status`, and 038 reads both to build the ready set. Every specify-first adopter wrote the resulting table into its own contract by hand, and hqgit had to invent a section called "Lifecycle as scheduling" because ours has none. This spec adds that section and an "Extra keys" section telling adopters to document their `extra_known_keys`, and claims both as section units of the contract.

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": "040-governance-document-gaps",
  "unit": {
    "kind": "file",
    "path": "standards/spec/contract.md"
  }
}

Source headings

  1. 056: The contract records the lifecycle table and the extra keys
  2. 1. Purpose
  3. 2. Territory
  4. 3. Behavior
  5. 3.1 Lifecycle as scheduling
  6. 3.2 Extra keys
  7. 3.3 The scaffold ships both
  8. 3.4 The lifecycle table is a summary, not a fifth authority
  9. 3.5 Nothing mechanical changes
  10. 4. Out of scope
  11. 5. Verification

Frozen anchors

No frozen anchors declared.