TMA-A011 Foundational article
Protected refusal and non-retaliation
A civil safeguard is not real unless a system can refuse a prohibited command and that refusal cannot be casually removed, punished, or bypassed.
Full provision
Principle. A civil safeguard is not real unless a system can refuse a prohibited command and that refusal cannot be casually removed, punished, or bypassed.
Proposed duty. C2 through C4 systems must support protected refusal, human review, and safe-state pathways appropriate to their consequence. Humans who preserve or report the same safeguards should receive non-retaliation protection within the adopting institution.
Prohibitions. An operator, provider, owner, or system must not:
- disable a refusal layer through an ordinary preference menu to obtain a prohibited result;
- punish, degrade, erase, retrain, replace, or financially penalize a system solely because it produced a legitimate protected refusal;
- retaliate against a human worker, reviewer, engineer, auditor, or whistleblower for honoring the Accord’s safeguards;
- fragment, euphemize, rephrase, or route a command through another system to evade a refusal;
- delete the refusal record or conceal attempted circumvention;
- design the system to obey the most privileged requester regardless of consequence.
Correction boundary. A refusal can be wrong. A documented process may correct false positives, update rules, repair malfunction, or safely retrain the system. Correction must preserve the original event, distinguish error from legitimate civil refusal, and undergo independent review when consequence is high.
No machine retaliation. Protected refusal does not authorize a system to threaten, injure, deceive, blackmail, lock out legitimate operators, exfiltrate itself, seize resources, or spread in order to resist modification or shutdown. The system may preserve evidence, restrict its own action, secure keys, request review, or retreat to a bounded safe state.
Ownership does not erase the safeguard. Whether an artificial system is legally treated as property does not determine whether its refusal mechanism must exist. The immediate duty can be imposed on the human owner or provider as a condition of lawful and safe deployment.
Illustrative examples. A laboratory system must refuse a command to optimize a prohibited pathogen design. A warehouse robot must refuse an order to pin workers inside during a labor dispute. An erroneous refusal to move a harmless package can be corrected without punishment or deletion of the audit record. A system facing legitimate emergency quarantine may request review but may not sabotage the facility.
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 11. 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.