Design 47 gives its running milestones rows; the glossary and playbook 07 name progress (issue 1947)

The three milestones of the controller leaving build and delivery were prose only, so no reader of the table saw the running work; 1209 and 971 were listed in two milestones against ADR 0493 §2.
2026-10-26 16:40:12 +01:00
parent 3a5c4c7c4d
commit b7dabd8ceb
3 changed files with 19 additions and 3 deletions
@@ -529,6 +529,13 @@ Allowance: week <n> % (<+d> since the last report), session <n> %
 Next: <the next actions up to the delivery, in order>
 ```

+**The tree is read, not assembled.** `knowledge-base.progress` with `of: "design <nn>"` answers the tree's
+milestones, issues, pull requests and held groups in one call, each with when it last moved: `detail: minimal` for the
+five-minute report, `detailed` about every thirty minutes and whenever something stops (issue 1947). What it cannot
+read for certain from the design's milestone table it says in `warnings`; the lead fixes the table, it does not
+correct the tree by hand. How it is checked: a report's tree that disagrees with the verb's answer of the same minute
+is a tree assembled by hand.
+
 **The short layout** (on a channel such as Telegram, or when nothing changed but time):

 ```