statecraft.
Catalog/spec-spine

119-a-release-verdict-judges-what-was-built

A release verdict judges what was built

Lifecycle approvedImplementation completeVerification unknownQualification unknown

The whole-corpus sweep (spec 089) runs every declared acceptance block and exits 1 when any fails. This repository files a spec's acceptance before the spec is built and writes it to fail first, so any filed-but-unbuilt draft keeps the sweep red. "Sweep green" as a release pre-flight is then unreachable for as long as the backlog is honest. The sweep had no lifecycle predicate, and the only ways to get a green run were to build unrequested features or to hide the failures. This spec adds a release verdict next to the corpus verdict. It is judged over the specs whose implementation is built, with pending work run, listed with its real outcome and never counted as success or exemption, and `--release` puts it in the exit code. The corpus verdict and its exit code are unchanged. It also moves the default run directory out of the macOS temporary tree, whose daily purge is the inferred cause of a run in which 26 blocks failed that had not, and makes that directory new per run, so a rerun cannot clear the evidence of the run before it.

Read the full pinned specification ↗

Relationships

Claimed units

  • extends
    {
  "nature": "corrective",
  "spec": "089-nothing-reruns-a-merged-acceptance",
  "unit": {
    "kind": "file",
    "path": "scripts/verify-sweep.sh"
  }
}
  • extends
    {
  "nature": "corrective",
  "spec": "089-nothing-reruns-a-merged-acceptance",
  "unit": {
    "kind": "file",
    "path": "scripts/test-verify-sweep.py"
  }
}
  • extends
    {
  "nature": "additive",
  "spec": "006-distribution",
  "unit": {
    "kind": "file",
    "path": "docs/releasing.md"
  }
}

Source headings

  1. 119: A release verdict judges what was built
  2. 1. Purpose
  3. 1.1 "Sweep green" was unreachable, measured
  4. 1.2 A run that failed for a reason outside the corpus
  5. 1.3 The owner's ruling
  6. 2. Territory
  7. 3. Behavior
  8. 3.1 The lifecycle is a governed read
  9. 3.2 The release outcome
  10. 3.3 Two verdicts, one exit code
  11. 3.4 The report is versioned, and the change is additive
  12. 3.5 The default run directory
  13. 3.6 The regressions run, and they cannot rot silently again
  14. 3.7 The runbook reads the release verdict
  15. 3.8 What does not change
  16. 4. Out of scope
  17. 5. Resolved decisions
  18. Verification

Frozen anchors

No frozen anchors declared.