4.5 Clause
Application to AI systems
The subclause applies the principles to a complete AI system rather than to a single component. A system can contain several components, each with its own method, and the capabilities a user sees may come from the combination rather than from any one part.
What this settles
Most real failures of description happen at the seams. A component view is accurate and useless if the reader cannot see how the parts combine into the behaviour they actually experience.
Who it binds
The organisation that describes the system and the recipient who relies on the description. The clause sets no duty, but it sets the unit of analysis.
What to do in your practice
Describe the system at two levels: the component methods and the system capabilities. Then record the combination, including orchestration, fallback and human handover. The gap between the two levels is where risk and change impact live.
Evidence an auditor or regulator asks for
| A component map with the method recorded for each component. | Shows where the behaviour comes from. |
|---|---|
| A system-level capability list with the components that deliver it. | Connects parts to the user experience. |
| A note on orchestration, fallback and human handover. | Captures the seams that a component list misses. |
Which capability a user experiences is produced by a combination of components rather than by one model?
Common gaps this page catches
- The description stops at the model and never reaches the system the user sees.
- Orchestration is undocumented, so no one can say which component produced an output.
- Human handover is described in a procedure but absent from the system description.
What to prepare before publication
Add the system level to the template. The first useful artefact is usually a simple diagram with each component labelled by method and each user-facing capability named.
How to test it here
Take one live system rather than a template, find the field or sentence where Application to AI systems 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 "concepts clause" and stops where the public record stops.
Common questions
- What does Application to AI systems mean in ISO/IEC DIS 42102?
- The subclause applies the principles to a complete AI system rather than to a single component. A system can contain several components, each with its own method, and the capabilities a user sees may come from the combination rather than from any one part.
- What evidence should we keep for 4.5?
- A component map with the method recorded for each component. A system-level capability list with the components that deliver it.
- Is Application to AI systems 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