Reversibility and undo
A reversibility badge at the authorization checkpoint classifying the action as reversible, amendable, compensable, or irreversible.
Agent actions differ in how far they can be undone. 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 citizen needs to understand the reversibility of an action before the agent takes it, and the system needs rollback mechanisms where reversal is possible.
Before an agent acts, the citizen is told whether the action is reversible, amendable, compensable, or irreversible. The classification is surfaced at the authorization checkpoint, with rollback mechanisms wired in where reversal is possible.
Reversibility signaling assumes understanding of administrative-law categories. The classification must be expressed in plain language at the review checkpoint, with the consequence of each category explained, so the citizen grasps the stakes before authorizing.
File your property tax relief application
You can correct this until your assessment issues. After that, you would lodge a formal objection.
- Established Headline
Compensating transactions in software and amendment processes in government are both well-established.
- Frontier
Reversibility signaling for agent-mediated government actions remains undesigned.
Compensating transaction pattern. In software engineering, a compensating transaction semantically undoes a completed transaction by executing the logical inverse (a "debit $100" is undone by "credit $100"). This works when the system models actions as events with inverse operations. See Wikipedia — Compensating transaction.
Tax return amendment process. Tax returns can be amended after lodgement within statutory time limits; the ATO allows amended returns that create a new version while preserving the original filing record. This is not a true "undo" but a "correct and re-submit": the original action remains on the record.
Recovery-oriented computing. System-wide undo support covering all aspects, including configuration and application management; the principle is that systems should be designed to support recovery from errors, not just prevent them. See Wikipedia — Recovery-oriented computing.
This is the hardest pattern to transfer. 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. 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 review checkpoint should clearly signal which category applies before the citizen authorizes the action. There is no established pattern for communicating reversibility of AI agent actions to citizens.
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 worst case