A taken container keeps a found network, a left-out module is kept, and genesis raises the forge as its module declares (hq ADR 0163) #64

2026-10-01T21:46:23Z

mesh-admin commented

2026-10-01 21:46:23 +00:00

The host's half of what ADR 0163 left to build after host 63.

Rule 4. A container may name networks it also joins once created — the found network a per-machine setting keeps for a taken container while a neighbour still resolves it there. Joined after the run, part of the container's spec (kept or let go recreates it), refused when it cannot be joined. Not for a run-once or scheduled step.
Rule 6. A declaration may carry left_out: the modules the mesh left out because a stored setting cannot compose with the module's definition. The host keeps what it wrote and holds for a left-out module and says so; before this, absence read as removal. A carried bundle may not say it.
Rule 7 (issue 090). Genesis raises the bootstrap forge under the gitea module's container name, with the module's image digest and the module's data directory mounted at /data, so the module holds it by the found rule instead of raising a second forge. The network is the one difference left for a take to say. Before this the forge had no volume: its repositories were the container's. A test holds the installer's constants to the module's manifest when the catalogue is checked out beside this repository.

Tests: go test ./... green (20 packages).

Merge this before mesh-controller's branch of the same name, and let the host roll on every machine first: an older host refuses an envelope with a field it does not know, and the controller sends networks and left_out only when a setting or a left-out module calls for them — but that is the moment a machine would go unanswered.

The host's half of what ADR 0163 left to build after host 63. - **Rule 4.** A container may name `networks` it also joins once created — the found network a per-machine setting keeps for a taken container while a neighbour still resolves it there. Joined after the run, part of the container's spec (kept or let go recreates it), refused when it cannot be joined. Not for a run-once or scheduled step. - **Rule 6.** A declaration may carry `left_out`: the modules the mesh left out because a stored setting cannot compose with the module's definition. The host keeps what it wrote and holds for a left-out module and says so; before this, absence read as removal. A carried bundle may not say it. - **Rule 7 (issue 090).** Genesis raises the bootstrap forge under the gitea module's container name, with the module's image digest and the module's data directory mounted at `/data`, so the module holds it by the found rule instead of raising a second forge. The network is the one difference left for a take to say. Before this the forge had no volume: its repositories were the container's. A test holds the installer's constants to the module's manifest when the catalogue is checked out beside this repository. Tests: `go test ./...` green (20 packages). **Merge this before mesh-controller's branch of the same name**, and let the host roll on every machine first: an older host refuses an envelope with a field it does not know, and the controller sends `networks` and `left_out` only when a setting or a left-out module calls for them — but that is the moment a machine would go unanswered.

mesh-admin added 1 commit 2026-10-01 21:46:23 +00:00

A taken container keeps a found network, a left-out module is kept, and genesis raises the forge as its module declares (hq ADR 0163) fb9c9c3ee8

A container may name networks it also joins once created, for the per-machine
setting that keeps a found network while a neighbour still resolves it there:
joined after the run, part of the spec, refused when it cannot be joined.

A declaration may say which modules the mesh left out because a stored setting
cannot compose with its definition. Absence used to read as removal; a left-out
module's records are kept and said, and its holds are not released.

Genesis raises the bootstrap forge under the gitea module's container name, with
its image digest and its data directory mounted at /data, so the module holds it
by the found rule instead of raising a second forge beside it (issue 090). The
network is the one difference left for a take to say. Before this the forge had
no volume: its repositories were the container's, lost with it.

mesh-admin merged commit 3b9692b3cb into main

2026-10-02 00:28:17 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-host#64