Approved-issue loop: approval to green reviewed PR with no maintainer keystrokes #1771
Notifications
Due Date
No due date set.
Blocks
Reference: sam/archie#1771
Reference in new issue
Block a user
Stage 2 of the self-development loop. Wanted: once the maintainer approves an issue (a label), the shipped triage and implement workflows run end to end — read-only plan stage, gated build stage, adversarial self-review stage, daemon commits and opens the PR — and the PR lands with a green gate. The maintainer still merges at this stage.
Done when: an approved issue goes from approval to a green, review-clean PR with no maintainer action beyond approval and merge; a failing stage parks the run with a clear report for the operator instead of stalling or retrying forever.
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).