AI Governance Engineer
GitHub
On this page

Pattern: Human-in-the-loop Gate

A human approval step at a defined high-consequence decision point, so an agent's autonomy stops exactly where the stakes justify the latency.

Layer 04 · Runtime Controls & Observability In the chapter 05 catalogue

One working control on the engineering side of AI governance.

Summary: Require human approval at a defined, high-consequence decision point before an agent’s action takes effect, so that autonomy is bounded by a person exactly where the stakes justify the latency. Oversight is a designed checkpoint, not an afterthought.

Human-in-the-loop Gate A sequence diagram generated by Archify. propose action routine: auto under guardrails high-consequence: human required approve within time box execute action reject or timeout: drop log approver, context, decision Classify by consequence Human decides in a time box Execute or drop, then log Agent · proposes action · Sequence participant Agent proposes action Policy check · human required? · Sequence participant Policy check human required? Reviewer · named human · Sequence participant Reviewer named human Action target · payment, denial · Sequence participant Action target payment, denial Evidence log · approver, decision · Sequence participant Evidence log approver, decision Legend request return security async trace default message
Human-in-the-loop GateFor the actions the policy marks as needing a human, the agent pauses, a named reviewer decides within a time box, and the decision is logged as evidence. Define which actions need a human by policy, not by habit. Generated from the Body of Knowledge.Open interactive diagram (opens in a new tab)

Objectives

Insert meaningful human oversight where an action is irreversible or high-impact, and record the decision as evidence.

Target users

AI governance engineer, product owner, risk owner.

Impacted stakeholders

Affected persons, users, model owners, regulators.

Relevant principles

Start from a named failure mode or harm; register and bound every actor before it acts.

Context

An agent whose actions include some that are irreversible or affect people’s rights (a payment, a denial, a publication) alongside many that are routine.

Problem

Full autonomy over a high-consequence action removes the human oversight the law and the risk both require; full manual review over every action destroys the value of the agent. Undifferentiated oversight fails in both directions.

Solution

Classify actions by consequence. For the high-consequence class, gate the action behind a human approval step with enough context to decide, and block the action until approval. Log the approver, the context and the decision as evidence. Keep the routine class autonomous under guardrails. This realises the EU AI Act Art. 14 human-oversight requirement 1 at the point of action.

Consequences

Oversight lands where it matters without throttling routine work, and the approval is auditable. The cost is designing the consequence classification and the latency it adds to gated actions.

Kill Switch / Circuit Breaker; Runtime Guardrail; Policy Card; Agent Identity & Scoped Credentials; FRIA-as-Code.

Maps to: EU AI Act Art. 14 · ISO/IEC 42001 · NIST AI RMF (Manage) · OWASP Agentic ASI02 · Layer 04 Runtime Controls & Observability.

Threat IDs follow the OWASP Top 10 for Agentic Applications 2026 2 and function labels the NIST AI RMF3. Mappings are illustrative, not a claim of conformity.

Sources

  1. [1] Regulation (EU) 2024/1689 (AI Act), Art. 14 (human oversight of high-risk AI systems). Publications Office of the EU (EUR-Lex). 2024-07-12. https://eur-lex.europa.eu/eli/reg/2024/1689/oj/eng (verified: primary)
  2. [2] Top 10 for Agentic Applications 2026 (ASI IDs). OWASP GenAI Security Project. 2025-12-09. https://genai.owasp.org/resource/owasp-top-10-for-agentic-applications-for-2026/ (verified: primary)
  3. [3] AI Risk Management Framework (AI RMF 1.0; Govern, Map, Measure, Manage). NIST. 2023-01-26. https://www.nist.gov/itl/ai-risk-management-framework (verified: primary)
Edit this page on GitHub
Cite this pattern

García Aibar, J. (2026). Pattern: Human-in-the-loop Gate. In AI Governance Engineering: The Thesis & Body of Knowledge (v0.5.0), chapter 05, Patterns. https://doi.org/10.5281/zenodo.22956197. https://aigovernanceengineer.com/patterns/human-in-the-loop-gate. CC BY 4.0

BibTeX

@misc{aige2026bok,
  author  = {Jorge García Aibar},
  title   = {{AI Governance Engineering: The Thesis \& Body of Knowledge}},
  chapter = {05. Patterns: Human-in-the-loop Gate},
  year    = {2026},
  version = {0.5.0},
  doi     = {10.5281/zenodo.22956197},
  url     = {https://aigovernanceengineer.com/patterns/human-in-the-loop-gate},
  note    = {Version 0.5.0}
}
Share on LinkedIn

Obligations this pattern evidences

Register rows that list this pattern among the patterns that build their evidence. Mappings are illustrative, not a claim of conformity.

Cases where it applies

Incident post-mortems that name this pattern as a control that would have caught the failure.

Draft controls in the open control profiles that build on this pattern. A control states the requirement and the evidence it must leave behind.