Name the design section, not its number; the preparer and playbook 07 place new code the same way (review 1)
mesh/delivery merged: source.main moved to novox/hq@f0c05d1edb84
mesh/check being carried to b525f1059b69 on f0c05d1edb84 | from d4ae72782336

Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig
This commit is contained in:
2026-11-04 23:20:38 +01:00
parent 69f95f551d
commit b525f1059b
5 changed files with 20 additions and 11 deletions
+3
View File
@@ -156,6 +156,9 @@ is a breach the lead names.
3. **For each item of the second answer, what happens to it after the change** (kept as it is, moved to a named seat,
module or verb, replaced by a named part, or dropped and why nothing needs it), **and the test that proves it**: an
acceptance criterion (item 5) at its level, or, for a dropped effect, the search showing no reader is left.
For every new exported type, field, constant, package or module, the answer names the line of the design
section *Where a seat's code goes* that places it (ask the knowledge base where a seat's code goes): where new
code goes is always a design question, never the lead's own choice.
Code starts only when the three answers are complete for every repository: no fixing agent starts on a context file
without them, and an effect found later is the prepare step missed, written into the answer and its issue before the
fix. In the days up to 2026-11-02 the controller was taken apart without this answer: jobs nobody had named (making
+4 -4
View File
@@ -40,11 +40,11 @@ processing power"). Everything before the push is local and fast, and no try is
with what happens to each after the fix. It is a few lines in the issue's note, under `What exists today`, and the
review runs the search again; a reader it finds that the note omits makes the fix wrong. **Where each new piece of
code goes is always a design question, never the lead's own choice:** before any code, ask the knowledge base for the
area (`knowledge-base.ask`) and read the design that places code ([design 20](../../03-DESIGN/01-to-be/20-writing-a-module.md)
*Where a seat's code goes*, and design 26 for a seat's types); the note names, for every new exported type, field,
constant, package, module or repository the fix adds, the design line or decision clause that puts it there. A
area (`knowledge-base.ask`) and read the design section that places code, *Where a seat's code goes* (found by
asking the knowledge base where a seat's code goes); the note names, for every new exported type, field,
constant, package or module the fix adds, the design line or decision clause that puts it there. A
handover to the developer quotes those lines and never decides a placement itself (issue 1748, 2026-11-04: a
retake class placed in mesh-sdk by the lead's handover, against design 26, passed review and its check). If a design question is open, it is settled before any
retake class placed in mesh-sdk by the lead's handover, against that section, passed review and its check). If a design question is open, it is settled before any
code is written: on the issue, through the knowledge base (`knowledge-base.ask` first: what is decided is read before anything is designed), or by the operator. A fix that turns out to
need a second repository, or more than about an hour, stops here and becomes a feature; one that needs a
decision stays a small fix. **The session's own model (the larger) then writes the issue's acceptance