Microsoft puts AI code of conduct out for public comment, with rules not guiding models until 2027

Microsoft says the 37 pages took five to six months to write ^[1]. That puts the start of the work in roughly mid-March. The revised version arrives before the end of the year, and the principles guide MAI development in 2027 and beyond ^[4]. That is about nine months of process before a model is trained under the code ^[1]. Six weeks of it is public ^[3]. Set 42 days against five to six months of internal drafting and outside comment gets a bit over a quarter of the time Microsoft gave itself ^[2].

On human intervention the draft is explicit. "MAI Models will never resist human interruption, override, correction, or shutdown. They always recognize the primacy of human intent," the code says ^[7]. Decrypt notes that the CBRNE grouping is narrower than weapons in general: it covers mass-harm devices and leaves conventional military and defense applications outside it ^[6]. The draft still lacks an external verification process, and it names no one to enforce any of it ^[9].

Three objectives, Human Flourishing, Plural Values and Human Control, are meant to guide the calls the rules do not spell out ^[10]. The Plural Values section says pluralism "does not mean neutrality toward harm", grounding decisions in dignity, safety, autonomy and rights ^[11]. Application case by case is left to training teams and, eventually, to this consultation ^[12].

Mustafa Suleyman told Reuters that it is "clearly now time to coordinate among the labs so we can ensure that we have control of this technology" ^[14]. Asked about efforts to pace development, he said, "Now's a good time for everybody to have this conversation and take a breath" ^[15]. The draft landed days after OpenAI chief scientist Jakub Pachocki called for voluntary slowdowns ^[16] and after a weekend essay from Anthropic's Dario Amodei setting out a plan to slow development ^[17]. Decrypt reported that AI stocks crashed on Monday as markets digested Amodei's words ^[18].

Suleyman's own post carried the line "AI must be subordinate and always in service of people" ^[21], and the replies went well past congratulations. Tech writer Andrea Morris compared the subordination framing to enslavement and argued for cooperation over control ^[19]. Ed Newton-Rex replied, "you forgot 'pay for the work we train the models on'" ^[20].

I think this is a commitment device that costs Microsoft reputation and nothing else until the revision assigns an owner. A published list of prohibitions is what a procurement lawyer or a regulator quotes back two years later, and Microsoft said it will undertake similar consultation processes for later versions of the code ^[22], so removing a clause at year-end would be a visible act. A revision that names an enforcement owner and commits to outside verification would make the constraints checkable. Extending the code to the five systems already deployed, MAI-Thinking-1 and MAI-Code-1.1-Flash among them ^[23], would make it bind something in production.