mesh-config reads the placement beside the controller's assignments while both stand, as L2 has it and the vault does, and is listed as a reader of them (issue 774, ADR 0549 §5; re-review)

2026-10-28 21:54:36 +01:00
parent 5be6576117
commit 10447d8c1e
9 changed files with 101 additions and 90 deletions
@@ -4,6 +4,7 @@
 # controller (novox/hq ADR 0549 §3, §6; issue 774).
 gitea          the provisioner's plan of a module (go/provider) rides only in an assignment's value; its home after the lease is issue 774's provisioner-plan subtask
 keycloak       the provisioner's plan of a module (go/provider), as gitea
+mesh-config    unioned with the placement while both stand, as the assigner and the vault do (ADR 0549 §5); its reading placement alone is a step before the lease write
+mesh-vault     the provisioner's plan, which only an assignment's value carries; its home is issue 774's provisioner-plan subtask
 postgres       the provisioner's plan of a module (go/provider), as gitea
 route-adapter  the provisioner's plan of a module (go/provider), as gitea
-mesh-vault     the provisioner's plan, which only an assignment's value carries; its home is issue 774's provisioner-plan subtask