From 14b5b324a258ae8e5c2c44ccbc7d37caa780813a Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 13 Nov 2026 09:17:36 +0100 Subject: [PATCH] Answer A-342: the node-engine sets MESH_NODE for every process it runs Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 77054c08..9187bf39 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -674,3 +674,8 @@ the principle that settles it, cited as "design 47 G A-n". `module`, id `zfs..` (the pool's own state: `zfs..pool`), kind `not-online`, its subject scope `module`, id `zfs`, on the node; `` is the device's own name, the last element of its path. ยง27's one finding per device not online stands; only its key takes the writer's form. +- **A-342** (A-339, A-341; principles 2, 7) A process learns its node the way the SDK already reads it: the node-engine + sets `MESH_NODE` to its own node's name in the environment of every process it runs, beside the resource's own `env` + (a resource's own `MESH_NODE` is refused by the manifest validator, so the mesh's value is the only one). The zfs + follower's writer and its `node-service-manager` calls then name the node; no new reference form and nothing special to + the keeper.