6 patterns
Safety & Oversight
Checks and human approval points wrapped around any of the other patterns.
Patterns in Safety & Oversight
Human-in-the-Loop
Safety & Oversight · 6 nodes · 2 LLM calls · branch · human · 3 scenarios
Pause before high-stakes or irreversible actions so a person can approve, edit or reject; then resume.
Guardrails
Safety & Oversight · 7 nodes · 5 LLM calls · parallel · branch · 3 scenarios
Checks that run before and after the agent, any of which can block or redirect the flow.
Permission Policies
Safety & Oversight · 6 nodes · 5 LLM calls · loop · branch · human · 2 scenarios
Every tool call is checked against declarative allow, ask and deny rules and a budget before it runs.
Sandboxed Execution
Safety & Oversight · 8 nodes · 2 LLM calls · loop · branch · human · 2 scenarios
Agent commands run inside an isolated filesystem and network boundary, so only crossings of that boundary need approval.
Dual LLM
Safety & Oversight · 8 nodes · 2 LLM calls · 2 scenarios
A tool-holding LLM never sees untrusted text; a tool-less LLM reads it, and code passes its output along only as variables.
LLM-as-Judge
Safety & Oversight · 7 nodes · 3 LLM calls · branch · 2 scenarios
A separate judge model scores a system's outputs against a rubric, and the scores gate releases or rank candidates.