docs: Course section — Human-in-the-Loop Approval Workflows

[rdwj]

Summary

Teach users how to require human approval for sensitive tool executions and build approval workflows. HITL is essential in regulated industries and high-stakes environments where autonomous tool execution is unacceptable.

Course Section Outline

• When to use approval workflows — high-stakes actions, regulated industries, data modification
• Adding requires_approval to tool definitions via the @tool decorator
• How the interrupt/resume cycle works — request suspension, approval callback, execution resume
• Configuring approval timeouts and escalation behavior
• Conditional approval predicates — approve automatically below thresholds, require approval above
• UI integration for approval prompts — notification, context display, approve/deny buttons
• Audit trail for approval decisions — who approved, when, with what context
• Common patterns: financial thresholds, data deletion gates, external API call authorization

Lab Exercise

Create an agent with a "delete_record" tool decorated with requires_approval. Trigger the approval flow through the UI. Test three paths: approve the deletion, deny it, and let it time out. Verify the audit trail captures all three outcomes.

Companion Issues

Companion issues filed on fips-agents/agent-template, fips-agents/gateway-template, fips-agents/ui-template, and fips-agents/fips-agents-cli.

Size

M