Ruslan Akchurin https://ruslanakchurin.dev/ 2026-06-25T00:00:00Z Ruslan Akchurin Start with the shape https://ruslanakchurin.dev/blog/making-iac-boring/01-shape 2026-06-25T00:00:00Z 2026-05-17T00:00:00Z By the time anyone reviews an IaC codebase, its shape is already decided. Resolve by contract https://ruslanakchurin.dev/blog/making-iac-boring/02-contract 2026-06-25T00:00:00Z 2026-05-19T00:00:00Z Cross-stack dependencies make another stack's outputs a public interface. A typed contract on a producer namespace and key is the alternative. Define tier membership https://ruslanakchurin.dev/blog/making-iac-boring/03-membership 2026-06-25T00:00:00Z 2026-05-24T00:00:00Z Environment boundaries blur when workload-specific members (service accounts, IAM bindings, DNS records) accumulate in the shared environment tier. Fail before apply https://ruslanakchurin.dev/blog/making-iac-boring/04-fail-before-apply 2026-06-25T00:00:00Z 2026-06-07T00:00:00Z An IaC contract holds only if the release path enforces it: a resolver checks type and context, then refuses invalid composition before apply. Re-cut the system https://ruslanakchurin.dev/blog/making-iac-boring/05-re-cut-the-system 2026-06-25T00:00:00Z 2026-06-24T00:00:00Z Refactoring a live IaC system toward a new architecture: freeze the old boundary, publish the new contract beside it, delete only after consumers move. Appendix A: The shape, runnable https://ruslanakchurin.dev/blog/making-iac-boring/appendix-a 2026-06-25T00:00:00Z 2026-06-25T00:00:00Z A companion repository makes the series architecture executable: four tiers, typed cross-tier contracts, and resolver probes that refuse bad composition before any provider call.