Skip to content

Draft — not approved. A working draft by UASK. It may change without notice.

Status: draft · Version 0.1.0

Release record template

Version: 0.1

The controlled record of one release: its inputs, its evidence, its exceptions and its approval. Required by SCF-EVD-004, which also requires it to be retained for the support period.

The sections follow the twelve steps of the release gate in EVALUATION.md §7, in order. A gate step with no section filled is a gate step not performed.

The product profile (PRODUCT_PROFILE_TEMPLATE.md) says what is claimed. This record says what was done to earn the claim. Neither replaces the other.


How to use this

One record per release, including fixpacks. Written before the release is signed, not reconstructed afterwards: a record assembled after the fact records what was remembered, not what happened.

Most of it should be generated by the pipeline. Fields a human must fill are marked (human) — and they are exactly the fields a pipeline cannot honestly produce.


1. Identity

Field Value
Product
Release version > MAJOR.MINOR.FIX per UPDATE_AND_LIFECYCLE.md §3
Kind > function release or fixpack
spec_id
lock_id
Channel published to
Upstream base
Build date > ISO 8601
Architectures
Supersedes > previous release in this function level

2. Scope of change — gate 1

(human)

What changed and why. For a fixpack, UPDATE_AND_LIFECYCLE.md §4.2 limits the contents to security corrections, defect corrections and what is needed for them to apply: if anything else is listed here, this is a MINOR release and the version is wrong.

Summary
Advisories included > <PRODUCT>-SA-…, -BA-…
Defect records closed
Profiles affected
Interfaces affected > and whether any declared behaviour changed

3. Inputs — gate 2

Lock complete > yes / no
Every input authenticated > signatures verified against declared trust anchors (SCF-SRC-002, SCF-SRC-003)
Archive state pinned > snapshot or equivalent (SCF-SRC-004)
Toolchain versions pinned
SOURCE_DATE_EPOCH
Source retained > where, and for how long (SCF-SRC-005, SCF-ART-007)

4. Build — gate 3

Boundary > what isolated the build, per SCF-BLD-002
Network during build > policy actually enforced, not intended
Build log retained at > resolvable location (SCF-BLD-008)
Builder image digest

5. Artefacts — gate 5

Artefact Digest Signature Notes
Manifest > location (SCF-ART-001)
Bill of materials > format and location (SCF-ART-002)
Provenance attestation > (SCF-ART-003)
Verification instructions > shipped with the artefact (SCF-ART-006)
Source bundle > (SCF-ART-007)

6. Verification

6.1 Offline checks — gate 4

Run on every build and capable of failing it (SCF-EVD-002). Licence, trademark and vulnerability checks are named explicitly by the gate.

Check Result Evidence

6.2 Boot chain currency — gate 6

Revocation policy generation > current? (SCF-BOOT-004)
Secure Boot status > honestly stated, including “not supported” (SCF-BOOT-002)

6.3 Emulated verification — gate 7

Scenario Result Evidence Level
E3

6.4 Reference hardware — gate 8

Mandatory scenarios: boot, update, rollback, recovery, storage encryption unlock.

Scenario Hardware Result Evidence Level
E4

SCF-EVD-003: properties depending on firmware, secure boot, measurement, storage encryption or hardware MUST be verified where those facilities exist. An emulated pass does not substitute.

6.5 Accessibility — gate 9

HIF profile Checks Result Evidence

6.6 Security update classification

Required by SCF-UPD-003 and UPDATE_AND_LIFECYCLE.md §5.2: verified against the client actually shipped, on a clean installation, at E3 or above. Reading the archive configuration is evidence about the archive, not about the client.

Client tested
Classified correctly > yes / no
Offered under security-only selection > yes / no
Evidence

7. Lifecycle — gate 10

Support period > start and end dates, per phase (UPDATE_AND_LIFECYCLE.md §7)
Channel
End-of-life date
Published where > reachable before acquisition (SCF-GOV-004) and from the system (SCF-LCM-004)

8. Exceptions open at release — gate 11

Each MUST have an owner and an unexpired review date. An expired exception blocks the conformance statement.

ID Requirement Owner Review date Compensating control

9. Rollback and withdrawal

(human)

Part of the gate, not a later decision (EVALUATION.md §7).

Rollback plan > how a machine on this release returns to the previous one
Rollback tested > evidence, E4 (SCF-UPD-006)
Withdrawal criteria > what would make us pull this release
Withdrawal procedure > including the superseding advisory

10. Approval — gate 12

(human)

Approver > named person (SCF-EVD-005)
Role
Date
Statement > that every gate step above is satisfied or covered by a registered exception

11. Retention

Record retained at
Retained until > end of support period, at minimum (SCF-EVD-004)
Source retained until > per licence obligations (SCF-LGL-003)

12. Common failures

Failure Why it is a failure
Record written after the release records recollection, not events; the gate was not a gate
Gate step left blank rather than marked failed a blank reads as “not applicable” and hides the omission
Reference-hardware section filled from emulation the single most consequential falsification available here
Rollback plan present, rollback untested the plan is the easy half
“Security update classification: not tested” then SCF-UPD-003 is not met, and the profile must carry an exception
Exceptions copied forward release to release the register stops being a plan and becomes a habit