Skip to content

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

Status: draft · Version 0.1.0

Update and lifecycle

Summary

Version: 0.1

Method for SCF-LCM, SCF-UPD and the release-facing parts of SCF-VUL and SCF-ART. The Constitution states what must hold. This document states how it is done and how it is checked. It introduces no new obligations; where it says MUST, it is giving the method by which an existing requirement is met.

Rules

1. Principle

A recipient of a system must be able to answer four questions without asking the producer:

  • what exactly do I have;
  • what changed since what I had before;
  • what am I promised about it, and until when;
  • how do I get the next thing, and how do I go back.

A version string that answers none of these is decoration. SCF-LCM-001 requires version identity to distinguish the specification, the release and the channel; sections 2 to 5 are the method for that requirement.

2. Three identities, not one

Axis Identity Audience Established by
Specification spec_id, lock_id — content addresses machines, rebuilds, deduplication the construction pipeline
Release a human version, section 3 people, contracts, support records the release gate
Channel a named suite, section 5 clients fetching updates publication

The three MUST NOT be conflated. Two releases may share a spec_id and differ in channel. A release MUST carry all three, and every artefact MUST be resolvable to its lock_id.

3. Release version

3.1 Form

<MAJOR>.<MINOR>.<FIX>

Semantically shaped like a familiar three-part version, but the meanings are those of an operating system, not of a library API.

Component Increments when Guarantees to the recipient
MAJOR the update contract changes, or the upstream base changes in-place update MAY be unavailable. A migration path MUST be published before release (SCF-LCM-005)
MINOR declared capability changes: components added or removed, a profile obligation changes, a default changes in-place update within the channel MUST work and MUST be tested
FIX a fixpack: security and defect corrections only no change to declared behaviour, interfaces, defaults or configuration. Applying it MUST NOT require any action by the operator

A fixpack MAY change the versions of packages it contains — that is what a security fix is. What it MUST NOT change is anything the product has declared. This is the distinction that a library-oriented scheme loses, and it is the distinction an operator actually needs.

3.2 The base is declared, not encoded

The upstream base MUST be stated alongside the version and MUST NOT be encoded into it. Encoding the base into the version couples the product to another project’s numbering and breaks when a second base is added.

3.3 Required identity on the system

/etc/os-release MUST allow a running system to be resolved to its release record:

NAME="<product>"
VERSION="<MAJOR>.<MINOR>.<FIX>"
VERSION_ID="<MAJOR>.<MINOR>.<FIX>"
BUILD_ID="<ISO-8601 build date>"
<PRODUCT>_BASE="<upstream id, e.g. debian-13>"
<PRODUCT>_LOCK="sha256:<lock_id>"
<PRODUCT>_CHANNEL="<suite>"
<PRODUCT>_SUPPORT_END="<YYYY-MM, or an explicit statement that there is none>"

A system that cannot state its own lock_id cannot be rebuilt from its own record, and fails SCF-REP-001 in practice regardless of what the pipeline can do.

The support field discharges SCF-LCM-004 on the machine itself: a recipient must be able to ask the system how long it is supported without approaching the producer. Where no support is offered, the field MUST say so rather than be absent — an absent field reads as an omission, and an omission reads as a promise.

3.4 Pre-release and build metadata

Pre-release qualifiers (-beta.N, -rc.N) MAY be appended and MUST be removed on promotion to a supported channel. Build metadata MUST NOT be used to distinguish releases: two artefacts that differ in anything a recipient can observe are different releases.

4. Fixpacks

4.1 What a fixpack is

A fixpack is a cumulative release within a function level. It MUST be cumulative: a recipient applying fixpack n MUST NOT be required to have applied n−1. Non-cumulative fixes produce combinations the producer has never tested, which is the failure the practice exists to avoid.

4.2 Contents

A fixpack MUST contain only:

  • corrections for published security advisories;
  • corrections for recorded defects;
  • changes required for the above to apply cleanly.

Anything else belongs to a MINOR release. A fixpack that quietly adds capability destroys the guarantee in section 3.1 and MUST NOT be issued.

Where individual fixes are published between fixpacks, the producer SHOULD publish a periodic set that has been tested together and is recommended as a whole. “Apply everything available” is not a tested configuration, and a recipient who does so is running a combination nobody has verified.

5. Channels

Each channel MUST have documented promotion criteria, a named owner, an audit trail and a demotion path (SCF-LCM-002).

Suite Contains Promotion into it Demotion
<release> the supported release as published release gate passed (SCF-EVD-005) none; a release is immutable (SCF-ART-005)
<release>-security security corrections only advisory published, fix verified withdrawal with a superseding advisory
<release>-updates non-security corrections accepted between fixpacks defect recorded, fix verified withdrawal with a superseding advisory
<release>-proposed candidates for the two above build passed automated checks dropped without notice
beta candidate releases function complete, gate not yet passed dropped without notice

5.1 Security updates MUST be separable at the client

SCF-UPD-003 requires security updates to be separable. Separability is a property of the published metadata, not of intent. The producer MUST publish repository metadata that allows an unmodified client to classify an update as a security update without consulting the producer.

