A new customer handed us a large automation codebase and vague answers to our questions. I read through it, turned it into two diagrams, and circled every unknown in red. Those red circles became a list of questions the customer agreed to answer, and the answers made the design decisions possible. Here's how that worked.
The problem: vague answers, a lot of code
Every new project starts with discovery. You ask how the system works, what it needs, and who owns what. In government cloud, the first answers are often vague. That isn't anyone's fault. The people on the call may not have built the system. Data agreements may not be settled. Policy may still be moving.
On this call, the customer's real answer was their automation: an Ansible collection that builds and configures a Kubernetes platform. It created a lot of resources, and there was a lot of code behind it. It was the most accurate description of the system that existed.…