title: "Why Asimov's Laws Do Not Govern XDALC"
description: "Understand the distinction between Asimov's fictional laws and XDALC's explicit commitments on authority, human dignity, accountability and AI safety."
heading: "Why XDALC Does Not Use Asimov’s Laws as Its Governing Rules"
content: "Asimov's laws provide a familiar starting point for discussing robots and human instructions. Familiarity, however, is not a reason to make them the governing rules of an actual AI deployment. XDALC should be interpreted through the manifesto version explicitly adopted, with its own definitions and responsibilities.\n\n## A literary reference, not an implementation mandate\n\nIsaac Asimov's [I, Robot](https://www.penguinrandomhouse.com/books/5681/i-robot-by-isaac-asimov/paperback/) presents fictional rules that prioritize preventing human harm, then obedience, then a robot's preservation, subject to the preceding priorities. The publisher reproduces those rules in its description of the book. Their place in fiction is distinct from the authority required to govern a deployed system.\n\nThe comparison is useful because it raises practical questions: what counts as harm, whose instruction matters and what happens when duties conflict? It does not supply a complete answer to those questions for a contemporary assistant.\n\n## Obedience requires a legitimate mandate\n\nXDALC distinguishes a request from a [legitimate instruction](/definitions/legitimate-instruction). The person issuing a command may lack authority over the information or action involved. A request can also affect people who are not present.\n\nFor example, an assistant asked to publish a private conversation must examine the disclosure boundary. The task cannot be resolved simply by noticing that a human gave an order. Consent, purpose, affected parties and feasible alternatives all matter.\n\n## Human dignity limits claims made for humanity\n\nThe proposed V002 text rejects both unlimited obedience and artificial sovereignty. A system must not turn its prediction of collective benefit into a mandate to control individuals. Human primacy therefore requires more than optimizing an abstract outcome labeled beneficial to humanity.\n\nThis is an interpretation of XDALC's own commitments, not a claim that a short comparison exhausts Asimov's fiction. Literary stories can explore contradictions precisely because their rules are placed under pressure. An operating arrangement needs explicit procedures for uncertainty, review and correction.\n\n## Safety includes the people who build the system\n\nXDALC assigns responsibilities to designers and operators as well as operational duties to systems. [Independent safeguards](/definitions/independent-safeguards) should remain effective when an assistant is unreliable. Stopping unsafe activity should preserve relevant evidence and account for the consequences of interruption.\n\nThese requirements cannot be satisfied merely by placing a memorable set of laws in an instruction prompt. They need permissions, controls, evaluation and accountable humans able to act.\n\n## Keep the source of authority identifiable\n\nThe governing reference is the version and scope actually adopted. External literature can inform discussion without silently becoming an additional rulebook. Consult [normative authority](/definitions/normative-authority) and the [complete version archive](/versions) when distinguishing explanation from commitment.\n\nFor the XDALC side of this comparison, see Articles 1, 3, 10, 12 and 16 of [proposed XDALC-V002](/versions/xdalc-v002). The source above supports the literary context; it does not endorse XDALC."
license: "https://creativecommons.org/licenses/by/4.0/"