For deb archives this means the security suite MUST be published with distinguishing archive metadata — a distinct Suite/Codename and a Label a client can match — and the producer MUST verify the classification against the client it ships, on a clean installation, before declaring the requirement met.

Known failure mode, observed in practice. Clients derived from common update managers classify a security update by matching the origin and label of the upstream distribution. A product publishing under its own Origin and Label will have every update classified as ordinary, including critical ones, while every published document claims security updates are separable. Where the producer ships the client as well, both ends MUST be corrected: the archive MUST carry distinguishing metadata, and the client MUST NOT hard-code the identity of a single upstream.

5.2 Verification

Classification MUST be verified at evidence level E3 or above (see EVALUATION.md): a clean installation, an update published to the security suite, and the shipped client observed to classify it correctly and to offer it under a security-only selection. Reading the archive configuration is E2 evidence about the archive, not evidence about the client.

6. Advisories and defect records

6.1 Identifiers

<PRODUCT>-SA-<YYYY>-<NNNN> security advisory
<PRODUCT>-BA-<YYYY>-<NNNN> defect advisory
<PRODUCT>-EA-<YYYY>-<NNNN> enhancement advisory
<PRODUCT>-D-<YYYY>-<NNNN> defect record

Identifiers MUST NOT be reused and MUST remain resolvable after end of life.

6.2 The defect record exists before the fix

A defect record is separate from the advisory that corrects it. It MUST be created when a defect is accepted, which is before a correction exists. This is what allows the producer to acknowledge a reported problem, state a workaround and carry a status, without waiting to have a fix — and it is what SCF-VUL-001 and SCF-VUL-002 require in practice.

For reported vulnerabilities a defect record MUST be created on acceptance. Where an external identifier exists it MUST be cross-referenced, not replaced.

6.3 Severity

The producer MUST publish a written severity scale with definitions, and MUST assign a severity to every security advisory. A score taken from an external calculator is not a severity scale: the scale states what the producer will do at each level and how quickly.

Advisories MUST be machine-readable in a published format, per SCF-VUL-004.

7. Support lifecycle

7.1 Phases

Phase The producer supplies The producer does not supply
Full support security corrections, defect corrections, hardware enablement within the declared matrix —
Maintenance security corrections only defect corrections, hardware enablement, capability
Ended artefacts, verification material and source remain retrievable corrections of any kind

Transitions MUST occur on announced dates, not on the availability of a successor. A release leaving support MUST NOT be withdrawn: source and verification material must remain available for the period the licences require (SCF-LGL-003, SCF-ART-007).

7.2 Declaration

Support dates MUST be stated before acquisition (SCF-GOV-004), to month-and-year precision, and MUST be reachable from the system itself (SCF-LCM-004). Where support is contractual, the contract is where the declaration is made, and the release record carries it; where an artefact is published without a contract, the statement accompanies the artefact at the point of download. Where no support is offered, that MUST be stated plainly.

The producer’s support period cannot exceed the upstream base’s, unless extended support is separately agreed and the producer has accepted the work of backporting. A commitment that outlives its base is a commitment to unbounded work. Silence about a support period is read as a promise, and an unstated promise is a claim without evidence (SCF-GOV-006).

7.3 Freshness

SCF-LCM-003 requires the producer to know how far behind a release is. Method: re-resolve the specification on a schedule and compare the resulting lock_id with the released one. A difference is the definition of “behind”, and it is measurable without inspecting any system.

8. Branches in the construction repository

SCF-BLD-009 places the construction platform in scope, so its branching is a property of the product and MUST be documented.

Branch Purpose Rule
main trunk MUST be buildable at every commit
release/<MAJOR>.<MINOR> a supported function level created at the first release of that level; fixpacks are cut from it; receives only what section 4.2 permits
fix/<identifier> work on a recorded defect named for the defect record or advisory it serves
feat/<short-name> work on capability merges to main, never to a release branch

Releases MUST be tagged, and the tag MUST be the release version. A corrective change that applies to both a release branch and the trunk MUST be applied to the trunk as well; a fix that exists only in a release branch reappears in the next function level.

9. Conformance checklist

# Check Level
1 Release carries specification, release and channel identity E2
2 /etc/os-release resolves the system to its lock_id E2
3 Fixpack contains only permitted changes E2
4 Fixpack is cumulative E3
5 In-place update within a function level works E3
6 Security update is classified as such by the shipped client E3
7 Rollback returns a reference installation to service E4
8 Every channel has stated criteria, owner, audit trail, demotion path E1
9 Severity scale published; every security advisory carries a severity E1
10 Defect record exists from acceptance, not from correction E1
11 Support dates published before acquisition and reachable from the system E2
12 Freshness measurable by re-resolution E2

10. Known gaps in this document

Recorded rather than left implicit, per SCF-GOV-006.

  • No method is given for atomic or image-based update models; the text assumes a package-based update path. Immutable profiles need their own section.
  • Interface stability levels are not addressed anywhere in the corpus. A system whose derivatives inherit behaviour needs a declared obligation level per interface, in the manner of a published interface taxonomy. This is a gap in the Constitution, not only here.