The MAI-Meta Foundation a constitution, not a configuration file
The law the agents cannot amend.
The Foundation holds the law: what may be done, by whom, and how compliance is proven. MAiFactory holds the work: the team, the project, the repository. Agents reside in the Factory and cannot amend the law they operate under.
01 — Why the Factory is governed
Nobody authorized that change.
Ask anyone who has shipped real work with an AI assistant whether it has ever rewritten something they did not ask it to touch. The agent reopened code from an earlier session, decided it was too complex, and improved it. Nobody authorized that. Nothing recorded it.
Alongside it sits the rest of what single-agent work carries: drift, hallucination, and confident agreement with whatever it was told last.
Self-review does not provide independent assurance. An agent checking its own output grades it against the same assumptions that produced it, so its blind spots stay blind.
A better prompt does not fix that. Separated duties and reviewers from a different provider family do.
02 — What governs the Factory
The MAI-Meta Foundation.
A constitution, not a configuration file
The Foundation holds the law: what may be done, by whom, and how compliance is proven. MAiFactory holds the work: the team, the project, the repository. Agents reside in the Factory and cannot amend the law they operate under.
It specifies what each role may and may not do, that producing and clearing authority never sit with the same role, that governance decisions require different provider families, what happens when a conflict cannot be resolved, and that no artifact is ever modified in place.
The Principal holds all ultimate authority. Agents operate under the Foundation; the Foundation operates under the Principal.
Like any constitution, it amends — proposed openly, reviewed by a role that did not draft it, released as a new version with a new hash, every prior version still readable.
Agents may propose. Only the Principal enacts. The seal never breaks — it advances.
Not tied to one project or repository. A new project inherits the control model without inheriting stale assumptions.
Governs agents across the Anthropic, Google and OpenAI provider families, and survives any one of them being replaced.
The Foundation stays separate from the teams, tools and project surfaces it governs. Teams and implementations can change without changing the constitutional source.
03 — The MAI-Meta Articles
Seven rules binding every team in every Factory.
Enforced, not suggested
Producing authority and clearing authority are never held by the same role over the same artifact.
Governance decisions require agents from different provider families, so correlated blind spots have nowhere to hide.
Agents separate what was verified from what was assumed, cite the source, and do not agree confidently without one.
Every approval binds to a versioned artifact and its content hash. Nothing is edited in place.
Ambiguity that matters halts the work and surfaces to the Principal. The system does not guess through disagreement.
Work found unreliable is marked inadmissible, its trace preserved, and rebuilt from clean authority.
Authority never shifts without someone authorizing the shift.
Agents may propose. Only the Principal enacts. The seal never breaks — it advances.