# Remediation Loop

> What happens after a failure is seen: trace to eval to policy to fix to proof. Closing the loop is what turns monitoring into assurance.

Category: observability

A remediation loop is the path from a detected failure to a durable fix: see it, trace it, turn it into an eval, change the policy, apply the fix, and produce proof it will not recur silently.

## Why it matters
Most teams stop at detection. They get an alert, eyeball it, restart something, move on. The same failure comes back next week wearing a different hat. A closed loop guarantees that each failure makes the system permanently better instead of just briefly quieter.

## In practice
Failure becomes a trace. The trace becomes an eval case. The eval exposes the missing boundary. The boundary becomes a policy. The policy is enforced and the whole thing leaves a receipt. Next time, it fails closed or does not fail at all.

## Where it shows up in my work
This is the exact loop I map for agent-monitoring teams: where agent monitoring becomes agent assurance. governable-ai.com lives at the proof end of it.

---
Source: https://ryanhunter.io/lexicon/remediation-loop
Part of the Agent Infrastructure Lexicon by Ryan Hunter. https://ryanhunter.io/lexicon