DriftLens — From Incident to Release Gate

A service can work on one developer’s machine and still fail at release because a required environment variable is missing from setup instructions or deployment configuration. Finding the cause often means manually comparing source code, configuration files, and error logs. The same mistake can then recur in the next release. DriftLens is a prototype for developers and small teams who need a clear release decision. It compares required settings across a contract, application source, `.env.example`, and `compose.yaml`. In our sample checkout service, the code requires `PAYMENT_API_KEY`, but both developer setup and deployment omit it. DriftLens identifies the two exact gaps and returns HOLD RELEASE with actionable findings. The workflow goes beyond detection. The team can connect an incident to the missing setting, inspect the affected files, preview a suggested repair, and run the check again. In the demo, two static blockers become zero and the verdict changes to READY TO PROCEED. A command-line gate and CI integration make the same analysis repeatable before later releases. The creative element is the complete path from an observed failure to a persistent guard: investigate the incident, trace the configuration, repair the gaps, and prevent the same static mismatch from passing unnoticed again. The prototype reduces manual cross-file comparison and makes the release decision visible and reproducible. DriftLens checks static configuration consistency. A READY verdict does not verify secret values, running services, or the success of an actual deployment.