From fb284fa6ee2a38965519426a2d1d5cb22d94b67d Mon Sep 17 00:00:00 2001
From: jochen <jschoubben@gmail.com>
Date: Sat, 17 Oct 2026 14:13:28 +0200
Subject: [PATCH] Playbook 07: the full report shows the whole design's
 milestones, the running one's issues under it (the operator, 2026-10-17)

---
 00-META/process/07-feature-branches.md | 25 +++++++++++++++----------
 1 file changed, 15 insertions(+), 10 deletions(-)

diff --git a/00-META/process/07-feature-branches.md b/00-META/process/07-feature-branches.md
index ab68222c..b4f5d008 100644
--- a/00-META/process/07-feature-branches.md
+++ b/00-META/process/07-feature-branches.md
@@ -203,26 +203,31 @@ needs the operator,** the lead reports, in one of the two layouts below (the ope
 of the issues, often). Times are local and absolute, from the clock (`date`), never guessed; every number has its
 unit and its bound or baseline; an issue is named by its number and a few words, never by its number alone.
 
-**The full layout** (in the session), the issues as a tree: grouped by repository, each issue under the one it
-waits for, marked ✓ landed, ▶ fixing, ⏸ waiting, ✗ stopped:
+**The full layout** (in the session) is the whole design as a tree (the operator, 2026-10-17: always the full
+overview): every milestone of the design with its state, and under the running milestone its repositories and
+their issues, each issue under the one it waits for, marked ✓ landed or delivered, ▶ fixing, ⏸ waiting, ✗ stopped:
 
 ```
 Feature <slug> · milestone <n> of <m> · phase <name>, <minutes used> of <bound> min
 Issues: <landed> of <total> landed · <fixing> fixing · <waiting> waiting
 
-mesh-controller (agent: fixing, 2 of 3 landed)
-├── ✓ 652  assignments on the bus                      landed 14:02
-├── ▶ 736  placement words leave the layers            fixing since 13:51, 23 of 30 min
-│   └── ⏸ 751  config keys named (mesh-catalog)        waits for 736
-└── ✓ 654  a file names its template                   landed 13:20
-mesh-catalog (agent: waiting)
-└── ⏸ 751  (above, under 736)
+Design <nn> · <its title>
+├── ✓ milestone 1  <its outcome, a few words>                 delivered 12:58
+├── ▶ milestone 2  <its outcome, a few words>
+│   ├── mesh-controller (agent: fixing, 2 of 3 landed)
+│   │   ├── ✓ 652  assignments on the bus                      landed 14:02
+│   │   ├── ▶ 736  placement words leave the layers            fixing since 13:51, 23 of 30 min
+│   │   │   └── ⏸ 751  config keys named (mesh-catalog)        waits for 736
+│   │   └── ✓ 654  a file names its template                   landed 13:20
+│   └── mesh-catalog (agent: waiting)
+│       └── ⏸ 751  (above, under 736)
+└── ⏸ milestone 3  <its outcome, a few words>                 <its issues>
 
 Opened along the way: <each issue opened during the feature, its number and a few words, and where it goes> — or "none"
 Past its bound: <the wait, how long, what is being done> — or "none"
 Needs you: <one line per question, with my recommendation> — or "nothing"
 Allowance: week <n> % (<+d> since the last report), session <n> %
-Next: <the next action, one line>
+Next: <the next actions up to the delivery, in order>
 ```
 
 **The short layout** (on a channel such as Telegram, or when nothing changed but time):
-- 
2.54.0