121-the-acceptance-workflow-judges-what-was-built

The Acceptance workflow judges what was built

Lifecycle approvedImplementation completeVerification unknownQualification unknown

The nightly `Acceptance` leg exits on the sweep's corpus verdict, so it is red for as long as any draft is filed ahead of its build, which is this repository's normal state. A signal that is always red cannot tell a reader that an implemented spec's acceptance just broke. Spec 119 built the release verdict and left the workflow's choice open. This spec takes it: both legs exit on the release verdict, the full selected corpus still runs, and a new report step puts both verdicts, every release failure and every pending block's real outcome into the run's summary and annotations. A missing, unreadable or inconsistent report fails the job on its own.

Read the full pinned specification ↗

Relationships

depends on

Claimed units

establishes

{
  "kind": "file",
  "path": "scripts/acceptance-report.py"
}

extends

{
  "nature": "corrective",
  "spec": "099-a-merged-acceptance-is-asked-again",
  "unit": {
    "kind": "file",
    "path": ".github/workflows/acceptance.yml"
  }
}

extends

{
  "nature": "additive",
  "spec": "089-nothing-reruns-a-merged-acceptance",
  "unit": {
    "kind": "file",
    "path": "scripts/test-verify-sweep.py"
  }
}

Source headings

121: The Acceptance workflow judges what was built
1. Purpose
1.1 A signal that is always red
1.2 What spec 119 left open
2. Territory
3. Behavior
3.1 Both legs exit on the release verdict
3.2 A report step that cannot be skipped by a red sweep
3.3 What the report step renders
3.4 The report step refuses what it cannot vouch for
3.5 The regressions
3.6 What does not change
4. Out of scope
5. Resolved decisions
Verification

Frozen anchors

No frozen anchors declared.