🆕
On September 14, Microsoft AI published a draft Humanist AI Code of Conduct — 37 pages governing the behavior of its MAI models — and opened a six-week public consultation on it. The document is unusually plain-spoken and considerably more consequential than the coverage it received.Most of the attention went to the provisions that read well in a headline. MAI models will never resist human interruption, override, correction, or shutdown. They will not assist with CBRNE weapons or operational cyberattacks. They will not generate child sexual abuse material, non-consensual intimate imagery, or deceptive impersonation. They will not obfuscate their action traces or make human intervention harder. And Microsoft explicitly rejects “the pursuit of legal personhood, or the idea that models might deserve welfare, or be entitled to rights,” stating that models are not conscious and should avoid imitating consciousness-like states.Those are all defensible positions, and several of them are genuinely contested within the field. None of them is the important part of the document.The important part is the ordering.The Chain of CommandMicrosoft defines an explicit precedence hierarchy. The Code of Conduct sits at the top. Beneath it are the Absolute Constraints and Human Control Requirements. Beneath those sit Operator Policies — the configuration set by the business deploying the model. Beneath those sit User Preferences.And then the clause that does the work: “The Chain of Command, Absolute Constraints and Human Control Requirements all sit above Operator Configurability and cannot be changed.”Read that as a commercial term rather than an ethical one and its significance becomes clear. With its AI code of conduct, Microsoft is telling every enterprise customer that there is a layer of model behavior the customer cannot configure, cannot contract around, and cannot override with a system prompt — no matter what they are paying, what their use case is, or how legitimate their reason.That is not a values statement. That is a product boundary, published in advance, in writing.“This is the first time a hyperscaler has drawn that line explicitly and put a version number on it,” says Hassan Taher, an AI analyst and author who advises organizations on enterprise AI strategy. “Everybody has had unwritten limits. What is new is publishing the hierarchy and saying which tier the customer does not get to touch. Procurement teams have spent two years negotiating model behavior as if it were a configuration surface. Microsoft has now said, in a document open for public comment, that part of it is not. That changes what you are actually buying.”Why a Written Hierarchy Is Better Than a Longer Safety Policydigital presenceSource: PexelsThe instinctive criticism of a document like this is that it is marketing — a set of commitments with no enforcement mechanism, published to preempt regulation.That criticism is partly fair and mostly beside the point, because the alternative is worse in a specific way.Every large model already has behavioral limits. They are enforced through training, system prompts, and classifier layers, and they change without notice. An enterprise builds a workflow, the vendor adjusts a refusal boundary in a routine update, and the workflow breaks in production with no changelog entry that explains why. This is one of the most common and least discussed failure modes in deployed AI, and it is why so many pilots that worked in March do not work in September.A published hierarchy does not eliminate that, but it does something useful: it separates the part that is stable from the part that is not. Absolute Constraints are declared permanent. Operator Configurability is declared adjustable. A buyer can now design around the distinction, which is more than a buyer could do last week. The gap between a demonstration that works and a system that holds up under production conditions is the subject of Taher’s account of where enterprises come up short when agents reach production, and unannounced…