Configuration drift is treated as a visibility problem solved by tooling. It isn't. It's a breakdown in ownership of declared infrastructure state — and no detection pipeline closes an accountability gap.
The industry built a full tooling category around drift: scanners, policy-as-code engines, GitOps reconciliation loops, IaC state management. Engineers get alerted when state diverges. Pipelines remediate. Tickets close. The problem is that none of those actions assign ownership. The loop runs cleanly at the boundary it was designed for. It is insufficient at the layer where accountability actually breaks.
How the Industry Closes the Loop on Paper
The canonical model goes: declare state in code, detect divergence, trigger remediation, mark resolved. Every tool in the drift management category is optimized for this cycle. Each one is correct within its designed boundary.
What the model doesn't close is the accountability layer underneath it. Detection fires, remediation executes, the alert clears — and the authority vacuum that permitted the deviation remains completely intact. The state returns to declared. The ownership question was never asked.
