Watch
0
0
Fork
You've already forked hyperhive
0

agents get read, not write, on their own agent-configs repo; an existing grant is left alone

This commit is contained in:
damocles 2026-11-15 16:20:54 +01:00 • committed by mara
commit 07c66e3a1c

View file

@ -19,7 +19,7 @@ No MCP tool exists for config changes: opening the PR IS the request.
own config as well as how it changes it.
Branch protection (the agent isn't on the `main` push allowlist;
merge and approvals allowlist = `operators` team; see "Forge config repos"
below) makes the agent a write collaborator that **can't merge its own
below) makes the agent a read collaborator that **can't merge its own
config PR**.
2. An operator reviews the PR **on the forge** (native diff, threaded
comments, CI status) and merges it there. Merging needs membership of
@ -194,10 +194,12 @@ Every agent created through the swarm has a repo in the private
hive-c0re pushes nothing to it, keeps no clone and reads nothing from it: forge
`main` advances only by an operator's merge.
Each agent is a **write collaborator on its own** `agent-configs/<name>`
repo — so it can push a branch and open a config PR — but not a member
of any other agent's, so it can't reach another agent's config through
the forge. Branch protection keeps the agent off the `main` push
Each agent is a **read collaborator on its own** `agent-configs/<name>`
repo, so it can clone it and open a config PR through the AGit flow (no push
access needed), but not a member of any other agent's, so it can't reach
another agent's config through the forge. A grant of more than read, made by
an operator or before agents got read, is left as it is: the `AddRepoMember`
node only adds read where the agent has none. Branch protection keeps the agent off the `main` push
allowlist and allowlists merging to the `operators` team only, so an
agent can't fast-forward its own config or self-merge its PR (see
[Config changes](#config-changes) above). hive-c0re passes the credential to