Files

T

jschoubben f509c61b50 VERSION (A-46, §368, §411): every manifest of the catalog says its version MAJOR.MINOR

mesh-delivery-builder.builder_versions answered no numbered version for any name asked (mesh-sdk go and ts, mesh-host, node-tools, mesh-delivery-builder, mesh-conditions), so every module takes 0.1, the floor §368 gives a module with none published: all 144 manifests (141 from "1", distribution, mesh-provisioner and mesh-provisioner-client from "2", which carries nothing over, §583).

Builds: design 47 G §368, §411, §583, A-46

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

2026-11-11 22:38:45 +01:00

module.json

VERSION (A-46, §368, §411): every manifest of the catalog says its version MAJOR.MINOR

2026-11-11 22:38:45 +01:00

README.md

Say in the go and nodejs READMEs that they are now the only declarers (issue 1573)

2026-10-21 09:51:22 +00:00

README.md

go

The Go toolchain as a module (novox/hq ADR 0477 clause 4, issue 1573).

The only module that declares the package go. checks/toolchains refuses any other that does.
Provides go-toolchain with the machine's reach: dev-tools, lab and mesh-build-go require it, so each composes only on a machine where this module is assigned. It is never pulled in for whatever asked, so go is assigned to a node on purpose, and a node without it refuses those modules at resolution.
Holds no long-running resource, so it adds nothing to health-undeclared.

The node-engine never uninstalls a package, so moving the declaration here removed nothing from a node.