https://andreasnissen.dev/tags/infrastructure/Recent content in Infrastructure on Andreas NissenHugoen-us© Andreas NissenSat, 05 Sep 2026 00:00:00 +0000https://andreasnissen.dev/writing/evidence-for-agent-infrastructure-changes/Sat, 05 Sep 2026 00:00:00 +0000https://andreasnissen.dev/writing/evidence-for-agent-infrastructure-changes/<p>A coding agent changes a service&rsquo;s liveness check from <code>/live</code> to <code>/ready</code>. Both endpoints return success during review. The configuration is valid and the deployment completes.</p> <p>Later, the database slows down. In this hypothetical service, <code>/ready</code> checks database connectivity. Enough failed liveness checks now cause the application container to restart, although restarting it cannot repair the database. The configuration change has coupled a dependency problem to application restarts.</p> <p>My release rule is simple: <strong>before shipping an infrastructure change, identify the failure it could introduce, the observation that would reveal it, and the action that would restore service.</strong> Match the evidence to those answers.</p>