The specification
The normative document implementations conform to. The whitepapers make the argument; the standard defines the requirements.
The IOM Standard
RFC 2119 conformance criteria — what an IOM must provide, what it explicitly does not, and how implementations are evaluated against the published standard.
Whitepapers
Eight vendor-neutral category papers in canonical reading order. Each draws one boundary; together they argue that authority is declared, not assembled.
Representation Is Not Authority
Against digital twins — a twin tells you what exists; only an IOM tells you what is legitimate.
Why AI Needs an Infrastructure Operating Model
The forcing function — every prior era kept a human in the loop to supply authority; AI removes that governor, so authority must be declared and machine-checkable.
Twelve Tools, One Missing Layer
Against the tool stack — even one vendor delivering all twelve capabilities would not produce an IOM. Aggregation is not authority.
Intelligent Control Plane or Operating Model?
Against the smart control plane — a smarter control plane improves how infrastructure executes; execution is not authorization.
Frameworks Describe. Something Must Govern.
Against EA frameworks — TOGAF, Zachman, ArchiMate describe architecture; description is not enforcement. Includes a TOGAF ADM mapping.
Security Is an Operating-Model Problem
Preventive security & Zero Trust — reconciling built state against running state turns drift from a forensic discovery into a preventable condition.
From Tool Aggregation to Infrastructure Authority
Adoption & reference architecture — what an IOM is made of, and the phased, low-risk path from read-only modeling to governed autonomy.
AIOps Is an Operating-Model Problem
AIOps grounded on an authority layer it consumes instead of inferring — correlation becomes intent-relative, noise collapses, root cause becomes deterministic.
Adoption
For teams ready to assess their own estate against the standard.
IOM Starter Kit
A practical guide to assessing your infrastructure-governance maturity, mapping existing tools against IOM requirements, and planning a structured adoption path.