089-nothing-reruns-a-merged-acceptance

Nothing reruns a merged acceptance

Lifecycle approvedImplementation completeVerification unknownQualification unknown

A `## Verification` block is run once, by the session that writes it, and then never again. `verify` is outside the gate chain on purpose, so a block that a later approved spec legitimately invalidates goes red silently and stays red: specs 084 through 110 each exist to repair one such block, and each was found by hand. Spec 083 §4 named the remedy, "a periodic sweep a maintainer runs, not a gate step", and left naming its home as its own work. This spec is that home. It establishes `scripts/verify-sweep.sh`, a maintainer-invoked sweep that runs the whole corpus's declared acceptance against one already-merged revision in an isolated worktree, accounts for every spec under five outcomes of which only two are success, and closes the 000-047 population as a ledger that can only shrink and that no future spec can enter.

Read the full pinned specification ↗

Relationships

Claimed units

  • establishes
    {
      "kind": "file",
      "path": "scripts/verify-sweep.sh"
    }
  • establishes
    {
      "kind": "file",
      "path": "scripts/test-verify-sweep.py"
    }
  • extends
    {
      "nature": "additive",
      "spec": "006-distribution",
      "unit": {
        "kind": "file",
        "path": "docs/releasing.md"
      }
    }

Source headings

  1. 089: Nothing reruns a merged acceptance
  2. 1. Purpose
  3. 1.1 The gap, in the corpus's own record
  4. 1.2 What the corpus declares today, measured
  5. 1.3 Why this is not `verify --all`
  6. 1.4 The first run, measured
  7. 2. Territory
  8. 3. Behavior
  9. 3.1 Where it lives and who runs it
  10. 3.2 It runs the existing mechanism, unchanged
  11. 3.3 Five outcomes, and only two of them are success
  12. 3.4 The 000-047 population: a closed ledger that only shrinks
  13. 3.5 Selection
  14. 3.6 Isolation, fixtures, and what happens after a failure
  15. 3.7 The trust boundary is preserved and made mechanical
  16. 3.8 The report is the evidence
  17. 3.9 When a maintainer runs it
  18. 4. Out of scope
  19. 5. Resolved decisions
  20. Implementation review (2026-09-17)
  21. Verification

Frozen anchors

No frozen anchors declared.