Postmortems turned into memory
DevOps, SRE and securityEngineering team writing blameless postmortems
Our postmortem for a 40-minute outage said 'never add a column with a default to the orders table during business hours'. It sat in Notion. Six weeks later an agent wrote exactly that migration on a Tuesday afternoon.
How do I make sure AI agents follow the lessons from our incident postmortems?
After each postmortem, save the lessons that change how work is done in ArcRoom with arcroom decide, linking the postmortem. Recall puts the lesson in front of an agent whose prompt or files touch that area, like migrations on the orders table. Give lessons that stop applying an expiry with arcroom rule, or report them with arcroom wrong. ArcRoom doesn't read Notion.
Also asked as: An agent wrote the exact migration our postmortem warned against. How do we stop that? · How do I turn incident lessons into rules AI agents actually see? · Can an AI agent learn from past outages before it changes the database?
After each postmortem, the lessons that change how work is done are saved with arcroom decide, with a link to the postmortem.
- Decision
- Recall
- Expiry rule
- Wrong-memory report
Recall (budget 1.2k tokens):
Step by step
- After each postmortem, the lessons that change how work is done are saved with arcroom decide, with a link to the postmortem.
- Recall puts the lesson in front of an agent whose prompt or files touch migrations or the orders table.
- Lessons that stop applying get an expiry with arcroom rule, or are reported with arcroom wrong.
What the agent sees
Recall (budget 1.2k tokens):
• Decision (Sep 2): migrations on orders run after 22:00 IST only.
Why: ALTER with default locked orders for 40 min (postmortem PM-17)Compared with today's tools
Postmortems in Notion or Confluence
Postmortems are written and filed; engineers are expected to read the relevant ones.
- Setup
- Already in place
- Ongoing
- read old postmortems before risky work, rarely done
ArcRoom
Every agent reads the team playbook before it works and writes to it when it finishes. Nothing to update by hand.
- Setup
- 2 min (npx arcroom init)
- Ongoing
- None
The wiki keeps the full story and stays the source; ArcRoom puts the one-line lesson in front of the agent when it is about to repeat it.
Where it stops
Someone has to turn the postmortem into one or two short decisions. ArcRoom doesn't read Notion.
Try it in your project
Works with the agents your team already uses, and any agent over MCP or the HTTP API.