Give the record writer a definition, as a role started more than once

The lead started an agent that proposes a record from a draft by hand in two sessions; agents-have-a-home asks a definition. Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ
2026-11-11 14:17:07 +01:00
parent 1c6fe9611c
commit b4abb98aaa
2 changed files with 35 additions and 1 deletions
@@ -21,7 +21,8 @@ operator). A fifth,
 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). A tenth, `hq-design-writer`, writes one set of design amendments
 (playbook 02, *Amending an existing design*) from accepted decisions and a milestone's findings, in a worktree of its
-own, ready for the review by architectural domain. An agent that researches, decides, designs or reviews a design starts
+own, ready for the review by architectural domain. An eleventh, `hq-record-writer`, proposes one decision record or
+research effort to the knowledge base from a draft (playbooks 01 and 02) and follows its review to approve. An agent that researches, decides, designs or reviews a design starts
 from the knowledge base and maps each interaction onto a mesh path. An agent that prepares, builds or reviews code
 starts from the milestone's part of its design alone, builds what its design lines say, and decides nothing: what
 the design does not answer is a design question for the operator, answered in the design before any code