Irreversible actions
Redesign irreversible actions so a responsible person owns the final transition.
Purpose
Redesign irreversible actions so a responsible person owns the final transition. The workflow is acceptable only while its evidence, permission, review, and stop boundaries remain true.
Prerequisites
- A named owner and reviewer for the irreversible actions workflow.
- An approved data and tool environment.
- Written acceptance criteria and a representative evaluation set.
- A clear action boundary, including what the system must never do.
Procedure
- Separate preparation from execution.
- Stage evidence and show the exact consequence.
- Require explicit qualified approval or keep execution entirely human.
Evidence and review
For irreversible actions, keep the source material, proposed output or action preview, validation results, reviewer decision, and final outcome connected. Use sampling only when its rule and escalation threshold are written before use.
Stop and escalation
- Do not infer approval from silence.
- Do not use bounded action when rollback is impossible and consequence is material.
Stop this irreversible actions workflow on unexpected sensitive data, conflicting authoritative evidence, permission expansion, repeated failure, or any result that the named reviewer cannot verify. Send the evidence package to the escalation owner instead of continuing with a guess.
