Skip to content

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

Change policy

Status
Draft
Version
0.1.0
Authority
UASK standard
Applies to
operating-system
Markdown source

Summary

Version: 0.1

This part states how the System Construction Framework (SCF) changes after version 1.0.0: what a consumer that pins a version may rely on, which changes need a MAJOR, MINOR or PATCH version, how rule identifiers are kept, how a rule is deprecated and withdrawn, how often the corpus is reviewed and how a change is recorded.

The rules of this part bind the maintainers of SCF. They are not requirements on a product, are not part of any profile and are not applicable to the release of a product (SCF-EVL-009).

The classes MAJOR, MINOR and PATCH here are the classes of change to SCF. The version of a product built with SCF has its own form, MAJOR.MINOR.FIX, set by Update and lifecycle §3.

Status: draft, proposed. The policy takes effect with SCF 1.0.0, and only after the decision record ADR-0010 that proposes it has been accepted by the Product Owner. Until then versions below 1.0.0 are initial development (SCF-CHG-003). Terms are defined in the glossary.

Rules

1. Public interface

SCF-CHG-001. Public interface

The public interface of SCF MUST consist of exactly the following, and a consumer that pins a version MAY rely on these and on nothing else:

  1. the rule identifiers and the obligation each rule states;
  2. the identifiers of the checks of Evaluation section 3 — the baseline verification corpus and the reference checks — and their expected results;
  3. the evidence levels E0 to E5 and the conformance levels SCF-Declared, SCF-Conformant and SCF-Validated;
  4. the fields of the conformance statement and of the release record, and the twelve steps of the release gate;
  5. the adapter contract: its operations and its invariants;
  6. the front-matter fields that consumers read: id, version, status and rule_prefix, where the version of the index document is the version of SCF (SCF-CHG-018).
  • Rationale. A consumer cannot judge whether a new version is safe to adopt unless the things it depends on are named; a version number without a declared interface protects nothing.
  • Source. SemVer 2.0.0, item 1 (a public API is declared) and item 5 (1.0.0 defines it), accessed 2026-11-21.
  • Applies. The maintainers of SCF.
  • Verification. E1 — review of the list against the corpus at each release. Item 1 covers the identifiers of the profile rules, item 2 the check identifiers and item 5 the adapter contract, as the corpus defines them. Checks: SCF-CHK-303.

SCF-CHG-002. Informative material

Material outside the public interface — the knowledge base, the platform dossiers, worked examples and guidance — is informative. It MAY change in a MINOR or PATCH release and MUST NOT create an obligation.

  • Rationale. Facts about named platforms and teaching material age faster than obligations; keeping them outside the interface lets them stay current without a MAJOR version, provided they cannot bind anyone.
  • Source. Decision, owner Product Owner (ADR-0010, proposed); the split between normative and informative text follows WCAG 2.2, whose techniques are informative and not required for conformance, accessed 2026-11-21.
  • Applies. The maintainers of SCF.
  • Verification. E1 — review of the change record and of each added sentence that carries a normative word; E2 — a report of such sentences outside rules (mechanical, not yet automated: backlog B-25). Checks: SCF-CHK-304.

2. Versions before 1.0.0

SCF-CHG-003. Initial development

Versions below 1.0.0 are initial development. Any part of SCF MAY change in any such release, and the rules of this part take effect with version 1.0.0.

  • Rationale. The corpus is being brought to a stable scope; promising compatibility before the scope is frozen would promise what cannot be kept.
  • Source. SemVer 2.0.0, item 4 (major version zero is for initial development), accessed 2026-11-21.
  • Applies. The maintainers of SCF.
  • Verification. E1 — the version of the release is read against this rule. Checks: SCF-CHK-305.

3. Classes of change

SCF-CHG-004. MAJOR change

A change MUST be released as a MAJOR version if, after it, a product that conformed could stop conforming, or if it removes or renames an element of the public interface. Changes after which a product could stop conforming include: adding a MUST or strengthening one, widening the Applies line of a mandatory rule, redefining a term on which a mandatory rule depends, tightening the expected result of a check, and redefining a conformance level. Changes that remove or rename an element of the public interface include withdrawing a rule, which removes its obligation, and renaming an identifier or a field.

  • Rationale. A pin protects a consumer only if no change that can break a conforming product, or take away something the consumer relies on, arrives under a version that promises neither.
  • Source. SemVer 2.0.0, item 8 (a backward incompatible change to the public API is a MAJOR change), accessed 2026-11-21.
  • Applies. The maintainers of SCF.
  • Verification. E1 — each change in the change record is classified, and the class is reviewed; E2 — the rule identifiers and normative words of the release are compared with those of the previous release (mechanical; python3 tools/rule_register.py scf, run on the release and on the previous release, lists the identifiers and levels to compare by hand; no script compares them yet: backlog B-25). Checks: SCF-CHK-306.

