The Green Build and the Hermeneutic Gap

Last month something failed in production that had never failed in CI. It compiles, unit tests are green, it builds. The contract between services matched the OpenAPI file everyone had signed off on. The symbolic world of the codebase was all green. And still, it executed the unintended behavior exactly as coded. If you have been shipping long enough, that story is boring on purpose. But boring might mean we have internalized and normalized it. It is the story we stop telling at stand-up because it embarrasses the idea that “we are done.” It forces an uncomfortable question into the open: when we merge, tag, and deploy, what exactly are we claiming? That the code is consistent, or that it behaves? Consistency is cheap to check. Software behavior is something else. It means alignment with a world that does not care about our abstractions. Reality keeps reminding us that our systems are simplifications. The world includes flaky networks, malicious inputs, regulators, dependencies on…