From 79dcc0a6ec37d89801b7d5b6e1ec2e12340fa48a Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 17 Oct 2026 13:35:20 +0200 Subject: [PATCH] Give design 57 its milestones and check every write-back moment (issue 1009, review round 1) --- 00-META/process/07-feature-branches.md | 6 +++++- .../57-building-config-and-provisioning.md | 18 ++++++++++++++---- 2 files changed, 19 insertions(+), 5 deletions(-) diff --git a/00-META/process/07-feature-branches.md b/00-META/process/07-feature-branches.md index cd4533fc..30e949b2 100644 --- a/00-META/process/07-feature-branches.md +++ b/00-META/process/07-feature-branches.md @@ -243,7 +243,7 @@ next action; then the prompt the operator pastes. The context files make the fea ## The design's state is written back Other sessions know what is built only from the design's frontmatter and the issue tracker; what the lead -knows and does not write back, nobody else knows. A design merged as one release with three of its tasks +knows and does not write back, nobody else knows. A design merged in one delivery with three of its tasks left, its frontmatter still saying `designed`, read to another session as not built, and a second design 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): @@ -276,6 +276,10 @@ issues in `fixing` that nobody works on reads to the operator as stuck work. - A design whose milestone issues are partly resolved says `in-progress`, and one whose issues are all resolved and delivered says `implemented`: read its Milestones section against `issue-tracker.get` for each issue. A design that says `designed` with a resolved milestone issue is a state not written back. +- A milestone whose issues are all resolved and delivered has the date in its entry in the design's Milestones + section; an entry without it is a delivery not written back. +- Every open issue of a design that says `in-progress` and has no agent on it shows, in `issue-tracker.get`, a + note saying what it waits for; one without such a note is a pause not written back. - The milestone issues in `fixing` (`issue-tracker.list`) belong to one design at most: milestone issues of two designs in `fixing` at once is the failure of "one design is built at a time". - More than one open pull request in a repository that share no feature name, or a feature step whose issues diff --git a/03-DESIGN/01-to-be/57-building-config-and-provisioning.md b/03-DESIGN/01-to-be/57-building-config-and-provisioning.md index 80da4148..87cb7c7a 100644 --- a/03-DESIGN/01-to-be/57-building-config-and-provisioning.md +++ b/03-DESIGN/01-to-be/57-building-config-and-provisioning.md @@ -61,10 +61,9 @@ both, by the form of its manifest, and the old forms stay accepted until the las Inside the release this still holds: the media catalogue and the applications kept in their own repositories move after it, so the old forms stay accepted until they have (R1). -**Where it stands, 2026-10-17.** The release is merged into main of mesh-controller, the node-engine -(`mesh-host`) and mesh-catalog, and delivered. Every package but B3, R1 and R2 is resolved. Those three -(issues 680, 682 and 683) are built after design 47's milestones are delivered and before design 58 starts, -the operator's decision of 2026-10-17 (one design is built at a time, playbook 07). +**Where it stands, 2026-10-17** (the Milestones section below). The packages' branches were merged into +main of mesh-controller, the node-engine (`mesh-host`) and mesh-catalog on 2026-10-16. T6 moved after them, as +planned above, and is resolved. B3 was left out as well, so B3, R1 and R2 are what is left. ## What exists already, measured @@ -338,6 +337,17 @@ removed code. amended, the 67 documents that still say "setting" in running prose are reworded so the glossary can retire the word (F4 left it off the *Not:* line for them), design 49 lists the Config domain, ADR 0348's and 0349's built status is said, and this document's status becomes `implemented`. +## Milestones + +Written back on 2026-10-17 (playbook 07, "The design's state is written back"): the packages above were built +as one delivery, not milestone by milestone, so the milestones are what was delivered and what is left. + +| # | Outcome | Packages | Issues | State | +|---|---|---|---|---| +| 1 | Config, provisioning, secrets, bindings, collections and runtime asks run the new way; the old forms are still accepted | every package but T6, B3, R1, R2 | 647, 650 to 679 but 659, 681, 684, 685 | merged into main on 2026-10-16; issues resolved | +| 2 | The media catalogue and the applications carry their file text as templates | T6 | 659 | resolved | +| 3 | The other providers answer their consumers; the old forms are refused; the record says what runs | B3, R1, R2 | 680, 682, 683 | open: built after design 47's milestones are delivered and before design 58 starts (the operator, 2026-10-17; one design is built at a time, playbook 07) | + ## What is deliberately not here - **Secrets in a module's own code** wait on issue 569 (a module's tools run as the tool runner's