Self-directed changes ship through the canary window before wide release #1774

Closed
opened 2026-11-02 14:32:29 +00:00 by sam · 1 comment
Owner

Stage 5 of the self-development loop. Wanted: changes archie makes to its own codebase route through the canary release path — the release-update judge evaluates the installed release over its window — and promote only on a clean judgment. Rollback is a plain revert of a gated commit, since every self-directed change is one.

Done when: a self-directed change is released as a canary, judged over the window, and promoted or rolled back based on that judgment, with the release history showing the canary entry and the verdict.

Stage 5 of the self-development loop. Wanted: changes archie makes to its own codebase route through the canary release path — the release-update judge evaluates the installed release over its window — and promote only on a clean judgment. Rollback is a plain revert of a gated commit, since every self-directed change is one. Done when: a self-directed change is released as a canary, judged over the window, and promoted or rolled back based on that judgment, with the release history showing the canary entry and the verdict.
sam added the task label 2026-11-02 14:34:09 +00:00
sam added the medium label 2026-11-12 15:51:28 +00:00
sam added a new dependency 2026-11-13 03:03:36 +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:11 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Reference: sam/archie#1774