System Construction Framework
Status: draft normative and professional knowledge base, version 0.1
SCF is a brand-independent framework for constructing operating systems: desktop and server systems, appliances, kiosks, edge and embedded devices, recovery media, security workstations and white-label derivatives.
SCF does not prescribe one package format, one build engine, one init system
or one update mechanism. It defines the stable obligations a system must
satisfy, the evidence that proves it, and the portable model that lets the same
obligations be met on deb, rpm, apk, BSD pkg, IPS, ports trees and
source-built systems.
An operating system is not a build artefact. It is a product with a support period, a threat model, a data policy, an update channel, a vulnerability process and a legal owner. A framework that only describes how to assemble an image describes the least important part of the work.
Normative hierarchy
- applicable law and safety obligations, including product-security regulation and export control;
- platform requirements necessary for interoperability and boot, including firmware, signing-authority and ABI constraints outside the producer’s control;
- upstream licence terms and trademark terms of every included work;
- the SCF Constitution;
- the applicable SCF Product Profile;
- documented product policy: threat model, support period, data policy, architecture and hardware matrix;
- build system, recipes, adapters and implementation.
A lower layer MUST NOT silently weaken a higher one. A justified exception requires scope, an owner, evidence, the risk, the mitigation and a review date.
Where SCF and HIF both apply to the same surface, both apply in full. SCF MUST NOT be used to justify weakening an HIF requirement, and HIF MUST NOT be used to justify weakening an SCF requirement.
Corpus
Orientation and foundations
Portable construction model
Systems and profiles
Evidence and conformance
Release and service
- Update and lifecycle — version identity, fixpacks, channels, advisories, support phases, branches in the construction repository
Templates
- Product profile — what a product claims and what backs it: identification, scope, conformance level, traceability matrix, exception register
- Release record — the controlled record of one release, following the twelve steps of the release gate
Planned documents
The following are part of the corpus map and are not yet written. Until a document exists, its subject is governed by the Constitution alone.
| Document | Subject |
|---|---|
SUPPLY_CHAIN.md |
provenance, attestation, SBOM, VEX, dependency due diligence |
BOOT_AND_INTEGRITY.md |
boot chain, measured boot, verified boot, anti-rollback |
CRYPTOGRAPHY_AND_KEYS.md |
algorithm policy, key custody, signing infrastructure, rotation |
DATA_PROTECTION.md |
data classification, encryption at rest and in transit, erasure, reset |
PRIVACY_AND_TELEMETRY.md |
lawful basis, minimisation, identifiers, consent surfaces |
VULNERABILITY_MANAGEMENT.md |
intake, triage, coordinated disclosure, advisories, reporting duties |
HARDWARE_ENABLEMENT.md |
architectures, firmware, drivers, certification, hardware matrix |
LOCALISATION_AND_SOVEREIGNTY.md |
languages, keyboards, time, jurisdiction and deployment profiles |
LEGAL_AND_LICENSING.md |
licence obligations, source availability, trademarks, export control |
BUILD_PLANE_ENGINEERING.md |
isolation, mirrors, caches, workers, quotas, operator runbook |
REFERENCES.md |
standards, regulation, primary sources |
Normative words
- MUST / MUST NOT — a requirement for SCF conformance;
- SHOULD / SHOULD NOT — the expected decision unless evidence justifies an exception;
- MAY — a permitted choice, subordinate to stronger requirements.
Core terms
| Term | Meaning in SCF |
|---|---|
| System | the complete operating system product, including defaults, policy and lifecycle |
| Specification | the declarative description of a system, authored by a human or generated from one |
| Lock | the specification with every input resolved to an exact, addressable version |
| Build | one execution of a lock inside an isolated environment |
| Artefact | a file produced by a build: image, root filesystem, package set, manifest, report |
| Release | an immutable, signed set of artefacts with a manifest, evidence and a support statement |
| Channel | a named, movable pointer to a release, with its own promotion and audit rules |
| Adapter | the component that maps the portable build model onto one platform family |
| Profile | a class of product that adds requirements to the Constitution |
| Evidence | a reproducible observation that a requirement is met |
Product process
purpose, users, threat model and jurisdiction→ product profile→ specification→ resolved lock→ isolated build→ artefacts, manifest, SBOM and provenance→ verification and evidence→ signing and release→ channel, support period and update service→ vulnerability handling→ end of life and migrationMaintain traceability from an obligation through a requirement, a decision, an implementation and a test to evidence. A requirement with no method of verification is incomplete.
Source policy
SCF cites traceable primary sources: standards bodies, regulation as published in official journals, upstream project documentation and source trees, and original technical reports. Secondary articles, translations and vendor marketing MAY help locate a primary source but MUST NOT be the evidentiary basis of a normative requirement.
The existence of a source does not make a statement universal. Every ported claim must carry its platform, version, date, scope and limits.
Change management
A material change records the changed statement, the reason and evidence, the affected profiles and tests, the migration impact, the reviewer and the date. Regulation, signing-authority policy and platform rules MUST be reviewed before related work and at least annually.
Legal notice
SCF summarises published legal and regulatory texts to make obligations verifiable in engineering. It is not legal advice. Before releasing a product into a regulated market, obtain qualified counsel on product-security regulation, licensing, trademarks and export control.