Outcome distillation: postmortems of merged runs become repo rules #1773
Notifications
Due Date
No due date set.
Blocks
Reference: sam/archie#1773
Reference in new issue
Block a user
Stage 4 of the self-development loop — the actual self-improvement. Wanted: a curator reads postmortems of merged runs (what failed, what the adversarial review caught, what the maintainer changed at merge) and proposes additions to the repo's agent instructions, each justified by the decision it changes; rules that stop changing decisions get removed. Proposals are one-action accept/reject for the maintainer.
Done when: the curator produces rule proposals citing the triggering run, accepted proposals land as commits citing this epic, and the instruction file stays short enough to read in full (rules that no longer change a decision are deleted).
Closed: goes against the product plan in epic #1977. A loop where Archie develops its own codebase through PRs frames Archie as a coding agent; coding is a side effect, not the goal. Learning from outcomes is covered by proposals (#1995).