4 Clause
Principles of AI system characterization based on methods and capabilities
The clause sets the principles that govern how a system is described with methods and capabilities. It separates the principles from their intended application, explains the two ideas, and then applies them to a whole system rather than to a model in isolation.
What this settles
Principles first, descriptors second. The order matters: a team that starts with a taxonomy tends to fill cells without agreeing why the description exists. This clause is where that agreement belongs.
Who it binds
The organisation that adopts the framework, as a matter of method. The clause sets no legal duty; it sets the reasoning the later clauses assume.
What to do in your practice
Hold one short session on the purpose of the description before any template is filled. Record the decisions the description will support: suitability, change impact, assurance, incident response and communication. Then choose the descriptors that serve those decisions.
Evidence an auditor or regulator asks for
| A purpose statement for the characterization, naming the decisions it supports. | Prevents a taxonomy exercise with no consumer. |
|---|---|
| A record of the principles session and who attended. | Shows the method was agreed, not imposed. |
| A list of descriptors deliberately excluded, with the reason. | Documents restraint as a decision. |
What decision will change because of this description, and who will make it?
Common gaps this page catches
- The team fills a matrix without agreeing what it is for.
- Principles are quoted in a slide and never used to choose descriptors.
- The description serves a single team, so nobody else can act on it.
What to prepare before publication
Write the purpose statement and the decision list first. Keep it to one page and revisit it when the system or its use changes.
How to test it here
Take one live system rather than a template, find the field or sentence where Principles of AI system characterization based on methods and capabilities is used, and put this page beside it. Record the answer, the artefact and the date. A glossary entry on its own is an intention; a dated record beside a live artefact is evidence.
What this page does not claim
The page does not reproduce the draft, does not know the descriptor wording that the public preview withholds, and does not certify the system or the organisation. It states the unit at the claim level "principles clause" and stops where the public record stops.
Common questions
- What does Principles of AI system characterization based on methods and capabilities mean in ISO/IEC DIS 42102?
- The clause sets the principles that govern how a system is described with methods and capabilities. It separates the principles from their intended application, explains the two ideas, and then applies them to a whole system rather than to a model in isolation.
- What evidence should we keep for 4?
- A purpose statement for the characterization, naming the decisions it supports. A record of the principles session and who attended.
- Is Principles of AI system characterization based on methods and capabilities a requirement?
- No. The draft is a descriptive framework. It sets no management system requirement and no conformity test. It becomes binding only when a contract, a regulator or a management system adopts it.
Related units
Last updated: · Markdown version · Check your system