# Human-in-the-Loop Gate

A required human approval checkpoint inserted before an agent takes a consequential or irreversible action.

## Why the CCAR-P exam tests this

CCAR-P tests placing approval gates on high-impact actions and enforcing them in code rather than relying on the model to ask.

## Definition

A **human-in-the-loop gate** pauses the agent and requires an explicit human decision before a sensitive action proceeds — sending funds, deleting data, emailing a customer, deploying code. The agent proposes; a person approves, edits, or rejects.

The gate must be a **deterministic control in code**, not an instruction in the prompt. A prompt saying 'ask before deleting' can be overridden by a confident model or an adversarial input; a code path that blocks the tool call until an approval token is present cannot. This is the difference between a suggestion and a guarantee.

Gate placement is a design decision: gate the **irreversible and the high-blast-radius**, and let low-risk, easily-reversible actions run autonomously so the human isn't drowned in trivial approvals. Escalation should trigger on **policy** (this action class requires review) rather than on the model's self-reported confidence.

## Exam trap

Believing a prompt instruction to 'ask the user first' is a real safeguard — a must-hold gate belongs in deterministic code, and escalation should key off policy, not the model's own confidence.

## Commonly confused with

- **agentic-loop** — The loop is the autonomous cycle; the HITL gate is a deliberate pause inserted into that cycle for approval.

## Related

- agentic-loop
- idempotency-and-retries
- workflow-vs-agent
- guardrails
- escalation

---

Source: Claude Cert Prep — an independent, unofficial CCAR-P study resource (domain P1). Not affiliated with Anthropic.