From f8547279cb992f8104c66a3fa02fbb2b9933e1f1 Mon Sep 17 00:00:00 2001 From: jochen Date: Mon, 12 Oct 2026 13:41:53 +0200 Subject: [PATCH] Say that a set shared value stands between a new default and the assignments it reached (ADR 0319 review) --- 03-DESIGN/01-to-be/27-a-module-requires-the-mesh-resolves.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/03-DESIGN/01-to-be/27-a-module-requires-the-mesh-resolves.md b/03-DESIGN/01-to-be/27-a-module-requires-the-mesh-resolves.md index 3f86ef2c..42dff768 100644 --- a/03-DESIGN/01-to-be/27-a-module-requires-the-mesh-resolves.md +++ b/03-DESIGN/01-to-be/27-a-module-requires-the-mesh-resolves.md @@ -221,7 +221,8 @@ reads the shared value, and only when that is unset too its default; read from t winning: the default, the shared value, the module's mesh-wide layer, the node's. So a person sets the interface font size once and every module that names it follows, while any one module or node can still be set apart in its own layer. A shared value is a fourth place of change beside the three -of ADR 0164, and the plan of a change to it names every assignment, of every module that reads it, +of ADR 0164 (a new default no longer reaches an assignment whose shared value is set), and the plan +of a change to it names every assignment, of every module that reads it, whose effective value moves. It is set and cleared through the `settings` verb without a module, and both `settings` listings name the shared name as a value's source beside the default, the mesh and the node. **A shared value reaches no trusted setting** (ADR 0319): a trusted setting may not declare a