Design 47: release 1-2 is the six milestones R1a to R2c, each one release; playbook 04 splits a milestone that holds a release order (the operator, 2026-10-19)

2026-10-19 00:11:02 +02:00
parent f7915f7f29
commit d10965a341
2 changed files with 18 additions and 6 deletions
@@ -17,7 +17,11 @@ A design becomes **milestones**, and each milestone becomes **issues**:
 - **Milestones are cut by release order.** A milestone ends where one repository's change must be released before
  another can use it (a new manifest word before the catalogue reads it, an SDK change before its users, until
  design 47's milestones 3 and 6 lift those orders); the lead checks this when cutting, so no milestone needs a
-  second release.
+  second release. The orders to look for are those playbook [07](07-feature-branches.md) step 0 item 6 names (an SDK
+  change before its users, a new wire key before the node that reads it, the first module of a repository the catalogue
+  never built, a part that needs a decision first); a milestone cut by such an order may be usable only by the next one,
+  and says so in its outcome. A milestone the prepare step finds holding such an order is split into milestones in the
+  design, each one release, never carried as parts of one (2026-10-18: design 47's release 1-2 became six).
 - **An issue is one repository's part of a milestone,** sized so a fixing agent finishes it inside the
  milestone's development time. Issues that must land in order are linked `depends-on`.