SCF-CHG-005. MINOR change

A change that adds to SCF or relaxes it, after which no product that conformed can fail and that removes or renames no element of the public interface, MUST be released as a MINOR version, or as a MAJOR version where the same release carries a MAJOR change (SCF-CHG-007). Such changes are: adding a SHOULD or a MAY, adding a profile, adding an informative or guidance document, adding a check for an existing rule that cannot fail a conforming product, relaxing an obligation, and marking a rule deprecated. A product that makes a new conformance statement after a SHOULD is added meets it or registers an exception (SCF-EVL-012); the statement it made before is not voided (SCF-CHG-020).

  • Rationale. Additions are what a living standard needs to grow; they must be visible to a consumer, who may want to adopt them, without being mistaken for a correction.
  • Source. SemVer 2.0.0, item 7 (backward compatible new functionality, and deprecation, are MINOR), accessed 2026-11-21.
  • Applies. The maintainers of SCF.
  • Verification. E1 — as for SCF-CHG-004. Checks: SCF-CHK-307.

SCF-CHG-006. PATCH change

A change that alters no obligation and no element of the public interface — a typographical correction, a clarification that does not change what is required, a repaired link, a refresh of a dated platform fact — MAY be released as a PATCH version.

  • Rationale. Corrections that cannot affect conformance should reach consumers without asking them to review anything.
  • Source. SemVer 2.0.0, item 6 (backward compatible fixes are PATCH), accessed 2026-11-21.
  • Applies. The maintainers of SCF.
  • Verification. E1 — as for SCF-CHG-004. Checks: SCF-CHK-308.

SCF-CHG-007. Highest class

A release that contains changes of more than one class MUST carry the version of the highest class among them.

  • Rationale. The version states the worst case a consumer has to review.
  • Source. SemVer 2.0.0, item 8 (a MAJOR release may also include minor and patch changes), accessed 2026-11-21.
  • Applies. The maintainers of SCF.
  • Verification. E1 — as for SCF-CHG-004. Checks: SCF-CHK-309.

SCF-CHG-008. Doubt

A change whose class is in doubt MUST be given the higher of the classes in doubt.

  • Rationale. Understating a change costs a consumer a surprise; overstating it costs a review.
  • Source. Decision, owner Product Owner (ADR-0010, proposed).
  • Applies. The maintainers of SCF.
  • Verification. E1 — the reviewer of the release records any change on which the class was disputed and the class chosen. Checks: SCF-CHK-310.

4. Rule identifiers

SCF-CHG-009. Identifiers are kept

A rule identifier MUST NOT be reused for another obligation and MUST NOT be renumbered. When a rule is split (SCF-CHG-011), its identifier stays with the first obligation, which is a part of the obligation the identifier stated before; that is not a change of meaning.

  • Rationale. Consumers cite rule identifiers in their own documents and checks; a changed meaning behind a cited identifier is a silent break.
  • Source. Decision, owner Product Owner (ADR-0010, proposed). In the audit of the plan to version 1.0 (2026-11-21) a consumer cited 75 of the 149 identifiers that existed then in its own documents; the count has not been repeated since, and SCF 0.1.0 now has more.
  • Applies. The maintainers of SCF.
  • Verification. E2 — the set of rule identifiers of the release is compared with that of the previous release, and no identifier is missing (mechanical; the output of python3 tools/rule_register.py scf, run on the release and on the previous release, is compared by hand; no script compares it yet: backlog B-25); E1 — the statement of each identifier present in both is read for a change of meaning, except an identifier recorded as split under SCF-CHG-011. Checks: SCF-CHK-311.

SCF-CHG-010. Withdrawn identifiers

A withdrawn rule MUST remain in its document as a stub that keeps the identifier and states when and why the rule was withdrawn.

  • Rationale. A reader following an old citation must find an explanation, not a missing page.
  • Source. Decision, owner Product Owner (ADR-0010, proposed).
  • Applies. The maintainers of SCF.
  • Verification. E2 — every identifier of the previous release is present in the release (as for SCF-CHG-009); E1 — each stub names the date and the reason. Checks: SCF-CHK-312.

SCF-CHG-011. Splitting a rule

When a rule is split, the first obligation MUST keep the identifier of the rule and each new obligation MUST take the next free number in the group of the rule.

  • Rationale. A rule that states several obligations becomes testable only when it is split; keeping the first identifier and appending the rest means no existing citation is renumbered.
  • Source. Decision, owner Product Owner (ADR-0010, proposed).
  • Applies. The maintainers of SCF.
  • Verification. E2 — as for SCF-CHG-009; E1 — the change record names each new identifier and the rule it was split from. Checks: SCF-CHK-313.

