{
  "schema": "org-writing@v1",
  "slug": "who-answers-for-an-artifact",
  "kg": {
    "id": "org:writing:who-answers-for-an-artifact",
    "type": "brick",
    "graph": "/kg.json"
  },
  "title": "Who answers for an artifact that acts",
  "subtitle": "Deployment does not move responsibility into the artifact",
  "abstract": "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.",
  "kind": "brick",
  "topics": [
    "Safety"
  ],
  "courseMemberships": [
    {
      "course": "org:courses:safety",
      "topic": "Safety",
      "wall": "org:walls:engineering",
      "position": 11,
      "total": 11
    }
  ],
  "publishedAt": "2026-08-03T00:00:00.000Z",
  "updatedAt": "2026-08-20T00:00:00.000Z",
  "version": 3,
  "guidelinesVersion": 16,
  "brief": {
    "problem": {
      "text": "When a deployed system causes harm, builders, deployers, vendors, and users can each offer a plausible story for why somebody else must answer.",
      "claims": [
        "The BC tribunal held Air Canada responsible"
      ]
    },
    "mechanism": {
      "text": "Responsibility follows deployment because the deployer chose to put the system in front of people, controls its reach, and benefits from its operation.",
      "claims": [
        "The BC tribunal held Air Canada responsible"
      ]
    },
    "move": {
      "text": "Treat every consequential system action as conduct the deployer must be prepared to bound, record, interrupt, and answer for.",
      "claims": []
    }
  },
  "sources": [
    {
      "repo": "mnstry-org",
      "path": "src/content/writing/the-agency-threshold.md"
    }
  ],
  "canonicalPath": "/writing/who-answers-for-an-artifact/",
  "body": "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.\n\nWhen 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.\n\nThe 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.\n\nCalling 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.\n\nThe 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.",
  "apparatus": {
    "note": "The human-facing essay is deliberately practical; this apparatus carries the full references, evidence-graded claims, article-local concepts, and research context behind it. Canonical concept definitions come from the concept registry.",
    "references": [
      {
        "id": "org:references:who-answers-for-an-artifact:r01",
        "author": "Civil Resolution Tribunal of British Columbia",
        "work": "Moffatt v. Air Canada (2024): the invented bereavement-fare policy",
        "year": 2024,
        "relevance": "The ruling that rejected the separate-legal-entity argument and held the deployer answerable; the brick's anchor case."
      }
    ],
    "claims": [
      {
        "id": "org:claims:who-answers-for-an-artifact:c01",
        "claim": "The BC tribunal held Air Canada responsible for its chatbot's invented bereavement policy, rejecting the 'separate legal entity' argument.",
        "basis": "The tribunal's published decision and contemporaneous reporting.",
        "confidence": "verified",
        "sources": []
      }
    ],
    "concepts": [],
    "researchContext": "Extracted from \"The agency threshold,\" which keeps the narrative version. The\nsingle claim is restated from the essay's apparatus and retains its earlier\ngrade. This brick owns the answerability question: actorhood names the action,\nbut it does not transfer responsibility away from the person or institution\nthat deployed the system."
  },
  "contract": "https://mnstry.org/contracts/org/org-writing.v1.schema.json",
  "releaseHash": "3c046226a0ad1abffb9c6b13f38920baa1f68998e95a18ee5f1be19ec486bf85",
  "versions": [
    {
      "version": 3,
      "cutAt": "2026-08-20",
      "note": "Founder-approved agency-threshold semantic migration",
      "visibility": "published",
      "path": "/writing/who-answers-for-an-artifact/",
      "contentHash": "sha256:3b8a8ac0cded79fc",
      "releaseHash": "3c046226a0ad1abffb9c6b13f38920baa1f68998e95a18ee5f1be19ec486bf85"
    },
    {
      "version": 2,
      "cutAt": "2026-08-03",
      "note": "Courses wave (operator-ratified): ending rewritten to ascend into the doors; the lift lands on the next threshold.",
      "visibility": "published",
      "path": "/writing/who-answers-for-an-artifact/v/2/",
      "contentHash": "sha256:ca5126335a9ec23f"
    },
    {
      "version": 1,
      "cutAt": "2026-08-03",
      "note": "Final brick wave: canonical treatment extracted under ontology v5 by operator instruction.",
      "visibility": "published",
      "path": "/writing/who-answers-for-an-artifact/v/1/",
      "contentHash": "sha256:fc1220acc7884f22"
    }
  ]
}