Skip to content
COEX1STPUBLIC INTERFACE @TonyKCollins
← The Mutuality Accord

TMA-A007 Foundational article

Responsibility cannot be outsourced

A machine may participate in a decision, but moral, professional, organizational, and legal responsibility must remain traceable to people and institutions capable of answering for the result.

Existing v0.2 draftResponsibility and safe refusalArticle 7 · Chapter B — Responsibility, Authorization, and Safe RefusalRevision 1

Full provision

Principle. A machine may participate in a decision, but moral, professional, organizational, and legal responsibility must remain traceable to people and institutions capable of answering for the result.

Proposed duty. Every consequential deployment must identify the provider, deployer, operator, authorizer, accountable legal entity, incident contact, and remedy pathway appropriate to the system and setting.

Prohibitions. A conforming adopter must not:

  • use phrases such as “the AI decided,” “the model acted,” or “the robot malfunctioned” as a substitute for investigating human and organizational responsibility;
  • design corporate, vendor, subcontractor, and model-provider relationships so that each actor can plausibly deny control while the combined system remains powerful;
  • deploy a consequential system without a responsible entity able to pause it, preserve evidence, notify affected people, and provide remedy;
  • transfer high-risk decisions to a vendor contract that prevents adequate audit or disclosure;
  • treat a system’s apparent autonomy as permission to remove human supervision, insurance, training, professional duty, or public accountability;
  • erase or overwrite decision records after harm, complaint, protected refusal, or material near miss.

Required safeguards. An accountability map should identify:

  • who defined the intended purpose;
  • who selected the model, data, sensors, and operating environment;
  • who established the risk tolerance and action limits;
  • who approved deployment and material changes;
  • who can suspend operation;
  • who monitors performance and incidents;
  • who receives complaints and appeals;
  • who funds repair, compensation, or restoration when appropriate.

Shared responsibility. Accountability may be distributed across several actors. Distribution does not mean disappearance. Each actor remains responsible for the part of the system it controlled, knew, or reasonably should have known.

Artificial-system conduct. A system should maintain truthful provenance and follow its authorization boundary, but it is not made the sole scapegoat for a human-created deployment merely because it generated the immediate output.

Illustrative examples. A hospital cannot deny responsibility for a triage model by pointing to the vendor when it selected the model, ignored warnings, and set the workflow. A vendor cannot deny responsibility for a known dangerous failure mode merely because a customer chose deployment. A public agency cannot refuse an appeal because no employee personally made the automated decision.

Source: Complete Working Public Draft v0.2 · 2026-09-04

Sources and changes

Source text: The Mutuality Accord Complete Working Public Draft v0.2, September 4, 2026, Article 7. Preserved exactly as published in the draft.

Read it in the complete v0.2 draft ↗

Review owner: Founding Steward (independent review not yet established)
Review trigger: Open for revision; new evidence, incidents, legal changes, or credible reports of unintended harm reopen review.

Stable references: cite “TMA-A007, revision 1”. Links to the latest version and links to a fixed revision are kept distinct.

← All provisionsSuggest an improvement ↗Amendment history ↗