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
@@ -21,12 +21,11 @@ account alone writes its buckets.

 ## How a value resolves

-For every module the seat mesh-placement's placement puts on a node (`mesh-delivery-assigner.placement`, ADR 0567), from the
-controller's mirror of each module's declarations (`mesh-controller.declared-config`): the manifest's default; mesh config for the predefined key the value falls back
+From the controller's mirrors of the assignments and of each module's declarations (`mesh-controller.assignments`,
+`mesh-controller.declared-config`): the manifest's default; mesh config for the predefined key the value falls back
 to; node config for that key on the node; the module's own value on that node, the most specific winning. A value
 naming no predefined key resolves from its default and the module's own value only (ADR 0348 §2). It resolves at
-start, whenever the placement or a mirror moves, and every five minutes, writing only the values that moved. Before
-any node's placement is read nothing is resolved anew, and what is resolved stays.
+start, whenever a mirror moves, and every five minutes, writing only the values that moved.

 ## The verb