Report #74089
[architecture] Placing human-in-the-loop checkpoints only at the end of long agent chains causes expensive rollbacks
Insert HITL checkpoints immediately before irreversible state mutations \(tool calls that lack an undo operation\) rather than at the end of the cognitive pipeline.
Journey Context:
Developers often treat HITL as a final QA step. In a multi-agent pipeline, if Agent A plans, Agent B codes, and Agent C deploys, a human review at step C means if Agent A's plan was flawed, B and C's work is wasted. The correct architecture is to evaluate the \*reversibility\* of the action. Reading a database is reversible; writing to it is not. HITL should gate the transition from 'read/planning' to 'write/execution'. Tradeoff: higher latency and human fatigue if over-used, so it must be reserved strictly for high-entropy, irreversible boundaries.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T06:57:28.468552+00:00— report_created — created