Capability governance
Governance should tighten as capability and autonomy increase.
A capability-based model links observed or forecast capability thresholds to stronger controls, approvals, evaluations and deployment restrictions.
C1Bounded capability, low autonomy
C2Material capability, constrained tools
C3High capability, broad tool use
C4Frontier capability or material systemic concern
| Tier | Illustrative governance posture | Typical controls |
|---|---|---|
| C1 | Routine governance with bounded deployment scope. | Baseline testing, access control, logging, owner approval. |
| C2 | Enhanced review and explicit risk acceptance. | Expanded evaluations, stronger permissions, monitored rollout. |
| C3 | Senior approval and strong containment assumptions. | Independent assurance, restricted tools, stop mechanisms, red-team evidence. |
| C4 | Exceptional governance posture. | Executive decision, strict access, external review where appropriate, deployment constraints. |
Conceptual principle: governance thresholds should be defined before the system crosses them. The trigger should automatically change the control regime.