The host self-updates, and an archive cannot be undeclared #212

2026-09-30T11:16:38Z

jschoubben commented

2026-09-30 11:16:38 +00:00

161 resolved and verified on a machine. The workstation runs a host the mesh compiled, published, delivered and started — applying declarations and reporting the version it was delivered as.

The system it was built for comes from the artifact (the one thing a toolchain takes from a module, which ADR 0142 already allowed). The version comes from where the binary sits, which 0142 decided and nothing had implemented.

Two mistakes on the way, both caught by reading the output rather than the line claiming success: a second -ldflags does not merge with the first (the binary gained its system and lost -s -w, 12.2MB against 8.5MB), and the delivered binary was named after its package so the first delivery was correct, reported success and was invisible to the launcher.

A delivered host that cannot apply is a machine the mesh cannot repair — the declaration that would fix it is the one it cannot apply. The launcher's fallback made that an inconvenience instead of an expedition.

162 is new and not about the host: an archive has no removal, so a module using one can never be unassigned, and the attempt takes the whole apply with it — the machine applies nothing else either. It is how undoing the first delivery froze the workstation.

Three machines still run a hand-placed host; each is one assignment and one push.

**161 resolved and verified on a machine.** The workstation runs a host the mesh compiled, published, delivered and started — applying declarations and reporting the version it was delivered as. The system it was built for comes from the artifact (the one thing a toolchain takes from a module, which ADR 0142 already allowed). The version comes from where the binary sits, which 0142 decided and nothing had implemented. Two mistakes on the way, both caught by reading the output rather than the line claiming success: a second `-ldflags` does not merge with the first (the binary gained its system and lost `-s -w`, 12.2MB against 8.5MB), and the delivered binary was named after its package so the first delivery was correct, reported success and was invisible to the launcher. A delivered host that cannot apply is a machine the mesh cannot repair — the declaration that would fix it is the one it cannot apply. The launcher's fallback made that an inconvenience instead of an expedition. **162 is new and not about the host:** an archive has no removal, so a module using one can never be unassigned, and the attempt takes the whole apply with it — the machine applies nothing else either. It is how undoing the first delivery froze the workstation. Three machines still run a hand-placed host; each is one assignment and one push.

jschoubben added 1 commit 2026-09-30 11:16:38 +00:00

The host self-updates, and an archive cannot be undeclared 3c535ead31

161 resolved and verified on a machine: the workstation runs a host the
mesh compiled, published, delivered and started, applying declarations
and reporting the version it was delivered as.

The system it was built for comes from the artifact — the one thing a
toolchain takes from a module, which 0142 already allowed because the
target is a property of the artifact. The version comes from where the
binary sits, which 0142 decided and nothing had implemented.

Two mistakes on the way, both caught by reading the output rather than
the line that claimed success. A second -ldflags does not merge with the
first: the binary gained its system and lost -s -w, 12.2MB against 8.5MB.
And the delivered binary was named after its package, so the first
delivery was correct, reported success and was invisible to the launcher.

A delivered host that cannot apply is a machine the mesh cannot repair,
because the declaration that would fix it is the one it cannot apply. The
launcher's fallback is what made that an inconvenience instead of an
expedition.

162 is new and not about the host: an archive has no removal, so a module
using one can never be unassigned, and the attempt takes the whole apply
with it — the machine applies nothing else either. It is how undoing the
first delivery froze the workstation.

jschoubben merged commit a841e2c173 into main

2026-09-30 11:16:44 +00:00

jschoubben deleted branch issue/161-resolved-and-162-an-archive-cannot-be-removed

2026-09-30 11:16:44 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#212