From b5b84fafc631f61fc55543f4a1acae3348b5330a Mon Sep 17 00:00:00 2001 From: jochen Date: Mon, 26 Oct 2026 18:21:31 +0100 Subject: [PATCH] Design 47: config placement, as ADR 0348 words it (issue 1126) --- 03-DESIGN/01-to-be/47-delivery-from-commit-to-delivered.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/03-DESIGN/01-to-be/47-delivery-from-commit-to-delivered.md b/03-DESIGN/01-to-be/47-delivery-from-commit-to-delivered.md index 71de04bb..c3422466 100644 --- a/03-DESIGN/01-to-be/47-delivery-from-commit-to-delivered.md +++ b/03-DESIGN/01-to-be/47-delivery-from-commit-to-delivered.md @@ -690,7 +690,7 @@ backup holder backs up nothing, and the have says so. routed names are composed under, its operator and agent logins by name with their homes, and whether it is adopted with the modules taken on it. No secret and no key material; - its modules in the order the composition reads them, each with its host ports by the port the software - listens on, its bindings by provision, and its settings placement (`places`, `accesses`, `networks`, + listens on, its bindings by provision, and its config placement (`places`, `accesses`, `networks`, `endpoints`, `expose`, `reach`, `ports`) as two layers: the mesh-wide one, repeated in every node's file so a node reads its own key alone, and the node's own, with a mark when the node has a layer that holds no placement, since an empty layer still carries the module's config values;