Decision: enforcement points are never self-merged #1775

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

Decision for the self-development loop: changes to the enforcement layer — the commit gate, the invariants in the repo agent instructions, access control and grant scoping, the daemon-only git path, webhook HMAC verification — may be proposed by archie but are never merged by archie; they always require maintainer merge. Everything else (workflows, curators, memory, docs, dashboard) is fair game for the loop.

Done when: the boundary is written into the repo agent instructions AND enforced at the enforcement points (the commit gate and access control hold any self-directed PR touching an enforcement path for maintainer review) — documented in docs is not enough, the gate itself must hold it; any self-directed PR touching an enforcement path is never merged by the loop.

Decision for the self-development loop: changes to the enforcement layer — the commit gate, the invariants in the repo agent instructions, access control and grant scoping, the daemon-only git path, webhook HMAC verification — may be proposed by archie but are never merged by archie; they always require maintainer merge. Everything else (workflows, curators, memory, docs, dashboard) is fair game for the loop. Done when: the boundary is written into the repo agent instructions AND enforced at the enforcement points (the commit gate and access control hold any self-directed PR touching an enforcement path for maintainer review) — documented in docs is not enough, the gate itself must hold it; any self-directed PR touching an enforcement path is never merged by the loop.
sam added the decision label 2026-11-02 14:34:09 +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:12 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Reference: sam/archie#1775