Say that a set shared value stands between a new default and the assignments it reached (ADR 0319 review)
mesh/merge-gate pass: the change touches no module of the mesh's graph
mesh/repo-check pass: its merge-check.sh passed
mesh/delivery superseded: a newer head of the same pull request

This commit is contained in:
jochen
2026-10-12 13:41:53 +02:00
parent 7af2ebe45e
commit f8547279cb
@@ -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