statecraft.
Catalog/spec-spine

168-ratification-has-two-paths

Ratification has two paths, both an owner approval

Lifecycle draftImplementation pendingVerification unknownQualification unknown

This repository builds a spec while it is still a draft and ratifies it in a second, hand-authored pull request. The owner has chosen ratify-then-build instead, with ratification as a triggerable action gated on an owner-only deployment environment, and a second path that ratifies at merge when a pull request lands a spec at draft and complete. Both paths flip only `status`, bind the approval to the exact bytes shown, and leave ratification owner-only.

Read the full pinned specification ↗

Relationships

Claimed units

  • extends
    {
  "nature": "corrective",
  "spec": "093-the-harness-this-repository-runs",
  "unit": {
    "kind": "file",
    "path": "AGENTS.md"
  }
}
  • extends
    {
  "nature": "corrective",
  "spec": "093-the-harness-this-repository-runs",
  "unit": {
    "kind": "directory",
    "path": ".claude/skills/"
  }
}

Source headings

  1. 168: Ratification has two paths, both an owner approval
  2. 1. Purpose
  3. 2. Territory
  4. 3. Behavior
  5. 3.1 One approval authority
  6. 3.2 Path A: ratify then build
  7. 3.3 Path B: ratify at merge
  8. 3.4 `AGENTS.md` names the two paths
  9. 3.5 The skills agree
  10. 4. Out of scope
  11. 5. Resolved decisions
  12. Verification

Frozen anchors

No frozen anchors declared.