Governance, Oversight & AgentOps

• Risk-based autonomy tiers: autonomy level as a function of action impact, uncertainty, identity, data sensitivity, regulation, reversibility and confidence
• Human-in-the-loop and human-on-the-loop checkpoints at durable pause points
• Policy-as-code compiled into gateway and runtime enforcement
• Registries for agents, prompts, models, tools, skills, datasets and policies
• CI/CD, canary and shadow release, with rollback
• Audit trail, lineage and evidence packs for regulators
• Feedback capture flowing into fine-tuning, distillation and prompt change
• Incident process and post-incident change

Accountable owner

AI Governance Office / Risk & Compliance, with Legal

• Chief Risk or Compliance Officer, or Head of Responsible AI — accountable owner
• AI risk manager — autonomy tiers and control design
• Compliance analyst — framework mapping and evidence
• Legal counsel — regulatory interpretation and contracts
• Product owner — accepts residual risk for their agent
• Internal audit — independent assurance
• Release manager — gates, canaries, rollback

Ownership and phase are architectural recommendations, not assessed results.

Keep it lightweight in the pilot: an agent registry, an owner per agent and a written autonomy tier. Promote to full control the moment agents touch production systems or personal data — before any traffic, not after.

Signals to watch

• Share of actions executed inside the policy envelope
• Approval latency and override rate
• Registry completeness against deployed reality
• Control coverage mapped to the chosen framework
• Time to revoke or roll back an agent
• Share of incidents that produced a durable change

Governance owns promotion authority and the decision record. Changes to that authority require separate authorization.

Failure modes

1. Approval theatre: reviewers who cannot see enough context to disagree
2. Policy drift between the written standard and the deployed rules
3. Shadow agents outside any registry
4. Transparency obligations missed because the system was classified as low risk
5. Feedback captured but never reaching a model or prompt change

Existing tool and standards snapshot · approximately mid-2026. Examples, not required dependencies; verify current versions before adoption.

Autonomy is a policy, not a switch. The formula above lets one system be fully autonomous for reversible reads and strictly gated for irreversible writes, which is the only configuration that survives contact with a regulated environment.