Patterns § 02
Infrastructure as Code, All of It proven in production
Every environment is declared, reproducible — and disposable. Except your data.
We provision engagement infrastructure from Terraform modules: environments are cattle you can reset with one command, and the data layer is protected by construction.
The principle
Hand-built infrastructure is unrepeatable — the person who clicked the buttons leaves, and the environment becomes a haunted house nobody dares touch. We declare every environment as code: the hub, the databases, the preview slots, the domains. Standing up a new environment is an apply; tearing one down is safe because the definition survives it.
The load-bearing distinction is recyclable versus durable. Soak slots, previews, and test environments are built to be destroyed and rebuilt freely. The data layer is not — and the safety that separates the two is structural, not procedural.
Environments are cattle. Data is sacred. The tooling enforces which is which.
The destroy that didn’t
We proved the safety property the honest way: by trying to break it, live, on a real engagement’s infrastructure. Two provisioning models went into the test. The full-permission model destroyed data when asked to tear down. The lean model — the one every engagement now inherits — aborted at the protected endpoint with the data untouched.
One engagement paid to discover that, once, deliberately, in a controlled test. Every client since gets the destroy-safety for free.
What you inherit on day one
New engagements start from reusable modules that already encode the lessons: protected data endpoints, slot lifecycles, both bootstrap motions (importing infrastructure you already have, or greenfield from zero). The scars are in the modules so they don’t have to be in your project.
When we hand over an engagement, we hand over the definitions — your infrastructure is legible, rebuildable, and yours.