During an incident, teams often find the old ticket that says *“resolved”* but lose the useful part: what was tried first, what failed, and what finally restored the service.

For a hackathon, we built **Adaptive Incident Intelligence**, a prototype that keeps that sequence in memory. When a new incident arrives, it retrieves similar cases through Hindsight, proposes an action with supporting evidence, and checks the proposal against deterministic policy rules. Higher risk actions require human approval. After an action, it retries the original failed operation and checks service health before recording the outcome.

The screenshots show the incident dashboard, an ordered history where a retry failed before a fix worked, and our evaluation view. In the demo shown, action accuracy on **12 held-out synthetic cases** rose from 0% with empty memory to 50% after evidence was added. That’s a small prototype evaluation, not a claim about production performance. All demo incidents and actions are simulated.

We used FastAPI, React, Hindsight, and a local model via Ollama. The part I’m most interested in is the boundary between useful agent memory and safe automation.

**If you build or operate LLM agents, what evidence would you need before letting one recommend an incident fix? And where would you draw the line for automatic execution?**



We built an incident response prototype that remembers failed fixes, not just successful ones.Would you trust its recommendations?