diff --git a/04-ISSUES/344-known-gaps-in-the-agents-boundary-accepted-for-now/00-report.md b/04-ISSUES/344-known-gaps-in-the-agents-boundary-accepted-for-now/00-report.md
index bd5cec58..506d55eb 100644
--- a/04-ISSUES/344-known-gaps-in-the-agents-boundary-accepted-for-now/00-report.md
+++ b/04-ISSUES/344-known-gaps-in-the-agents-boundary-accepted-for-now/00-report.md
@@ -66,6 +66,14 @@ note. Each gap says what is open, why it matters, and what would close it.
    after two minutes, while the record allows it fifteen. On a large disk the verdict stays "not judged".
    *Closes with:* one bound, settled in the node-engine with ADR 0266.
 
+10. **An agent can merge its own pull request.** No mesh repository's main requires an approval on the forge
+   (`required_approvals: 0`), and the forge tool merges as the forge's administrator once the required checks are
+   green. An agent can therefore change a module that runs on every node, open the pull request, wait for the
+   checks and merge it, and the controller walks the change out. The checks judge whether every machine still
+   composes, not what the change is for. The operator's yes in a session is a convention, and nothing checks it.
+   *Closes with:* a merge that needs the operator's own approval: a required approval on the forge from the
+   operator's personal account only, or an approval through ADR 0259's asks.
+
 ## Why it is an issue
 
 Each gap is a known way around a rule the mesh states. A gap that is written down can be weighed and closed. A