From eaf011e971f10af3303b084f767518be4659d010 Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 14 Nov 2026 15:53:44 +0100 Subject: [PATCH] Node-engine: a first start whose composing never ends is named by MESH_ENGINE_OWN_MODULE (A-404, live start recovery) A-403 named the engine from the base's catalogue, but on novox the base stops at the first manifest it cannot read, before mesh-host, so the engine stayed unnamed and its seat unserved. --- cmd/mesh-host/main.go | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/cmd/mesh-host/main.go b/cmd/mesh-host/main.go index a788afd5..a7bd3819 100644 --- a/cmd/mesh-host/main.go +++ b/cmd/mesh-host/main.go @@ -992,6 +992,11 @@ func runLink(ctx context.Context, opts options) error { // The engine's own module, first from its applied record of the build whose fingerprint is its own (design 47 G §527, // §634, A-149); on a first start with no such record, from its first composing. own.Set(ownModuleApplied(appliedStoreFor(opts.state), os.Getenv(compositions.FingerprintVar))) + // The live start's recovery (A-404): a first start whose composing never ends is named by its unit's environment, so it + // serves its seat (root-free); the name the assignments place on this node. Ended by the lookup from the bus after G. + if own.Get() == "" { + own.Set(os.Getenv("MESH_ENGINE_OWN_MODULE")) + } queue := &link.Session{ Own: own, Membership: membership,