Start here
26 minutesWhat the category is, why description is not enough, and where the gap sits in a real stack.
The library
Everything the standard has published
24 open publications — the specification, the arguments behind it, and the instruments for applying it. Every one is readable in full on this site and downloadable in the formats it exists in. All CC BY 4.0.
Start with a sequenceEach path is three or four documents in a stated order, with the reason for that order.
You are evaluating AIOps
26 minutes- AIOps Is an Operating-Model Problem
- Representation Is Not Authority
- Why AI Needs an Infrastructure Operating Model
Why observability cannot close the gap, and what has to exist instead.
You already have the tools
23 minutes- Twelve Tools, One Missing Layer
- IaC Declares How. An IOM Declares What’s Allowed.
- Frameworks Describe. Something Must Govern.
The same argument against three categories you have already bought.
You are an analyst
21 minutesThe category thesis, its normative definition, and the two failure modes it names.
Browse by kind
Browse by theme
Normative · Specification
Enterprise Architecture · Governance
Foundations · Reference Architecture
Category Architecture · Foundations
AI Governance · Foundations
AI Governance
Analysis · Build vs. Buy
AI Governance · Category Architecture
Enterprise Architecture · Governance
AI Governance · Security · Zero Trust
Adoption · Reference Architecture
AI Governance · AIOps · Observability
Infrastructure as Code · Platform Engineering
Conformance · Governance
Adoption · Assessment
AI Governance 5
Foundations 3
Governance 3
Category Architecture 2
Reference Architecture 2
Adoption 2
Enterprise Architecture 2
Platform Engineering 1
Conformance 1
Assessment 1
Zero Trust 1
Security 1
Standard
The IOM Standard v1.0
A vendor-neutral specification for the infrastructure authority layer.
Read → PDF DOCXWhitepaper
Aspirational Architecture
TOGAF, golden paths, and infrastructure-as-code each declare intent, and each assumes something else will hold reality to it. Nothing validates a change against any of them before it runs.
Read → PDF DOCXModel Inversion
Operations infer intent from telemetry after the fact. Model Inversion reverses the direction, making an authoritative model the first input rather than the last conclusion.
Read → PDF DOCXThe Amalgamation Fallacy
Discovery, CMDBs, and telemetry each record what is. No amount of integration turns a description of the estate into a statement of what is allowed.
Read → PDF DOCXRepresentation Is Not Authority
Digital twins represent infrastructure; an Infrastructure Operating Model governs it. Why legitimacy — not fidelity — is the category boundary.
Read → PDFWhy AI Needs an Infrastructure Operating Model
AI-driven infrastructure stalls for structural reasons, not algorithmic ones. AI can see what exists, not what is legitimate — and autonomy needs legitimacy.
Read → PDFTwelve Tools, One Missing Layer
Approximating an IOM takes roughly a dozen platforms — but even one vendor shipping all twelve would not produce one. Authority is not an integration construct.
Read → PDFIntelligent Control Plane or Operating Model?
A smarter control plane improves how infrastructure executes; it cannot establish what it means, who owns it, or what it may do. Control is not authority.
Read → PDFFrameworks Describe. Something Must Govern.
TOGAF, Zachman, ArchiMate and SAFe describe architecture; none enforces it. Why EA needs an IOM authority layer to keep intent and reality reconciled.
Read → PDFSecurity Is an Operating-Model Problem
Security fails on static assumptions in a changing world; posture decays between scans. Why preventive security and Zero Trust need an IOM authority layer.
Read → PDFFrom Tool Aggregation to Infrastructure Authority
What an IOM is made of and how it is adopted — a phased, low-risk path that governs existing tools before execution, without replacing them.
Read → PDFAIOps Is an Operating-Model Problem
AIOps noise is not a model problem — telemetry records what happened, not what was intended. An IOM authority layer makes root cause deterministic.
Read → PDFIaC Declares How. An IOM Declares What’s Allowed.
Infrastructure as Code declares how to build; an Infrastructure Operating Model declares what is allowed — and validates the plan before it runs.
Read → PDFProcess
Conformance Submission
How an implementation is verified against the IOM Standard: what evidence is required, how it must be demonstrated, and what a listing in the conformance directory asserts.
Read →Starter Kit
The IOM Starter Kit
A working document for scoring IOM readiness across six capability dimensions, mapping existing tools to requirements, and planning adoption in four phases.
Read → PDF DOCXDiagram
Authority Layer Context
Read → PDF SVG PNG
Authority Layer Gate
Read → PDF SVG PNG
Authority Stack
Read → PDF SVG PNG
Eras Operating Models
Read → PDF SVG PNG
Five Eras
Read → PDF SVG PNG
Inference Vs Authority
Read → PDF SVG PNG
Maturity Climb
Read → PDF SVG PNG
Operating Loop
Read → PDF SVG PNG
Representation Vs Authority
Read → PDF SVG PNG
The library is also published as structured data, so it can be consulted rather than scraped: /documents/index
and /llms.txt.