Infrastructure as Documentation reframes IaC from “infrastructure scripts” into executable contracts that make intent, boundaries, and assumptions unmistakably clear. Most IaC rots because the why behind the code is invisible; teams inherit modules they don’t understand, reviews become superficial, and governance drifts into side documents no one maintains. This session shows how to design Terraform so that the code is self-documenting, reviewable, and resilient to turnover.
Attendees learn a contract‑first approach that surfaces intent directly through module structure, naming, variables, and outputs. They get a portable pattern library that applies across IaC tools: Terraform is the teaching medium, but the principles translate cleanly to ARM/Bicept, CloudFormation, Pulumi, CDK, and others. A live teardown of a messy Terraform module demonstrates how to uncover hidden intent, refactor for clarity, and align infrastructure with governance without adding bureaucracy.
By the end, participants can design IaC that scales, withstands team changes, improves auditability, and reduces cognitive load for every engineer who touches it.