The pipeline gets better every time it runs. Errors are inputs.
The loop
- Catch: an error, a gap, or a repeated manual step surfaces during work (audit finding, review correction, deploy incident).
- Fix where found: repair the live problem first.
- Fix at the source: if the error can recur, the fix goes into the library (the skill, the spec, the template, this wiki), same turn or same session. All projects inherit it.
- Script the deterministic: any step that is "same input, same output, no judgment" becomes a script or cron, registered in the tool catalogue, never an instruction an AI might skip.
- Audit the system itself: periodic lean-audit per project. Bias to LESS: prefer deleting or merging a rule over adding one. A rule nobody needed twice gets removed.
Bright lines
- A recurring correction that stays only in chat is a future error.
- A guideline that contradicts another one is a bug; resolve it the day it is found.
- New rules require a diagnosed cause, not a hunch.
Done when
- This chapter is never done. That is the point.