The capability MUST be kept in commons/ of the .github repository, which holds what any company or harness of Intellectual Frontiers may use (commons/about.ts; amended 2026-11-15, when commons' READMEs became its TypeScript, commons 0011-documentation). Its ontology MUST be under commons/ontology/supply-chain/, its specifications in commons/spec-kit/, its tools in commons/tools/ and what the tools generate in commons/generated/.
Enforced (check): .github: bun test ./tests/ — Layout: the files the specification names are there
A file a tool generates MUST carry .auto. in its name (packaging.auto.toml) or sit between marks that say AUTO-GENERATED inside a file a person writes, MUST say which tool and which source made it, and MUST NOT be edited by hand: a check MUST fail where it is not what its tool makes from the ontology.
Enforced (check): .github: bun test ./tests/ — Generated and Generator: the files say they are generated, carry .auto. and are what the tool makes
A harness or a script MUST read a generated table and MUST NOT keep a fact of its own that the ontology holds (a command, a package name, a detection ID); where it must carry a copy because it runs before it can read anything (a script piped from the internet), the copy MUST be generated and checked as FR-002 says.
Enforced (check): .github: bun test ./tests/ — Module: the TypeScript module says what the TOML says; archon's own check follows its wiring
A software component MUST be identified by its package URL (purl) where the package URL specification has a type for its package manager, and an SBOM made from this capability MUST write it with SPDX 3.0.1's Software/packageUrl. A component whose manager has no purl type MUST say so and MUST NOT be given an invented type.
Enforced (check): archon: archon test — archon's SBOM tests: components carry package URLs of the type the table names, percent-encoded, and the document validates against SPDX 3.0.1
Every component MUST be able to say where it came from: a distribution's repository, reached through a package manager the ontology names, or a download pinned by its SHA-256.
Enforced (check): archon: archon test — archon's SBOM tests: pinned programs carry the lock's download address and SHA-256, system packages the manager that supplied them
What has been run on a real computer, what has been run only against stand-ins, and what has not been run MUST be told apart wherever a status is shown, and nothing not run for real MAY be called verified. A claim of verification MUST say where and when.
Enforced (check): .github: bun test ./tests/ — Generated: a family is verified only with where and when, and a catalogued family has no assurance
This capability MUST NOT claim that anything is compliant with a regulation or a standard. It MUST say which practices it supports, as informative notes, and name the sources it read.
Enforced (none): a property of the text, read by a person
The practices below are what this capability supports; none is a claim of compliance (FR-007).
Component inventory and provenance: the NIST Secure Software Development Framework (SP 800-218) asks makers to collect provenance for each release and each component, with a software bill of materials (SBOM) as its example. NIST's software supply chain guidance under US Executive Order 14028 applies the controls of SP 800-161 (cybersecurity supply chain risk management) to suppliers. The NTIA minimum elements of an SBOM (supplier, component name, version, other unique identifiers, dependency relationships, author, timestamp) are the fields FR-004 and FR-005 keep.
European Union: the Cyber Resilience Act (Regulation (EU) 2024/2847), Annex I, Part II, requires manufacturers to draw up an SBOM in a commonly used and machine-readable format covering at least the top-level dependencies. It names no format; SPDX (ISO/IEC 5962 for its 2.x version) and CycloneDX (ECMA-424) are the usual ones.
Provenance of builds: SLSA v1.0 (OpenSSF) describes provenance for build artifacts. It is not mapped here yet (OQ-2).
Declaring a harness's own pinned programs: each harness declares its own tools (commons/toolchain), which read the pins of 0002-packaging for the addresses and hashes.
Scanning for vulnerabilities, signing and attestation.
Judging whether a harness complies with any regulation.
A package manager that has no package URL type (nix, guix, flatpak, snap, winget, scoop, chocolatey, xbps, portage, opkg, FreeBSD's pkg): its components are identified without one and the table says so, per FR-004.
A generated file edited by hand: the check that regenerates it fails, per FR-002.
A harness that has its own copy of a command the ontology holds: it is a drift, per FR-003, and the harness's own checks name it.
A family a person has tried on a real computer but nobody has written down where: it stays unverified until verifiedOn says where and when, per FR-006.
Whether the European Commission specifies the SBOM format and elements by implementing or delegated act, and when: the sources read cite different provisions; the official text is to be checked.
The namespaces the package URL types give their packages (deb, rpm, apk and alpm use the distribution), to be confirmed against the type definitions before an SBOM is made.
A harness can say, from a table it does not write, how to install a program on every family the table supports, and what each family calls the package.