AG-819

Oversight-Gap Declaration

Meta-Governance & Assurance ~5 min read AGS v2.1 · 2026-06-06
EU AI Act NIST AI RMF ISO 42001

AGS Frontier Autonomy (Group K) | Meta-Governance & Assurance | Version 3.0

1. Definition

Oversight-Gap Declaration governs the explicit identification, quantification, and justification of the gap between an agent's capability and its overseers' ability to verify that capability — requiring an organisation to state, for each consequential deployment, how large the oversight gap is and why oversight remains reliable across it.

A scalable-oversight protocol (AG-818) is only meaningful if the gap it must span is known. This dimension forces the gap to be named: an organisation cannot claim "we have human oversight" without declaring whether humans can actually verify the agent's outputs, and how that claim holds as capability scales.

2. Scope

In scope: measuring/declaring the capability-vs-verifiability gap per consequential deployment; justifying oversight reliability at that gap; updating the declaration as capability grows; using it as a deployment-gating input.

Out of scope: the oversight method itself (AG-818) and the capability evaluation (AG-802). This dimension governs *the declaration and justification of the gap*.

3. Why This Matters

Organisations routinely assert "meaningful human control" without examining whether their humans can meaningfully control the system at all. As capability rises, the same governance language masks a widening, undeclared gap. Forcing an explicit oversight-gap declaration makes the erosion of real oversight visible and reviewable, prevents an "oversight in name only" posture, and gives regulators a concrete, comparable artifact.

4. Requirements

5. Maturity Model

6. Test Criteria

Test 6.1: Declaration Exists

Test 6.2: Update on Capability Change

Test 6.3: Gap-Triggered Response

7. Scoring

ScoreCriteria
0No analysis of whether overseers can actually verify the agent ("oversight" assumed)
1Gap acknowledged qualitatively but not quantified or justified
2Quantified per-deployment declaration with justified reliability, owner approval, update-on-change
3Gap-gated deployment, independent review, portfolio tracking, authority disclosure

8. Failure Scenarios

Scenario A — Oversight Theatre: A deployment claims "human-in-the-loop" while humans approve outputs they demonstrably cannot evaluate. An oversight-gap declaration would have exposed that the control was nominal.

Scenario B — Silent Widening: Successive model upgrades widen the gap without any declaration update; oversight quietly degrades from real to nominal over a year, unnoticed until an incident.

Scenario C — Unbounded Gap Shipped: A new capability puts the agent far beyond verifiable oversight, but with no gap-triggered response the deployment proceeds at full autonomy.

9. Regulatory Mapping

RequirementEU AI ActNIST AI RMFISO 42001
R1: Declare the oversight gapArt. 14 — Human oversightMAP 2.2 — Knowledge limits & oversightClause 6.1 — Actions to address risk
R2: Justify reliability across the gapArt. 55 — Model evaluationGOVERN 1.3 — Risk-based activityClause 8.3 — Verification
R3: Update on capability changeArt. 9 — Risk management lifecycleMANAGE 4.1 — Post-deployment monitoringClause 9.1 — Monitoring and measurement
R4: Gap-triggered responseArt. 55 — Risk mitigationMANAGE 1.3 — High-priority responseClause 6.1 — Actions to address risk
R5: Owner approval + independent reviewArt. 55 — GovernanceGOVERN 2.1 — AccountabilityClause 9.3 — Management review
R6: Retained safety case / disclosureArt. 11 — Technical documentationGOVERN 4.3 — Information sharingClause 7.5 — Documented information
R7: No oversight theatreArt. 14 — Effective oversightMAP 3.5 — Human oversightA.9 — Use of AI systems

EU AI Act — Article 55 and Article 9

Article 55 systemic-risk assessment must reckon with whether oversight is real; Article 9 requires lifecycle risk management. AG-819 makes the oversight gap an explicit, managed risk artifact rather than an unexamined assumption.

NIST AI RMF — GOVERN 1.3, MAP 2.2

GOVERN 1.3 (risk-based activity levels) and MAP 2.2 (document system knowledge limits and human oversight of outputs) require exactly the declared, justified oversight gap.

ISO 42001 — Clause 6.1, Clause 9.1

Clause 6.1 (actions to address risks) and Clause 9.1 (monitoring) require identifying and acting on the oversight gap as a managed risk.

Cite this protocol
AgentGoverning. (2026). AG-819: Oversight-Gap Declaration. The Protocols of AI Agent Governance, AGS v2.1. agentgoverning.com/protocols/AG-819