Confirm changes
Step · Stable
Pause the flow and surface a confirm card in the inbox for a human to review. The run resumes after the human confirms, edits, or declines. Use {{ label.decision }} to branch on the outcome.
Places a deliberate human-review gate in a flow. Unlike the automatic JIT reversibility gate (which fires only when input was auto-applied), this step always pauses — the flow author chooses when to ask for review. The human sees the confirm card from the proposal identified by proposal_id in their inbox bell panel. After the decision the run continues; branch on {{ label.decision }} (confirm / edit / decline) for post-decision routing.
When to use
Section titled “When to use”Use when a flow should always wait for explicit human review of a proposal before proceeding — e.g. after AI extracts changes from a document, surface them for approval before writing to the substrate.
When not to use
Section titled “When not to use”Do not use for general human questions — use Ask a person instead. If you only need a guard on irreversible actions on auto-applied data, the automatic JIT gate (ROU-213) fires without an explicit step.
Inputs
Section titled “Inputs”Configured per use: proposal_id, title, hint.
Outputs
Section titled “Outputs”Auto-generated from the skill registry (load_skills()). Do not edit by hand.