Design 58: the operator confirmed the milestones; issues 878 to 887, building after design 57's delivery (playbook 04)

2026-10-16 09:55:11 +02:00
parent 45e2d7e972
commit 43c3f2c098
1 changed files with 7 additions and 0 deletions
@@ -164,6 +164,13 @@ the previous one's is. What it replaces is in the as-is documents
 [16 — Logins on the bus](../00-as-is/16-logins-on-the-bus.md). The issues are opened once the operator confirms
 the milestones, and their numbers written here.

+**Confirmed by the operator on 2026-10-16.** One issue per milestone: 1 is issue 878, 2 is 879, 3 is 880, 4 is
+881, 5 is 882, 6 is 883, 7 is 884, 8 is 885, 9 is 886, 10 is 887. A milestone's issue is split into one issue per
+repository part when its feature step starts (playbook 07): several of the parts are modules that do not exist yet,
+and the issue tracker takes only registered owners. The building waits until the delivery under way of
+[57 — Building config and provisioning](57-building-config-and-provisioning.md) is done; the status here stays
+`designed` until milestone 1 starts.
+
 | # | Outcome, in one sentence | Proves | Repositories and their parts | Depends on |
 |---|---|---|---|---|
 | 1 | Every tool on the mesh says whether it reads, acts or is dangerous, a tool's description shows it, and the catalogue refuses a module that leaves one unmarked | test 3 | mesh-sdk: the effect in a tool's declaration, an unmarked tool served as dangerous; mesh-controller: the manifest field; mesh-catalog and mesh-media-catalog: every module marked, the check | — |