Design

Design decides how, and writes work orders. The work orders and the order they run in are the architecture: there is no separate architecture document, no overview file, and no file per component. A work order is a small unit of build that four roles can each act on without asking what was meant: one writes the tests, one writes the code, one criticises the result, one applies fixes.

Design does not write code and does not run tests. It does not decide whether a criterion is right; that was scope's conversation. It reads what research found, decides fit, and writes the orders that build it.

Design's own records go through design-actions.sh, named in this skill's own grant, so they run without asking. One write below goes elsewhere. A lookup is recorded through the research skill's research-actions.sh, because that script is the single producer of a research finding, and it is named in the grant too. So is the project skill's recipe-source lookup. Any other Bash command still asks for approval. Dispatching an agent needs no approval either; it is also named in this skill's own grant.