Synchronous Execution-Plan Confirmation
Agent synchronously emits its full execution plan for user confirmation before any side-effect step, and provides asynchronous operation recordings for post-hoc review.
Problem
When the agent executes silently and only shows results after the fact, users cannot verify that the agent understood the request correctly until damage is done. Post-hoc transcripts help audit but cannot prevent. Differs from approval-queue by being agent-driven (the agent emits the plan up front) rather than human-driven (the human writes the plan).
Solution
At the boundary between planning and execution, the agent renders the plan in plain language (or structured form the user can review). User must explicitly confirm (button press, signed message) before execution starts. During and after execution, full operation recordings are persisted to a user-visible log for asynchronous review. Pair with human-in-the-loop, dry-run-harness, decision-log, policy-gated-agent-action.
When to use
- User-facing agent with consequential actions.
- Regulated industry requiring documented user authorization.
- Plan can be rendered in user-comprehensible form.
Open the full interactive page →
Diagram, neighbourhood map, code examples, related patterns and full provenance.