Playbook 07: the lead reads what an answer names before it answers

Three lead answers in one day named a structure from memory and needed a correction once a developer read the code. Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 20:32:42 +01:00
parent a4f9d43037
commit 26faa9981f
1 changed files with 4 additions and 1 deletions
@@ -318,7 +318,10 @@ answer is written down before the code; 2026-11-11: the lead answers it against

 1. **The lead answers each question against the principles**, in one line in the milestone's lead-answers file
   (beside the milestone part, cited as "design NN M A-n"), naming the principle that settles it (step 0, *Who answers
-   a design question*). One no principle settles the lead sends on: to the operator, one per ask, as playbook
+   a design question*). **Before an answer names a field, a key, a bucket, a subject or a function, the lead reads it
+   where it lives** (the code at the join head, or the seat definition) and checks the answer against what is there,
+   not against the question's words (2026-11-12: three answers that day named a structure from memory and needed a
+   correction once a developer read the code). One no principle settles the lead sends on: to the operator, one per ask, as playbook
   [02](02-graduation.md), *Answering a design question*, says, each ask added to its wait list, when its answer
   changes what the operator sees or how they work, removes data or needs the operator's terminal; every other one to
   `hq-design-writer` in its handover. A question the writer finds is the operator's it hands back.