Consider a reconstructed incident that shows up when teams treat an agentic loop as an architecture review. A backend pair watched their coding agent close six steps with a confident summary and a tidy pull request. The suite was green, the changelog mentioned Redis-backed sessions, and nobody had added Redis to compose, secrets, or the runbook. The miss was not a weak model so much as a missing freeze on what the repository was allowed to assume. Developer glossaries often present planning, ...