statecraft.
Catalog/spec-spine

040-governance-document-gaps

Three governance statements the first adopter could not act on

Lifecycle approvedImplementation completeVerification unknownQualification unknown

hqgit is the first repository outside this one to adopt spec-spine, and what its author had to write by hand is a measurement of what the governance documents fail to supply. Three findings. First, the constitution's own Amendment clause names a mechanism that cannot be written: it says the constitution may be amended by "an ordinary spec that `amends` it", but `amends` resolves to spec ids and the constitution is not a spec, so the sentence has no implementation, and hqgit copied it verbatim into a corpus where it is equally unwritable. Spec 037 4 named this as an open question and deliberately did not answer it; this spec answers it. Second, spec 000 3 files `depends_on` and `implementation` under "optional descriptive keys", which was true when it was written and is now false: 033 refuses a cycle in one, and 038 and 041 make the other decide scheduling and diagnostic severity. hqgit had to write its own "lifecycle as scheduling" section because tier 1 reads as though the field were inert. Third, constitution V says pre-existing code is evidence but never says what to write about code adopted with defects; hqgit supplied the missing half. The scaffold learns all three, because the scaffolded constitution is four bullets with no tier statement, no normative hierarchy and no amendment clause, and the evidence is that the first adopter did not use it.

Read the full pinned specification ↗

Relationships

Claimed units

  • establishes
    {
  "anchor": "amending-the-constitution",
  "file": "standards/spec/contract.md",
  "kind": "section"
}
  • 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"
  }
}
  • refines
    {
  "aspect": "constitution-amendment",
  "unit": {
    "anchor": "amendment",
    "file": "standards/spec/constitution.md",
    "kind": "section"
  }
}
  • refines
    {
  "aspect": "adopted-code-as-evidence",
  "unit": {
    "anchor": "v-legacy-as-evidence",
    "file": "standards/spec/constitution.md",
    "kind": "section"
  }
}

Source headings

  1. 040: Three governance statements the first adopter could not act on
  2. 1. Purpose
  3. 1.1 The constitution cannot be amended by the mechanism it names
  4. 1.2 Tier 1 calls two operational fields descriptive
  5. 1.3 Constitution V has no operational half
  6. 1.4 What this measurement also says about the scaffold
  7. 2. Territory
  8. 3. Behavior
  9. 3.1 Amending the constitution
  10. 3.1.1 The mechanism
  11. 3.1.2 The constitution is edited in place, and why that is not spec 037's rule reversed
  12. 3.1.3 The claim is a ledger fact, not a gate refusal
  13. 3.2 `depends_on` and `implementation` are lifecycle keys
  14. 3.3 Adopted code is specced as found
  15. 3.4 The scaffold ships all three
  16. 4. Out of scope

Frozen anchors

No frozen anchors declared.