Liability surfacing at the point of action
A liability statement at the review checkpoint naming who is responsible if the agent's action contains errors.
At the moment an agent takes an action with legal or financial consequences, the citizen needs to understand who bears liability if it goes wrong.
The exposure could fall on the citizen for having delegated, on the agent provider that built and operated the agent, or on the government for accepting an agent-mediated submission, and these claims compete with no settled answer. Leaving the allocation ambiguous at this moment is harmful.
At the moment an agent takes a consequential action, the citizen sees a plain-language statement of who bears liability if it goes wrong: a pre-determined, disclosed allocation rather than one litigated after the fact.
Liability disclosures must be plain-language and not assume legal literacy. The statement appears at the review checkpoint in a citizen summary, with the full allocation expandable, so the citizen understands their exposure before authorizing the action.
The PSD2 'liability is pre-determined and disclosed before the transaction' rule becomes a plain-language liability line at the checkpoint: 'You are authorizing [agent] to [action]. If this contains errors, [allocation].'
No surface has been built yet; the approach above is the brief for one.
- Established Headline
Professional intermediary liability models are well-settled.
- Emerging
AI Act provider/deployer liability allocation is still taking shape.
- Frontier
Citizen-facing liability disclosure patterns for AI agent actions remain undesigned.
EU AI Act provider and deployer obligations. The AI Act distinguishes the provider of a system (who designs it) from the deployer (who uses it), each with distinct obligations on oversight, documentation, and risk management, an allocation designed to be surfaced rather than hidden. See PwC — EU AI Act.
PSD2 authentication liability shift. Under Strong Customer Authentication, liability for fraudulent transactions shifts depending on whether authentication was properly performed: if the merchant or payment provider fails to apply SCA, they bear the liability. This creates a clear, pre-determined framework understood before the transaction occurs. See Ravelin — PSD2 and merchants.
Tax agent lodgement responsibility. When a registered tax agent lodges on behalf of a client, the agent bears professional responsibility for the accuracy of the lodgement (subject to the information provided), and ATO systems record whether a return was self-lodged or agent-lodged. See ATO — Lodge your tax return.
The tax agent model is the closest analogue: a professional intermediary acting on delegated authority with defined professional responsibilities. For AI agents, the liability framework does not yet exist in most jurisdictions, but the interaction pattern should surface whatever framework applies.
At minimum, the review checkpoint should include a plain-language statement: "You are authorizing [agent] to [action]. If this contains errors, [liability allocation statement]." The PSD2 liability-shift model suggests the framework should be pre-determined and disclosed, not litigated after the fact.
The failure mode is no clear accountability for an incorrect automated decision, often with the onus of proof reversed onto the citizen. A disclosed liability allocation at the point of action makes accountability legible before harm occurs.
The worst case