From 2a27c38beb6d32c545d8fa210f774f683a66c40f Mon Sep 17 00:00:00 2001 From: jochen Date: Tue, 13 Oct 2026 20:33:28 +0200 Subject: [PATCH] Design 27: a served own name with a default, or nested, is refused too (ADR 0346, review 224) --- 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 8187bbe3..45114fdc 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 @@ -290,7 +290,8 @@ the consumer's own, so the binding and the proxy name one host. Where the provid no such name (it has no public domain, or the endpoint is not reached publicly), the key is left out of what the consumer is told, and `plan` says so on the provider's machine and under the consumer's need. *How it is checked:* the module check refuses a served value naming a requirement the module does not -contribute to or a fact other than those names; the controller's unit tests for both paths and for the +contribute to or a fact other than those names, one with a default (`|default:`), and one nested in a +list or an object; the controller's unit tests for both paths and for the left-out key, each run against the unchanged controller first. ## How a definition reads what was resolved