Decision: enforcement points are never self-merged #1775
Notifications
Due Date
No due date set.
Blocks
Reference: sam/archie#1775
Reference in new issue
Block a user
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.
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).