Read Clause 8 as a set of operating obligations
Clause 8 addresses operational planning and control, risk assessment and treatment, and impact assessment. Read each of these as an operating obligation, and describe it with the same four elements: the requirement, the control, the owner, and the evidence.
From requirement to evidence
| Element | Description |
|---|---|
| Requirement | Operational planning and control, risk assessment and treatment, impact assessment |
| Control | A documented process or a runtime-enforced mechanism |
| Owner | A named role accountable for the control |
| Evidence | Records produced by the control as it operates |
Change control and third-party components are the hard cases
Change control and third-party components are the hard cases for Clause 8. Treat them the same way as any other requirement: assign an owner, choose a mechanism, and define the evidence the control produces.
Change gating is one of the controls that must hold on every change, which makes it a candidate for technical enforcement rather than documented process alone.
Where runtime governance fits
Runtime governance fits where a control must hold on every request, tool call, or change. Runtime policy enforcement, tool approvals, and audit logging can support operational controls for production AI agents.
Deciding which controls need runtime enforcement
| Mechanism | Use it for | Examples |
|---|---|---|
| Documented process | Decisions that need human judgment | Accepting residual risk |
| Technical enforcement | Anything that must hold on every request, tool call, or change | Access control, policy enforcement, logging, change gating |