Product profile template
Version: 0.1
The form in which a product states what it claims and what backs the claim.
It instantiates the traceability matrix of EVALUATION.md §6, the
conformance levels of §5 and the exception register of §8. It introduces no new
obligations.
One profile document per release, not per product: a claim is bounded by the release it was verified against.
How to use this
Copy §§1–7 into the product’s own documentation and fill them. Guidance is in blockquotes and is deleted when filled.
Three rules govern every entry:
- A requirement with no path to evidence is incomplete and MUST NOT be counted as met
(
EVALUATION.md§6). “Implemented” is not evidence. - A property may only be claimed at the level at which it has been observed (§2 of
EVALUATION.md). A kernel option in a configuration file is E2 evidence about the configuration, not E4 evidence about the running system. - An unmet requirement is recorded as an exception, not omitted. A profile with no exception register invites the question of what was left out, and answers it badly.
1. Identification
Without these bounds the statement is void (
EVALUATION.md§5). Fill every row.
| Field | Value |
|---|---|
| Product | |
| Release version | |
| Specification identity | spec_id, lock_id |
| Channel | |
| Upstream base | |
| SCF version | |
| HIF version | |
| Profiles claimed | |
| Architectures | |
| Reference hardware | > make, model and firmware. “amd64 PC” is not reference hardware |
| Date of statement | |
| Statement owner | > a named person |
2. Scope
2.1 In scope
What this statement covers: the artefacts, the delivered configuration, the update channel. Name them precisely enough that a reader can obtain the same thing.
2.2 Out of scope, and why
What a reader might reasonably assume is covered but is not: other architectures, other profiles, variants built from the same tree, third-party software installed later.
Silence here is read as a claim. State the boundary.
3. Conformance statement
| Level claimed | > SCF-Declared, SCF-Conformant or SCF-Validated |
| Basis | > the criteria of EVALUATION.md §5 for that level, each answered below |
SCF-Declaredmarks the beginning of a process. It MUST NOT be presented as a quality signal, in this document or in any material derived from it.
3.1 Criteria for the level claimed
Criterion (EVALUATION.md §5) |
Met | Where shown |
|---|---|---|
4. Traceability
For each requirement in scope, the chain of EVALUATION.md §6 must be completable.
The table records it; §4.2 records the full chain where an external obligation exists.
4.1 Requirement matrix
| Requirement | How satisfied | Verification | Evidence | Level | Status |
|---|---|---|---|---|---|
SCF-___-___ |
> mechanism, not intention | > the named method | > where the evidence is, resolvable | > E0–E5 |
> met / exception / not in scope |
Status
metrequires a level at or above the minimum for the requirement class (EVALUATION.md§2). An entry whose evidence column is empty isexception, whatever the implementation says.
not in scoperequires a reason in §2.2. It is not a way to shorten the table.
4.2 External obligations
Where a requirement exists because of law, a threat model or a customer requirement, record the whole chain so the origin survives staff changes:
obligation → SCF requirement → product requirement → specification field, component or policy → implementation → automated check → manual or hardware scenario → evidence and level → exceptions
| Obligation | Chain |
|---|---|
5. Exception register
Fields are those of
EVALUATION.md§8. An expired exception blocks a new conformance statement until reviewed.An exception MUST NOT carry a permanent architectural decision. If a requirement is wrong, propose a change to the standard instead — the corpus has a procedure for that, and using an exception instead hides a defect of the standard inside a product.
| Field | Entry |
|---|---|
| ID | |
| SCF version and requirement | |
| Product and profile | |
| Reason | > why it is not met. “Not implemented yet” is a reason; “low priority” is not |
| Affected users, devices and data | |
| Risk and likelihood | |
| Compensating control | > what reduces the risk meanwhile, or explicitly “none” |
| Owner | > a named person |
| Expiry or review date | > a date, not “ongoing” |
| Evidence | > of the risk assessment and of the compensating control |
6. Not claimed
Properties a reader might expect and that are deliberately not claimed: higher classification tiers, certification schemes, cryptographic strength beyond what was measured, hardware outside the matrix.
SCF-CRY-007bounds cryptographic claims.SCF-GOV-002requires the declared scope of responsibility to be honest. This section is where both are discharged.
7. Approval
| Approved by | > a named person, per SCF-EVD-005 |
| Role | |
| Date | |
| Against gate | > the release gate of EVALUATION.md §7, evidenced in the release record |
A green pipeline, a visual inspection or an absence of complaints is not a gate (
SCF-EVD-005). The approver is accountable for the statement, not for the build.
8. Common failures
Recorded so they are recognised rather than repeated.
| Failure | Why it is a failure |
|---|---|
| Evidence column says “see repository” | not resolvable; evidence must be reachable by the reader of the statement |
| Level claimed higher than the observation supports | the most common defect; configuration inspected but behaviour claimed |
| Empty exception register | either nothing was checked, or something was hidden. Both are worse than an honest list |
| Statement without reference hardware | void by EVALUATION.md §5, however complete the rest |
| Exception with no expiry | becomes permanent silently; the register stops being a plan |
| Requirement marked out of scope to avoid work | §2.2 must justify it, and a reader will check |