> Markdown copy of [https://aimaturitymodels.com/strata/](https://aimaturitymodels.com/strata/), generated at build time: a rendering, not a source of truth. Map: [/strata/llms.txt](/strata/llms.txt). Site map: [/llms.txt](/llms.txt).

# Strata — the architectural governance plane (S0–S7)

AI coding agents need a disciplined conceptual world that defines what kinds of things may exist, where they belong, what intent they realize, and what authority allows them to act. Type it, locate it, and resolve what it's for — before it acts, not after.

### S0. Intent — Why the practice exists

The originating motivation for the practice — ineffable until it's actually elucidated. Not itself a governed artifact until expressed; everything below exists in service of it. Intent is also not a label attached to architecture afterward: every valid governed thing must resolve to the Intent it exists to realize.

### S1. Fundamentum — Principles, constraints, and charters

The first governed expression of Intent. Principles and foundational constraints that rarely change, together with the charters defining what actors — including AI colleagues — are authorized to do. These are generated from Intent, not selected independently and rationalized afterward.

### S2. Normae — Adopted frameworks, standards, and maturity models

The standards against which the practice chooses to govern or measure itself. Adopted, not generated from first principles — selected because they serve the Intent and Fundamentum already established. The AI-Native maturity models in this family are examples; TOGAF® is another. A standard can therefore be entirely legitimate and still be wrong for a practice, if it doesn't serve that practice's Intent.

### S3. Vocabula — Shared language: ontology, taxonomy, lexicon, semantics

The shared language that makes governance checkable — what the practice means by a term, what kinds of entities exist, how they're classified, and which distinctions must stay distinct. This is what lets a human and an AI system inspect the same governed record and recognize the same kind of thing. Without it, governance stays dependent on interpretation.

### S4. Corpus — The governed record

The official archive of the practice. Corpus answers what is part of the record. It does not answer what is in force — a document can sit in the Corpus without possessing authority. Membership establishes that something belongs to the governed record; it doesn't enact, approve, or operationalize what the artifact says. Recorded is not the same as authorized.

### S5. Auctoritas — Authorization, contracts, and briefs

The machinery by which governed work becomes sanctioned — where permission becomes real. A draft authorization is not authorization merely because its text says "approved"; the constitutive act, issuance by the proper authority, is what changes its status. This is the difference between a record describing authority and authority actually having been exercised.

### S6. Operationes — Live systems, tools, and execution

The running practice: systems execute, tools act, processes run, agents perform work, and authorized decisions affect the world. Correct placement here does not itself authorize an action — a system can be well described, correctly classified, and traceable to Intent while still lacking authority for a particular consequential act. Well-formed is not the same as permitted.

### S7. Observatio — Reports, gaps, results, feedback

What operation teaches the practice — the evidence produced when architecture meets reality: results, exceptions, failures, measurements, gaps, and lessons. Those observations may justify changes elsewhere in the governed world, and at the deepest level may challenge the Intent the practice set out to realize. That is feedback, and it returns to the stratum it bears on — Intent among them, rarely. Naming that stratum is part of the claim.

**S2/Normae, concretely:** the AI-Native SDLC Maturity Model (/models/sdlc/whole-model-view/) is itself an instance of this layer — an external standard this practice measures itself against, adopted rather than generated. TOGAF® is another. Recognizing that placement is exactly the discipline instructions S1–S4 ask of you for your own proposed work.

**Fiber and feedback are different.** The intent fiber is not a loop — it is present throughout every valid descent from S0 to S7; a governed thing without a resolved intent reference is ill-typed at any stratum, not just at the ends. Feedback is a separate, additional claim: S7 (Observatio) returns findings to the stratum they bear on — Intent among them, rarely — and naming that stratum is part of the claim (`SPEC-STRATA` v2.4). A stratum can carry the fiber correctly with no feedback event having happened yet; feedback, when it does happen, still has to carry its own resolved intent reference to be real, the same as everything else.