Overview
AI9GM (ai9gm.com) is the AI-Centric IT Governance Model — an open framework for governing AI deployment across an enterprise. It organizes governance into six interdependent layers — Foundation, Structural, Intelligence, Governance, Execution, and Strategic — and presents itself not as a single document but as an ecosystem: an open standard surrounded by a community, a knowledge base, and an implementation network. It is a meta-framework that extends established standards such as COBIT, ITIL, and ISO into the AI era rather than replacing them.
AI9GM and StrataProtocol.org were built in parallel, on the same Nuxt and Docus documentation stack, and the two informed each other directly: the Docus portal pattern that AI9GM proved out fed the starter specification this platform is built on. That parallel is part of the case it makes.
Classification: Class 1.3 — Platformization
AI9GM is classified Class 1, Category 1.3 — Platformization — the same category as StrataProtocol.org. The work was not inventing an unproven product; it was taking a governance model refined through practice and converting it into an accessible, externally-facing standard with a surrounding ecosystem. That is the defining move of Platformization: a validated capability becomes a public, reusable platform — here, a governance model becomes an open framework with documentation, a community, and certified implementation partners.
Technology Stack
| Concern | Choice |
|---|---|
| Documentation platform | Nuxt with Docus — the same @nuxt/content and Nuxt UI foundation that powers StrataProtocol.org |
| Shared foundation | The Docus portal pattern the two projects converged on, later captured as a reusable starter specification |
STRATA Principles Observed
AI9GM is unusual among these cases: its very subject is layered governance, so the parallel with STRATA is structural, not just methodological.
- A layered governance model — AI9GM's six interdependent layers mirror STRATA's stratum model. Both answer the same instinct: governance fails when its concerns are tangled, and holds when they are layered so each builds on the one beneath it.
- A platformized ecosystem — the Framework → Community → Knowledge → Implementation tiers are Platformization done correctly: a standard at the center, with the surrounding systems that turn it from a document into a living, adopted framework.
- Self-documenting by design — the governance framework for AI is itself documented to a best-in-class standard, on the same Docus discipline this platform uses, so the published model is also the record of how it is structured and why.
What STRATA Would Have Formalized
AI9GM was self-documenting by design, but its construction discipline lived in practice rather than in a named protocol. STRATA would make that explicit: a written Classification Record fixing the platformization stance, a derivation chain from strategic vision down through the governance layers, and a five-stratum artifact trail capturing how the framework itself was built — not only what it prescribes. The model already taught governance; STRATA would have governed its own delivery the same way this platform does. See the Execution Loop for that discipline in formal terms.
Go deeper than the summary
Case Studies
Real-world projects governed by the full five-stratum STRATA sequence — across varied classes, stacks, and domains, including the early implementations that shaped the protocol before it was formally specified.
Full Case Study
The complete reading of AI9GM through the five strata — classification, derivation, authority chain, execution loop, and artifact trail — a Class 1.3 enterprise AI-governance framework built on the same Nuxt and Docus stack as StrataProtocol.org.

