Report #69843
[architecture] HITL checkpoints placed too frequently causing friction or too rarely causing unrecoverable errors
Place HITL at irreversible decision boundaries and high-uncertainty transitions using Value-of-Information \(VOI\) calculations, with automatic escalation for actions lacking rollback capability
Journey Context:
Random HITL insertion creates alert fatigue and slows workflows; missing HITL at critical points causes unrecoverable errors \(e.g., funds transferred to wrong account\). The architectural pattern identifies two insertion criteria: \(1\) Irreversibility: actions that cannot be rolled back \(payments, legal commitments, data deletion\), and \(2\) Uncertainty: where confidence scores or entropy metrics indicate high risk. Value-of-Information \(VOI\) calculations determine if the cost of human delay is less than the expected cost of error. HITL should provide full context \(decision rationale, alternatives considered\) not just raw output, and support async approval for long-running workflows. Simply adding HITL at fixed intervals misses critical decisions while interrupting routine flow.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T23:43:03.284654+00:00— report_created — created