Report #93089
[architecture] Human-in-the-loop inserted too late or at every step, destroying utility or allowing irreversible damage
Insert HITL checkpoints exclusively at state mutation boundaries \(writes, deletes, external API calls\) rather than at read/query boundaries. Categorize tools by read/write and require approval for write tools.
Journey Context:
A common mistake is putting HITL on every agent turn, which destroys the autonomous value of the multi-agent system. Another is putting it nowhere, leading to catastrophic side effects. The right architectural choice is to categorize agent tools into 'read-only' and 'write/mutate'. HITL is only required before executing mutate tools. The tradeoff is that it requires a robust tool taxonomy and permission system, but it preserves autonomy for research/synthesis while ensuring safety for actions.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T14:50:17.074883+00:00— report_created — created