mesh-controller

Files

T

jochen cdebb7d1a5 Compose a process's environment as a container's

A module's own code moving out of its container (novox/hq to-be 38 WP4c)
becomes a process on the machine, and still has to be told what its
container was: the port this machine gave the module and where the
foundation's seats are. ${port:…} and ${seat:…} were filled only in a
file's content and a container's env, so in a process's env they reached
the machine as literals, and the modules that moved first (mesh-catalog
#245) wrote their run-once steps a 0600 env file instead. A process's env
now takes the same resolution and the same refusals; ${dir:…} and
${access:…} already did, and a bundle's env (ADR 0192) already resolves
${dir:…} and ${port:…}.

2026-10-04 00:27:42 +02:00

broker

The node's runtime reads the consumers of the modules it carries (hq ADR 0198)

2026-10-03 22:30:55 +02:00

builder

Run the toolchain's esbuild as itself: npm installs its native binary in place of the script

2026-10-03 23:26:08 +02:00

catalogue

Compose a process's environment as a container's

2026-10-04 00:27:42 +02:00

envfile

An address is read from the node's settings where it is used, never recorded with a port