5. Deprecation and withdrawal

SCF-CHG-012. Deprecation window

A rule MUST be marked deprecated before it is withdrawn, and a deprecated rule MUST stay in force for at least 12 months and for at least one further MINOR release after the release of SCF that marks it. A rule whose presence is itself a security or legal defect in SCF MAY be marked deprecated and withdrawn in the same MAJOR release, which SCF-CHG-015 permits within the 12 months, with the migration note of SCF-CHG-014.

  • Rationale. A consumer needs time and a visible warning to adapt before an obligation disappears; a rule that is itself the defect cannot be left in force for a year.
  • Source. Decision, owner Product Owner (ADR-0010, proposed); informed by the Carbon Design System, in which a deprecated asset stays through its major version and is removed in the next with a migration guide, accessed 2026-11-21.
  • Applies. The maintainers of SCF.
  • Verification. E1 — the dates and versions in the change record are read against this rule when a rule is withdrawn. Checks: SCF-CHK-314.

SCF-CHG-013. Withdrawal only in a MAJOR release

A deprecated rule MUST be withdrawn only in a MAJOR release.

  • Rationale. Withdrawing an obligation changes what conformance means (SCF-CHG-004).
  • Source. SemVer 2.0.0, item 8, accessed 2026-11-21.
  • Applies. The maintainers of SCF.
  • Verification. E1 — as for SCF-CHG-012. Checks: SCF-CHK-315.

SCF-CHG-014. Migration note

A release that withdraws a rule MUST carry a migration note that says what a product that met the rule does now.

  • Rationale. A withdrawal may leave a product with work to remove or with a gap to fill; the note says which.
  • Source. Decision, owner Product Owner (ADR-0010, proposed).
  • Applies. The maintainers of SCF.
  • Verification. E1 — the note is present in the change record and in the stub of SCF-CHG-010. Checks: SCF-CHK-316.

6. Cadence and review

SCF-CHG-015. Cadence of MAJOR releases

A MAJOR release of SCF MUST NOT be made less than 12 months after the previous MAJOR release, except for a correction that closes a security or legal defect in SCF.

  • Rationale. Consumers plan upgrades and need a predictable rhythm; a defect that harms them is the one reason to break it.
  • Source. Decision, owner Product Owner (ADR-0010, proposed).
  • Applies. The maintainers of SCF.
  • Verification. E1 — the dates of the releases are read against this rule; an exception names the defect. Checks: SCF-CHK-317.

SCF-CHG-016. Review of the corpus

Every document of SCF MUST be reviewed at least every 12 months, and its review date and interval MUST be recorded in its front matter as last_reviewed and review_every.

  • Rationale. Statements about platforms, regulation and practice age; an interval with a recorded date makes staleness visible.
  • Source. Decision, owner Product Owner (ADR-0010, proposed).
  • Applies. The maintainers of SCF.
  • Verification. E2 — the lifecycle check of the validator warns about a document whose review date plus interval has passed. Checks: SCF-CHK-318.

SCF-CHG-017. Review of external facts

The regulation, signing-authority policy, platform rules, upstream support periods and end-of-life dates, hardening baselines, algorithm policy, and upstream trademark and licence terms on which SCF depends MUST be reviewed before related work and at least annually.

  • Rationale. These change outside SCF and without notice to it; an obligation that rests on a superseded fact misleads.
  • Source. Decision, owner Product Owner. Carried over without change from the overview and the knowledge base of version 0.1.0.
  • Applies. The maintainers of SCF.
  • Verification. E1 — the change record of each release lists what was re-read and when. Checks: SCF-CHK-319.

7. Versions, claims and records

SCF-CHG-018. Version of the standard

The version of SCF MUST be the version of its index document, and every release of SCF that changes any document of SCF MUST raise it.

  • Rationale. A conformance statement names one number; that number has to be the same wherever it is read.
  • Source. Decision, owner Product Owner (ADR-0010, proposed).
  • Applies. The maintainers of SCF.
  • Verification. E1 — the version of the index is compared with that of the previous release whenever any document differs. Checks: SCF-CHK-320.

SCF-CHG-019. Version of a document

Every document of SCF MUST state a version or inherit the version of the standard.

  • Rationale. A reader of one document must be able to tell which edition of the standard it belongs to.
  • Source. Decision, owner Product Owner. Carried over without change from the knowledge base of version 0.1.0.
  • Applies. The maintainers of SCF.
  • Verification. E1 — review of the front matter of every document at each release. Checks: SCF-CHK-321.

SCF-CHG-020. Earlier conformance statements

