Safety · research august 2026 · published 2026-08-03 · v3 · 2 min read · history
Who answers for an artifact that acts
Deployment does not move responsibility into the artifact
The liability question agentic systems force, the Air Canada ruling that previews the answer, and what operating as the answerable party requires. The canonical treatment of artifact accountability.
When a deployed system causes harm, responsibility can disappear into a familiar chorus. The builder says the deployer configured it. The deployer says the model behaved unexpectedly. The vendor’s terms assign the output to the user. Each party has a plausible story for why somebody else must answer.
When Air Canada’s website chatbot invented a bereavement-fare policy and a grieving customer relied on it, the airline argued that the chatbot was a separate legal entity responsible for its own statements. The British Columbia tribunal rejected the argument and held the airline responsible for information delivered through its website. The ruling involved a consumer tribunal and a modest sum, but its logic reaches further. The company chose to put the system in front of the public, presented it as speaking for the company, and benefited from its operation. The company therefore remained answerable for what happened.
The alternatives separate responsibility from the ability to act on it. Assigning liability to the artifact creates an uncollectable defendant. Assigning it to users burdens the party with the least visibility into the system. Assigning it to nobody subsidizes reckless deployment. The deployer is the address where control, benefit, and the power to change the system already meet.
Calling the chatbot an actor names what happened: it changed what a person believed and did. The label does not make the deployment somebody else’s responsibility. Giving a system more freedom increases the burden of control because the deployer chose to grant that freedom.
The operating posture follows directly. Bound what the system can do, record what it did, preserve a way to interrupt it, and name the person or institution that will answer for the result. The agency threshold names the action, the chosen means, the permission, and the answerer. This brick stays with the final field. A system may act, but the human answer does not disappear.
Evidence and lineage
Research trail
Follow the sources, inspect how the claims are graded, or propose a correction at the exact record it concerns.
Sources 1
-
Civil Resolution Tribunal of British Columbia (2024). Moffatt v. Air Canada (2024): the invented bereavement-fare policy
The ruling that rejected the separate-legal-entity argument and held the deployer answerable; the brick's anchor case.
Comment on this source
Claims and confidence 1
- verified
The BC tribunal held Air Canada responsible for its chatbot's invented bereavement policy, rejecting the 'separate legal entity' argument.
The tribunal's published decision and contemporaneous reporting.
Respond to this claim
Read next
You have walked Safety end to end, from the threshold to the courtroom: what an actor is, how assigned and learned objectives differ, what present evidence can establish, why promises fail, and the shapes that hold instead. Everything here is buildable now.
Practice Pick one system you operate or depend on and place it on the agency spectrum in writing: which of the four threshold criteria does it meet today, and which could it meet under pressure? Then find one rule in your life that works by asking for good behavior, and sketch what removing the path would look like instead.