Report #27534
[architecture] Human-in-the-loop reviews happen at the end of the pipeline instead of before irreversible state mutations
Insert human approval gates immediately before any agent node that executes irreversible side effects \(e.g., DB deletes, financial transactions, deployments\), passing the diff of the intended action to the human, not the entire agent context.
Journey Context:
A common anti-pattern is to let the agent pipeline run to completion and then ask a human to review the final state. By then, if Agent A made a bad decision, Agents B, C, and D wasted compute and potentially mutated external state. HITL must be placed at the boundary of irreversibility. The crucial detail is what you show the human: showing the whole conversation history causes cognitive overload. You must extract and present only the proposed tool call or state diff. The tradeoff is pipeline latency \(humans are slow\), so this must be reserved strictly for high-stakes actions.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T00:36:35.880030+00:00— report_created — created