Home / Lessons / Make it stick / 24 of 27
Scar tissue
The same mistake cannot happen silently twice.
Each serious failure gets a name and a written lesson. Then one question: where must this live?
Architecture and decisions go in the project wiki. Failure patterns every agent should know go in the repository rules. Preferences and lessons go in memory. And anything critical to safety becomes enforcement: a hook, a test, a check in CI, a permission or a database control.
The next agent to approach the same dangerous path is warned with evidence, or blocked. The incident has changed the system, not only my opinion.
How I do it
Important lessons move out of prose and into something that runs, whenever that is possible.
The rule
After every failure ask where the lesson must live so that it cannot be skipped.
Rule 24. After every failure ask where the lesson must live so that it cannot be skipped. (Scar tissue, https://chiefofagents.si/one-page#rule-24)
The skill I use for this: /principle-fix-root-causes. Made by Lauren Tan.
Read next
The ideas behind it
This lesson as plain text, for your agent. Or all 27 on one page.