One YAML File Controls What Exists: A Developer's Hard Lesson in Service Manifests

A software engineer building Go microservices from a PHP monolith discovered that a newly written background worker never ran in production despite passing all local builds, tests, and pipeline checks. The root cause was simple: the service manifest, a single YAML file, had not been updated to declare the new binary, so the build system never compiled or deployed it. Because an absence generates no error or alert, every automated check passed without ever being asked about the missing component. The incident reinforced a strict architectural rule: a binary only exists in the environment if the manifest declares it, and adding new entry points requires explicit owner approval. The engineer now enforces a written prohibition against introducing new binaries outside of manifest declarations, ensuring all background work fits within already-declared daemons.