A subagent works from hq; a coding one in a worktree under hq's .work, also reading its repository's conventions (the operator, 2026-11-03)

2026-11-03 12:46:24 +01:00
parent e8c154c3a0
commit 4315bb6307
2 changed files with 2 additions and 2 deletions
@@ -18,7 +18,7 @@ playbook 01's *Review by architectural domain*, two architectural domains each:
 `research-reader`, carries one reading task of playbook 01's step 5: code on main, counts from the manifests, a
 try in process. Four more carry playbook 07: `mesh-preparer` (the prepare step), `mesh-developer` (develop),
 `mesh-code-reviewer` (the review) and `mesh-watcher` (every wait). Every agent starts from the knowledge base and maps
-each interaction onto a mesh path; the lead writes only the handover, never an agent's way of working.
+each interaction onto a mesh path; the lead writes only the handover, never an agent's way of working. A subagent runs in the session that started it, from hq: its way of working comes from its definition and hq's playbooks, its knowledge from the knowledge base; one given a coding task works in a worktree under hq's `.work/` and also reads the conventions of the repository it changes, and where those contradict hq, hq wins and the agent says so.

 ## The development cycle