statecraft.
Catalog/spec-spine

099-a-merged-acceptance-is-asked-again

A merged acceptance is asked again

Lifecycle approvedImplementation completeVerification unknownQualification unknown

`verify` is outside the gate chain because it executes what a spec declares and a pull request is a stranger's code. Spec 089 built the sweep that re-asks the corpus's acceptance and made it maintainer-invoked, which leaves the window it was built to close open between runs: spec 092's block was red on `main` from #277 until #278 with every required check green, and no light turned. This spec runs the sweep where the trust boundary already allows it, on the default branch after a merge and nightly, scoped after a merge to the specs that own a changed path. It amends spec 089's "never CI" to "never on untrusted input", which is the rule that clause was written to hold.

Read the full pinned specification ↗

Relationships

Claimed units

  • establishes
    {
  "kind": "file",
  "path": ".github/workflows/acceptance.yml"
}
  • establishes
    {
  "kind": "file",
  "path": "scripts/acceptance-scope.sh"
}
  • extends
    {
  "nature": "additive",
  "spec": "089-nothing-reruns-a-merged-acceptance",
  "unit": {
    "kind": "file",
    "path": "scripts/verify-sweep.sh"
  }
}
  • extends
    {
  "nature": "additive",
  "spec": "094-one-gate-and-the-boundaries-it-holds",
  "unit": {
    "kind": "file",
    "path": "crates/spec-spine-core/tests/gate.rs"
  }
}

Source headings

  1. 099: A merged acceptance is asked again
  2. 1. Purpose
  3. 1.1 The window spec 089 left open
  4. 1.2 The boundary the "never CI" clause was protecting
  5. 1.3 Why this spec is its own witness
  6. 2. Territory
  7. 3. Behavior
  8. 3.1 Where it runs, and where it MUST NOT
  9. 3.2 The scope after a merge
  10. 3.3 The nightly leg sweeps the whole corpus
  11. 3.4 The decision about the token
  12. 3.5 The trusted ref is named, not inherited
  13. 3.6 Spec 089's acceptance line, corrected in place
  14. 3.7 What it does not do
  15. 4. Out of scope
  16. 5. Resolved decisions
  17. Verification

Frozen anchors

No frozen anchors declared.