diff --git a/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md index 49d513e4..c0649e9c 100644 --- a/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md @@ -957,3 +957,7 @@ The lead's one-line answers to the questions H2's develop and review raise (impl words with the setting's composed value and never a value the engine composed before. The config seat's resolved value of a key is composed again when its declaration (its default) changes; until that is built, the engine's composed value wins over a stale resolve, said in the journal. P-failure-loud, P3. +- **H-A-477 (addendum, 16:55)** The second sentence asks no node-engine code in this fix: the live refusal itself says + the engine composed the setting as 5 (the manifest's default), so a resolve with source "default" does not reach + the node's layer today. The config seat composing a key again when its declaration changes is the next milestone's + item, with a journal line in the engine if a stale resolve ever wins. P-evidence.