Files
mesh-controller/internal/inventory/migrations/0017-what-a-machine-already-holds.sql
jschoubben c3b88b9148 Rename mesh-control -> mesh-controller, substrate -> foundation
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
2026-09-16 18:40:40 +02:00

13 lines
729 B
SQL

-- Ports a machine holds that the mesh did not assign.
--
-- novox/hq ADR 0038. The foundation is not a module: a node raises it from the bundle it carries
-- before any mesh exists, so the control plane has never heard of the store or the broker. Told
-- what they hold, it can put a module somewhere else; not told, it hands out a port one of them
-- has and finds out from a container runtime three layers down.
--
-- On the node rather than in the assignment table, because these are not assignments -- nothing
-- here chose them, and nothing here can move them. They are a fact about the machine, replaced
-- whole each time the machine states it.
alter table node add column carried_ports integer[] not null default '{}';