Playbook 02: one design per thing; a graduation rewrites the design that covers it instead of writing a second (the operator, 2026-10-16)

2026-10-16 19:40:48 +02:00
parent 225eee14d0
commit 101d7f30f7
1 changed files with 4 additions and 1 deletions
@@ -33,7 +33,10 @@ about an hour, and said to the operator if it runs past.
   - **Pre-check each record before proposing it**, as for research (playbook [01](01-research.md), step
     5): every record, issue or design it names is in `links`; each deferral names its issue; each figure
     is given as measured; no word on a glossary *Not:* line.
-3. **Write the design.** Create the document under `03-DESIGN/01-to-be/` with frontmatter:
+3. **Write the design.** **One design per thing** (the operator, 2026-10-16): when a to-be design already
+   covers what the decisions change, they rewrite that design, as *Amending an existing design* below says,
+   and no second design is written beside it that refers to it. Only for something no design covers, create
+   the document under `03-DESIGN/01-to-be/` with frontmatter:

   ```yaml
   ---