One name per thing, per the HQ glossary: the module/container/image/binary/repo becomes mesh-controller, the seat the-controller, and the store+broker pair the foundation (embedded base bundles, default template and example lock renamed with their go:embed directives). No behaviour change — a pure vocabulary rename. Claude-Session: https://claude.ai/code/session_01D6qtiYU3P9jk3pnAXyAFyx
31 lines
1.0 KiB
YAML
31 lines
1.0 KiB
YAML
# One machine that becomes a mesh and then assigns itself plex's tool runtime.
|
|
#
|
|
# The audit-node bed proved an assigned *consumer* (novox/hq ADR 0048). This proves an assigned
|
|
# module that *serves tools* (ADR 0052): the same first-node foundation, plus plex's tool runtime on
|
|
# top. The node enrols itself, the mesh issues plex a broker account scoped to serve.plex.* and
|
|
# assigns it, the host runs the runtime container, and a caller invokes plex.plex_reachable over the
|
|
# mesh — proof the module runs its own code as its own process under its own scoped account.
|
|
scenario: plex-node
|
|
|
|
segments:
|
|
hosting:
|
|
kind: public
|
|
cidr: [192.0.2.0/24]
|
|
|
|
machines:
|
|
anchor:
|
|
at: { segment: hosting, address: [192.0.2.10] }
|
|
egress: true
|
|
inbound: allow
|
|
memory: 3GiB
|
|
cpus: 2
|
|
|
|
images:
|
|
- mesh-controller:development
|
|
# Plex's tool runtime, built by scripts/build-module-runtime.sh plex into the local daemon and
|
|
# loaded onto the machine, which holds it by its own image ID.
|
|
- mesh-runtime-plex:development
|
|
|
|
place:
|
|
all: [host, runtime]
|