diff --git a/README.md b/README.md index 1079460f3..ccc5a50f8 100644 --- a/README.md +++ b/README.md @@ -750,10 +750,11 @@ can be seen on the pilot server as soon as it joins the pilot. **Bring your own harness.** dx-maps works with whatever AI coding agent or agent harness you already use. The repo gives you the branch strategy below, the checks (`bun run gates:pre`) and the Plugin -Studio; it does not ship a harness. Roles such as a coordinator that puts the merges onto the pilot in order, or a -gate-keeper that reads each change before it joins the pilot, are jobs your harness gives to its agents. +Studio; it does not ship a harness. The roles are one coordinator agent that puts the merges onto the pilot +in order, one repo agent per repository that handles its branches and watches the work being done in it, +and one agent per plugin; your harness gives these jobs to its agents. -![The delegation model: the pilot branch (development) at the centre behind the pilot lock; publishing to the landing branch (main) and its outputs below it; inside the Plugin Studio; eight plugins around it, each owned by one agent; a coordinator and a gate-keeper over the agents; below, how a change joins the pilot and then reaches the landing branch, in four steps, the three outputs, and how it scales: one PR branch per plugin, a self-hosted git service, and publishing to a public host only from the landing branch](documentation/readme-images/delegation-model.png) +![The delegation model: the pilot branch (development) at the centre behind the pilot lock; publishing to the landing branch (main) and its outputs below it; inside the Plugin Studio; eight plugins around it, each owned by one agent; a coordinator and a repo agent over the plugin agents; below, how a change joins the pilot and then reaches the landing branch, in four steps, the three outputs, and how it scales: one PR branch per plugin, a self-hosted git service, and publishing to a public host only from the landing branch](documentation/readme-images/delegation-model.png) [Open the diagram full size](documentation/readme-images/delegation-model.png): on a phone its small text needs it. @@ -842,8 +843,9 @@ So the project works like a busy kitchen: 2. **Only one change joins the pilot at a time.** Whoever holds the *pilot lock* first catches up with everyone else's latest work, fixes any clash itself and runs every check; the change goes into the pilot branch only if nothing fails. The pilot branch always works. -3. **Someone keeps order.** A coordinator can put the merges onto the pilot in order, and a gate-keeper can read - each change by its content before it joins the pilot. Your harness gives these jobs to its agents. +3. **Someone keeps order.** One coordinator agent puts the merges onto the pilot in order, and one repo agent + per repository handles its branches and watches the work being done in it. Your harness gives these jobs + to its agents. 4. **The landing branch moves only when a person approves a publish**, after the checks pass on that exact version. The pilot server follows the pilot branch; the landing server rebuilds from the landing branch. diff --git a/documentation/readme-images/delegation-model.png b/documentation/readme-images/delegation-model.png index 63217aa59..a55897cda 100644 Binary files a/documentation/readme-images/delegation-model.png and b/documentation/readme-images/delegation-model.png differ diff --git a/documentation/readme-images/src/delegation-model.svg b/documentation/readme-images/src/delegation-model.svg index 5edefe17c..18a63de63 100644 --- a/documentation/readme-images/src/delegation-model.svg +++ b/documentation/readme-images/src/delegation-model.svg @@ -116,14 +116,14 @@ Experimental shelf · 5 plugins -roaming -agent +an agent +per plugin coordinator -gate-keeper -a coordinator puts the merges in order; -a gate-keeper checks each one by its content +repo agent +one coordinator puts the merges in order; +a repo agent per repo runs its branches and watches the work one owner per plugin, in its own branch · a second reader for every change @@ -141,7 +141,7 @@ coordinator — orders merges -gate-keeper — checks each merge +repo agent — one per repo How a change joins the pilot — one at a time, so many plugins can be built at once