[EPIC] Archie self-development: the closed self-improvement loop #1769

Closed
opened 2026-11-02 14:32:02 +00:00 by sam · 2 comments
Owner

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):

  1. Self-intake curator: run failures, gate output and transcripts become filed issues; maintainer approves priority.
  2. Approved-issue loop: approval -> triage/implement workflows -> adversarial review -> daemon opens a green PR; maintainer merges at this stage.
  3. Implementation judge: the prbench judge pattern scores diffs, calibrated against maintainer merge decisions; auto-merge only above the bar for the qualifying class.
  4. Outcome distillation: a curator turns merged-run postmortems into repo rules, each added only because it changes a decision.
  5. Self-changes ship through the canary window (releaseupdate judges the installed release) before wide release; rollback is a revert of a gated commit.

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.

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): 1. Self-intake curator: run failures, gate output and transcripts become filed issues; maintainer approves priority. 2. Approved-issue loop: approval -> triage/implement workflows -> adversarial review -> daemon opens a green PR; maintainer merges at this stage. 3. Implementation judge: the prbench judge pattern scores diffs, calibrated against maintainer merge decisions; auto-merge only above the bar for the qualifying class. 4. Outcome distillation: a curator turns merged-run postmortems into repo rules, each added only because it changes a decision. 5. Self-changes ship through the canary window (releaseupdate judges the installed release) before wide release; rollback is a revert of a gated commit. 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.
Author
Owner

Child issues, in stage order:

  • #1770 self-intake curator (stage 1)
  • #1771 approved-issue loop (stage 2)
  • #1772 implementation judge + auto-merge bar (stage 3)
  • #1773 outcome distillation into repo rules (stage 4)
  • #1774 canary window for self-directed changes (stage 5)
  • #1775 decision: enforcement points never self-merged (hard boundary)
Child issues, in stage order: - #1770 self-intake curator (stage 1) - #1771 approved-issue loop (stage 2) - #1772 implementation judge + auto-merge bar (stage 3) - #1773 outcome distillation into repo rules (stage 4) - #1774 canary window for self-directed changes (stage 5) - #1775 decision: enforcement points never self-merged (hard boundary)
sam added the epic label 2026-11-02 14:34:08 +00:00
sam added the high label 2026-11-12 15:51:28 +00:00
sam added a new dependency 2026-11-13 03:03:44 +00:00
Author
Owner

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).

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).
sam closed this issue 2026-11-14 14:45:21 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Reference: sam/archie#1769