Playbook 04 and design 47: the milestone is one release, not a feature step (review of #401)

2026-10-17 13:47:37 +02:00
parent 6bf18062c4
commit addbd74c39
3 changed files with 7 additions and 7 deletions
@@ -44,9 +44,9 @@ A design becomes **milestones**, and each milestone becomes **issues**:
   entry in the design.
 7. **Flip the status.** `status: in-progress`, `updated:` today; the design change goes through playbook
   [08](08-small-fixes.md) (one hq pull request).
-8. **Hand each milestone to playbook 07, one at a time.** The milestone is the feature step; its issues are the
-   step's issues; the next milestone starts when the previous one's delivery plan is done. A design waits while
-   another design's milestones are being built: one design is built at a time (playbook
+8. **Hand each milestone to playbook 07, one at a time.** The milestone is one release of playbook 07; its issues
+   are the release's issues; the next milestone starts when the previous one's delivery plan is done. A design waits
+   while another design's milestones are being built: one design is built at a time (playbook
   [07](07-feature-branches.md)), so this step starts only when the design before it is delivered.
 9. **On completion of the last milestone**, run the "when something ships" section of playbook
   [02](02-graduation.md).
@@ -250,9 +250,9 @@ left, its frontmatter still saying `designed`, read to another session as not bu
 was started beside it (issue 1009, 2026-10-17). So the lead writes the design's state back at each of these
 moments, the same hour, an hq change going through [playbook 08](08-small-fixes.md):

- **The first step starts:** the design's `status: in-progress` ([playbook 04](04-build-handoff.md) step 7),
+- **The first milestone starts:** the design's `status: in-progress` ([playbook 04](04-build-handoff.md) step 7),
  if it is not already.
- **A step's delivery plan is done:** its issues are resolved (phase 4), and the design's milestone entry says
+- **A milestone's delivery plan is done:** its issues are resolved (phase 4), and the design's milestone entry says
  it is delivered, with the date.
 - **The building pauses with work left** (another design takes its turn, a hand-over, the session's end): the
  design stays `in-progress`, and each issue left gets a note with `issue-tracker.note` saying what it waits
@@ -485,8 +485,8 @@ What the build proves before this design is implemented (research 055's directio

 ## Milestones

-Confirmed by the operator on 2026-10-17 (playbook 04). Each is one feature step of playbook 07; the next starts
-when the previous one's delivery is done. Each milestone is one release (playbook 07).
+Confirmed by the operator on 2026-10-17 (playbook 04). Each is one release of playbook 07; the next starts
+when the previous one's delivery is done.

 | # | Outcome | Acceptance tests | Repositories | Issues |
 |---|---|---|---|---|