Standards governance
Doctrine posts on who owns the standards that decide whose content is trusted. The technical detail can be excellent and the governance can still be broken.
Most conversations about standards focus on the technical specification. Which fields, which signatures, which file format. Almost nobody asks the question that determines whether a standard will still mean what it says in five years: who owns it. This set examines the structural failure modes and states how MX is governed differently.
The CMS industry is currently learning this lesson the expensive way. These posts are written for buyers, agency leaders, and platform strategists who have to price the governance risk into their decisions before the next dispute starts.
Doctrine posts
Each post argues a principle first, then tests it against live cases, then names what the failure looks like in practice. Read in order as posts are added.
1. Whose Standard Is It Anyway?
Records provenance is too important to belong to vendors whose products generate the records. The WordPress kill-switch story, the three structural failure modes it reveals, and the test buyers should apply to any standard that claims to be open.
2. Not the Main Sponsor
A founder's commitment, with the trigger condition stated. Why DDT Ltd caps at the same 25% as every other Founding Partner, and what changes the day The Gathering is fully funded by sponsorship.
3. A Rule You Sell Is Not a Standard
When the company that profits from the verdict also writes the rule, the rule bends toward the product. AMP and OOXML as worked failure modes, the IETF as the working alternative, and why the MX standard sits with The Gathering, not the vendor that sells the audit.
4. The Spec Was Never the Fragile Part
JPEG was threatened twice in thirty years while the specification never changed: once by a patent beneath it, once by a browser that switched off its successor. The fragile parts of a standard are the patents below it and the distribution above it.
5. Neither Code nor Content
FAIR governs code, MX governs content, and a trained model's weights are neither. The signature for a weights file is arriving from the code side; the readable, attested provenance record is the gap MX fits.
6. The Badge and the Body
The moment someone says compliant, two powers are in play: the definition of passing, and the business of selling the pass. Keep them in the same hands and the badge stops meaning anything. Why MX keeps the scoring definition with The Gathering and the audit with REGINALD.
7. Capture Happens at Version Two
A standard is rarely taken at version one, when everyone is watching. It is taken at the next version, by whoever controls what the standard becomes and who is allowed to extend it. Why MX keeps change control with The Gathering.
8. Two Implementations or It Isn't a Standard
A specification with one implementation is not a standard; it is that program's documentation, and whoever owns the program owns the rule. The COG specification has a JavaScript reference and an independent Rust implementation that interoperate.
9. Exit Is the Only Real Vote
The ultimate check on whoever holds a standard is the community's ability to leave and have the fork survive. Terraform to OpenTofu, Redis to Valkey. MX is forkable by design, with no owner positioned to betray.
10. When the Law Points at Your Standard
The moment a regulator names a standard as the route to compliance, the body that holds it begins to write the law. Harmonised standards under Europe's AI rules show the power and the hazard. For MX, being pointed at by law would be a responsibility, not a prize.