Reversibility and undo
A label on every agent action for how much of it can be walked back: reversible, amendable, compensable, or irreversible. A user learns that an action can't be undone while there is still time to decline it.
The impact of agents
The more government actions agents take on a user's behalf, the more of what they do will land on the irreversible side of the line before the user has had a chance to weigh in. Some government actions (lodging a tax return, filing a form) can be amended. Others (paying a fee, submitting a statutory declaration) cannot be simply reversed. The user needs to understand the reversibility of an action before the agent takes it.
What must be verified
The reversibility classification assigned to an action must be accurate before the agent is allowed to proceed on it: telling a user an irreversible action can be undone is worse than giving no classification at all. The agency that owns the action must verify the classification before the checkpoint shows it to the user.
Protecting access
A user who misses the warning or does not fully grasp it is left holding the consequence of an action that cannot be undone. A user authorizing under time pressure, reading the badge through a screen reader, or reading the service in a language other than the one the badge is written in, must grasp that 'irreversible' means this exact consequence. If they don't, the consequence lands the moment the action is taken.
Keeping the path open
- Express the classification in plain language with the consequence attached: 'this can be amended within 28 days', 'this cannot be undone'.
- Never signal reversibility by color alone.
- Make the badge readable by assistive technology, legible at high zoom, translated into the user's preferred language, and stated in words wherever it appears.
Response surface
An action's legal reversibility is shown as a plain-language badge before the user authorizes the agent to take it.
File your property tax relief application
You can correct this until your assessment issues. After that, you would lodge a formal objection.
Maturity
- Established
For compensating transactions in software, a long-documented architecture pattern, and amendment processes in government such as tax return corrections: the latter now anchored to the ATO's own amendment process and its statutory time limits, the software side still resting on architecture guidance and research rather than a deployment record.
- Frontier Headline
For reversibility signaling on agent-mediated government actions, which remains undesigned.
Precedents
The compensating transaction pattern (Azure Architecture Center). A compensating transaction semantically undoes a completed one by executing its logical inverse, so a debit of one hundred is undone by a credit of one hundred. It works where the system models actions as events with inverse operations.
Recovery-oriented computing, Patterson et al. Patterson and colleagues argue for system-wide undo covering configuration and application management, on the principle that systems should be designed to recover from errors and not only to prevent them. Recovery is treated as a first-class design target.
Amending an Australian tax return. A return can be amended after lodgment within statutory time limits, producing a corrected version while the original filing stays on the record. The ATO documents the request route, the time limits, and the before-you-amend steps. It is correct-and-resubmit, and the original action is never removed.
Submissions to an Australian House committee, the counter-case. Once a submission to a House of Representatives committee inquiry is accepted it is protected from legal action for its content and cannot be withdrawn or altered without the committee's permission, with a supplementary submission the route for adding material. Some records lock on lodgment by design.
What carries over to agent use
Government actions have real-world consequences that cannot always be compensated: a benefit payment to the wrong account, a statutory deadline missed by an erroneous filing, a privacy breach from an agent disclosing to the wrong service. Of every pattern in the library, this one transfers least cleanly. The pattern library should categorize agent actions by reversibility:
- Fully reversible: draft saved but not submitted; form pre-filled but not lodged.
- Amendable: filed but correctable within a window (tax amendments, change of details).
- Compensable: cannot be undone but can be offset (an overpayment can be refunded).
- Irreversible: cannot be undone (statutory declarations, privacy disclosures, missed deadlines).
The compensating-transaction pattern proves that reversibility can be modeled and executed system-side; it says nothing about how that classification should be communicated to a user before they authorize the action. That user-facing half of the pattern has to be designed fresh, not adapted from the software original.
Where things go wrong
Where this goes wrong is a reversal process so protracted and burdensome that even determinations identified as incorrect persist. Pre-signaling notices as 'amendable' with a streamlined correction path reduces that harm. The badge itself can mislead: an agent or agency that labels an irreversible action as amendable, whether by error or to move the user past hesitation, obtains the authorization without the user ever weighing the actual consequence.
Sources
5 references
The instrument, the operating deployment, or the official record itself.
-
Amershi et al. — Guidelines for Human-AI Interaction (CHI 2019)
Guideline G9, 'Support efficient correction': make it easy to edit, refine, or recover when the system is wrong. A peer-reviewed anchor for the user-facing correction affordance, distinct from the backend recovery mechanisms the other sources here describe. Validated against 2018-era, non-agentic interfaces.
- Amend your tax return — Australian Taxation Office
- Making a submission to a committee inquiry — aph.gov.au
Writing about the subject rather than the framework itself, including vendor commentary.