A later release of SCF MUST NOT void a conformance statement made against an earlier version; the statement is judged against the SCF version it names.

  • Rationale. The producer of a product cannot re-run its evidence whenever the standard moves; the statement is bounded by the version and the release it names.
  • Source. Decision, owner Product Owner (ADR-0010, proposed). The obligation to name the SCF version is in Evaluation and conformance §5 and is not repeated here.
  • Applies. The maintainers of SCF.
  • Verification. E1 — review of each release for text that applies a new requirement to a statement made earlier. Checks: SCF-CHK-322.

SCF-CHG-021. Change record

Each change after 1.0.0 MUST be listed in the change record of the document it changes, with its version and class, the changed statement, the reason and evidence, the affected profiles and checks, the migration impact, the reviewer and the date. The change record of a document is the table of that name at its end, newest entry first; the change record of a release is the set of the entries that carry its version in the change records of the documents it changes.

  • Rationale. The reader of a diff sees what changed; the record says why, who agreed and what it means for a product.
  • Source. Decision, owner Product Owner. Carried over from the change-management text of the overview and the knowledge base of version 0.1.0, which this rule replaces.
  • Applies. The maintainers of SCF.
  • Verification. E1 — each change of the release has an entry with all fields, and each document that differs from the previous release (listed by git diff --name-only between the two releases over standards/scf) has a new entry in its change record. The automated report of a changed document with no new entry is E2 and is added when backlog B-25 is closed. Checks: SCF-CHK-323.

SCF-CHG-022. Corrections after 1.0.0

A defect found in a document of SCF after 1.0.0 MUST be entered in the change record when the maintainers accept it, that is when they decide that the text is wrong, and MUST be corrected in the next release in which its correction is permitted: a correction of the class MINOR or PATCH in the next release, a correction of the class MAJOR (SCF-CHG-004) in the earliest MAJOR release that SCF-CHG-015 permits. Until then the entry is marked a known erratum.

  • Rationale. A defect left in place is read as the standard; correcting it in the open is what errata are for, and a defect whose correction must wait for the cadence of MAJOR releases stays visible as a known erratum while it waits.
  • Source. Decision, owner Product Owner (ADR-0010, proposed).
  • Applies. The maintainers of SCF.
  • Verification. E1 — each accepted defect has an entry in the change record; an entry marked a known erratum names the earliest release in which the correction is permitted, and no later release lacks the correction. Checks: SCF-CHK-324.

Guidance

Three version numbers

Three numbers appear around SCF and should not be confused.

Number What it identifies Set by
SCF version the standard: the version of the index document, named by a conformance statement this part
Hub release tag the bundle of the whole Hub in which a consumer receives SCF; a consumer pins an exact tag the Hub release process
Release version of a product one release of a system built with SCF, in the form MAJOR.MINOR.FIX Update and lifecycle §3

A Hub release may carry an SCF version that has not changed since the previous Hub release. In this part a release of SCF is a Hub release in which at least one document of SCF differs from the previous Hub release; it carries a new SCF version (SCF-CHG-018). A Hub release that changes no document of SCF is not a release of SCF.

Classifying a change

Example Class Reason
A new universal requirement MAJOR a product that conformed could fail it
A recommendation becomes a requirement MAJOR strengthened
A new recommendation or permission MINOR nothing that conformed can fail; a new statement meets a new recommendation or registers an exception
The Applies line of a mandatory rule is widened MAJOR a product outside the old line could now fail
A glossary term on which a mandatory rule depends is redefined MAJOR a product that conformed could fail
A rule is withdrawn after deprecation MAJOR SCF-CHG-013
The expected result of a check is tightened MAJOR a product that passed could fail
A new profile MINOR no product claims it yet
A rule is marked deprecated MINOR still in force
A new check for a rule that no conforming product can fail MINOR nothing that conformed can fail
A new informative document MINOR adds, creates no obligation
A source date is corrected PATCH no obligation changes
A broken link is repaired PATCH no obligation changes
A sentence is reworded and a reader could take it to require something new MAJOR SCF-CHG-008

Change record

A change record is a table at the end of the document that records the changes of SCF-CHG-021, newest entry first, so that the last entry is the version in which the document was introduced. A release has no table of its own; its changes are the entries that carry its version in the tables of the documents it changes.

Corrections that change an obligation

A correction is classified like any other change. A correction that alters no obligation is a PATCH; one that tightens an obligation is a MAJOR change even though it repairs an error. A MAJOR correction that falls inside the 12 months of SCF-CHG-015 waits for the earliest release that permits it, unless it closes a security or legal defect; the defect is entered in the change record as a known erratum meanwhile (SCF-CHG-022).

Sources

Accessed 2026-11-21.

Change record

Version Date Class Change
0.1.0 2026-11-21 introduced the document, as proposed by ADR-0010