Answer A-149: the node-engine's own name from its applied store at start

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 09:41:27 +01:00
parent 2b13097956
commit 855149b25b
1 changed files with 3 additions and 0 deletions
@@ -558,3 +558,6 @@ names the principle that settles it, and is cited as "design 47 G A-n".
 - **A-148** (A-145; principle 7, one release one check) A trunk fault that fails a release's own check rides that
  release as its own commit, as fix 1975's distribution test did: the second reader release carries the builder's
  by-hand answer fix (an ask is answered as put only after its put; issue 1126, ADR 0668 §1).
+- **A-149** (§634, §527, A-120; principles 2 and 7) The node-engine knows its own name at start from its applied
+  store: the record of the module whose fingerprint is its own `MESH_FINGERPRINT`; the finding writer, discovery and
+  the vault login use it. Only on a first start with no such record do they wait for the first composing to name it.