---
template: release-spec/1
id: RS-NNN            # RS-NNN or the release version (v1.2.0); never reused
title: Release spec — [release name]
status: draft         # draft | review | approved | released — the lead approves; the owner when scope or appetite changes
version: 0.1.0        # version of this release spec; a change of scope or appetite makes a new revision
tier: standard        # lightweight | standard | high-assurance, as set at G0 (mgmt.governance-tiers)
appetite: 3 agent-days # the time the owner will give this release; scope bends, time does not
approver: [lead; owner or client when the rules require it]
prd: project/PRD.md@0.1.0             # the PRD version this release builds on
blueprint: project/BLUEPRINT.md@0.1.0 # the Blueprint version this release builds on
date: YYYY-MM-DD
---

# Release spec — [release name]

<!-- Template from the UASK Engineering Hub, item process.release-spec.
     Save as project/specs/RS-NNN.md (or beside the release plan). Write it before Build starts and get it
     approved at gate G2. Sections that need a tier say so in their first line; a section that does not apply
     says "none" and stays. Delete these comments when a section is written. -->

## 1. Context and scope

<!-- Why this release comes now, and what it builds on: the previous release, the pitch, the open findings.
     Two to five sentences. -->

## 2. Goals and non-goals

<!-- Goals are requirement ids from the PRD that this release delivers. Out of scope lists ids that are
     explicitly not delivered. Non-goals are things that could be goals but are not. -->

| ID | Requirement | Why in this release |
|---|---|---|
| FR-1 | … | … |

Out of scope: [ids, each with where it goes instead, for example "FR-n → next release"].

Non-goals:

- …

## 3. Design

<!-- Which sections of the Blueprint change, by number; which interfaces and contracts change; every data
     migration. A hard-to-reverse choice becomes an ADR, linked here. -->

- Blueprint changes: [§5 gets a new component …]
- Interfaces and contracts: [none | list]
- Data migrations: [none | list, with whether each can be reversed]

## 4. Alternatives considered

<!-- Required: standard, high-assurance -->
<!-- Options that were rejected, and why. Each hard-to-reverse choice is an ADR; name it in the last column. -->

| Option | Why not | ADR |
|---|---|---|
| … | … | — |

## 5. Cross-cutting impact

<!-- Required: standard, high-assurance -->
<!-- Only what this release changes: security, privacy, performance, accessibility, observability. -->

| Concern | What changes | How it is checked |
|---|---|---|
| Security | none | — |

## 6. Acceptance and verification

<!-- Each criterion has a method, an environment and an expected result (see the acceptance criteria item).
     Write the check first and see it fail before the code is written. Name the evidence the verifier will ask for. -->

| Criterion | Check to add first (red before green) | Evidence expected |
|---|---|---|
| AC-1 | … | test output, a screenshot, a log line |

## 7. Rollout and rollback

<!-- Write the rollback first. For a live system, name the backup that was proved by restore, and where it is kept
     (the backup rule of the project lifecycle item). Fill in the release checklist from this section. -->

- Backup proved by restore: [what, where, when, how restored]
- Window and who can roll back during it: […]

| Step | Action | How it is undone | Time to undo |
|---|---|---|---|
| 1 | … | … | … |

## 8. Work packages

<!-- One package is the unit one builder takes: a goal, the files it touches, a Done criterion that someone else can
     check, an estimate. The total is compared with the appetite; if it is above, cut scope. -->

| WP | Goal | Files | Done criterion | Estimate |
|---|---|---|---|---|
| WP-1 | … | … | … | 0.5 agent-day |

Total: [n] against an appetite of [n].

## 9. Risks and rabbit holes

<!-- Required: standard, high-assurance -->
<!-- What could exceed the appetite, and the circuit breaker: when the appetite is reached with the work
     unfinished, the lead stops and puts the options and a default to the owner. -->

| Risk or rabbit hole | Likelihood and impact | Mitigation |
|---|---|---|
| … | … | … |

Circuit breaker: [when the appetite is reached, the lead stops and asks the owner; the default is …]

## 10. Open questions

<!-- Each question has a default that applies if nobody answers by the given date. -->

| Question | Default | Who answers | By |
|---|---|---|---|
| … | … | … | … |

## Close-out

<!-- Optional. Fill in when the release ships: link the release record and compare actual with appetite. -->

- Release record: […]
- Actual effort against appetite: […]
