[EPIC] Archie self-development: the closed self-improvement loop #1769
Notifications
Due Date
No due date set.
Depends on
Reference: sam/archie#1769
Reference in new issue
Block a user
Wanted: archie persistently and increasingly develops its own codebase, self-improving without degrading it. The principle: enforcement stays in the harness (commit gate, daemon-only git, scoped grants, HMAC, invariants), never in the prompt; archie improves everything else (workflows, curators, memory, docs), which is data the server validates.
Stages (filed as child issues):
Hard boundary (separate decision issue): changes to enforcement points are never self-merged; they always require maintainer merge.
Done when: the loop runs end to end on real issues with the maintainer merging nothing but boundary-class PRs, and the judge bar plus canary judgment measurably keep quality flat or rising.
Child issues, in stage order:
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).