From fff89b7c62182bc5fe1bb6be51f96257e9304821 Mon Sep 17 00:00:00 2001
From: mesh-tools <mesh-tools@noreply.localhost>
Date: Fri, 16 Oct 2026 19:18:42 +0000
Subject: [PATCH] Playbook 07: report the whole issue tree every five minutes,
 every two while a delivery runs

The operator asked for a status update more often, with an overview of the issues worked on.
---
 00-META/process/07-feature-branches.md | 13 ++++++++-----
 1 file changed, 8 insertions(+), 5 deletions(-)

diff --git a/00-META/process/07-feature-branches.md b/00-META/process/07-feature-branches.md
index 663edd29..5d9dad8d 100644
--- a/00-META/process/07-feature-branches.md
+++ b/00-META/process/07-feature-branches.md
@@ -206,9 +206,10 @@ on, with when it started and its bound.
 | a merge after ready | 5 minutes after the checks pass | read `mesh-delivery.show` for the delivery |
 | a delivery plan | its class's budget (`mesh-delivery.times`), at most 30 minutes | read `mesh-controller.plans`, then `mesh-delivery.stalled` |
 
-**Every ten minutes, and at once when something lands, stops or needs the operator,** the lead reports, in
-one of the two layouts below. Times are local and absolute; 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.
+**Every five minutes, every two minutes while a delivery plan runs, and at once when something lands, stops or
+needs the operator,** the lead reports, in one of the two layouts below (the operator, 2026-10-16: an overview
+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:
@@ -225,6 +226,7 @@ mesh-controller (agent: fixing, 2 of 3 landed)
 mesh-catalog (agent: waiting)
 └── ⏸ 751  (above, under 736)
 
+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> %
@@ -237,8 +239,9 @@ Next: <the next action, one line>
 <slug> step <n>/<m> · <phase> <used>/<bound> min · <landed>/<total> landed · past bound: <none | what> · needs you: <nothing | what> · week <n> %
 ```
 
-A report says what changed since the last one first; an unchanged table is not repeated, the short layout
-says it instead.
+A report says what changed since the last one first. In the session every report is the full layout, the whole
+tree of the step's issues included, also when only time passed: the operator reads the state from it without
+asking. The short layout is for a channel.
 
 ## The context of the lead's own session