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
@@ -106,7 +106,7 @@ issue whether it is being fixed in between, after the delivery, or waits, and on
 `.claude/agents/`: `mesh-preparer` for this step, `mesh-developer` for step 1, `mesh-code-reviewer` for step 2,
 `mesh-watcher` for every wait, and the four reviewers by architectural domain and `research-reader` of playbook 01.
 The lead writes only the handover: what the agent works on (issue, records, branch, worktrees, commits) and where it
-reports. How it works, what it reads first and what it judges come from its definition, and so does its model: a
+reports. 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. How it works, what it reads first and what it judges come from its definition, and so does its model: a
 `mesh-developer` runs on the smaller model, and the lead starts one on the larger model only for work whose parts meet
 at an interface still being designed, written with its reason in the milestone file; a lesson about how an agent
 works goes into its definition by an hq pull request (the operator, 2026-11-03: "please don't write prompts by hand,