novox/hq
13
0
Fork 0
Code Issues Pull Requests 2 Releases Wiki Activity

Merge pull request 'Playbook 07: report the whole issue tree every five minutes, every two while a delivery runs' (#389) from fix/pb07-overview-every-five into main

Browse Source
This commit was merged in pull request #389.
This commit is contained in:
mesh-tools
2026-10-16 19:34:36 +00:00
parent 80e36c7595 fff89b7c62
commit f9c240a957
1 changed files with 8 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
00-META/process/07-feature-branches.md
+8 -5
View File
@@ -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 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` | | 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 **Every five minutes, every two minutes while a delivery plan runs, and at once when something lands, stops or
one of the two layouts below. Times are local and absolute; every number has its unit and its bound or needs the operator,** the lead reports, in one of the two layouts below (the operator, 2026-10-16: an overview
baseline; an issue is named by its number and a few words, never by its number alone. 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 **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: waits for, marked ✓ landed, ▶ fixing, ⏸ waiting, ✗ stopped:
@@ -225,6 +226,7 @@ mesh-controller (agent: fixing, 2 of 3 landed)
mesh-catalog (agent: waiting) mesh-catalog (agent: waiting)
└── ⏸ 751 (above, under 736) └── ⏸ 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" Past its bound: <the wait, how long, what is being done> — or "none"
Needs you: <one line per question, with my recommendation> — or "nothing" Needs you: <one line per question, with my recommendation> — or "nothing"
Allowance: week <n> % (<+d> since the last report), session <n> % 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> % <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 A report says what changed since the last one first. In the session every report is the full layout, the whole
says it instead. 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 ## The context of the lead's own session