Design 47 H2: H-A-400, a taken key only for an act that acted; TypeScript reads the composed setting word

This commit is contained in:
2026-11-22 00:47:02 +01:00
parent c3246cfeb4
commit 9b981693df
@@ -252,3 +252,11 @@ The lead's one-line answers to the questions H2's develop and review raise (impl
a need (H-A-375 reads the same); mesh-sdk's S10 value `node-modules` is corrected to a list of seat names, a one-line
commit in the mesh-sdk worktree by the build modules' developer citing this answer. RG2 covers artifact-store-tools
as the map says. P-NATS-native, P3, ADR 0596.
- **H-A-400 (a taken key is kept only for an act that acted; a TypeScript module reads a setting from the composed
word, 00:49)** §775, C2. (1) The holder keeps the taken key `git.<ask>` only when the act acted; an answer that
performed nothing (away, a transport fault, a refusal before any act) drops the key, so the kept call's repeat under
the same id acts, as §776 ("a merge call answers away and lands when called again") and §807's owed act need.
H-A-381 (1)'s "never happened" refusal holds for a key whose act acted and whose state is gone. (2) A TypeScript
module reads a setting from the word the node-engine composes into its process environment, MESH_CONFIG_<KEY>
(H-A-370, E3), here MESH_CONFIG_ASK_TAKEN_BOUND, never from its config file: one word for a setting in every language;
the config file keeps only what no setting names. P3, H-A-370, ADR 0668 §2.