Take mesh-config off the assignments readers: since #558 (issue 1953) it reads placement and its modules' manifests alone (issue 774)

2026-10-29 21:08:02 +01:00
parent 071429c3be
commit 16378e0850
1 changed files with 0 additions and 1 deletions
@@ -4,7 +4,6 @@
 # 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