mesh-controller

Files

T

jochen 28c7f05b39 A resolved manifest keeps a built reference in the store's own form, never the address it was reached by (hq ADR 0155)

The first bundle resolved on the mesh carried the store's host in bundles[0].source, and registration
refused node-tools as naming an installation — rightly. The build record already keeps the
store-relative form; the resolved manifest now keeps the same for bundles and archive resources,
and composition routes it through the store a machine reaches, as it already did for a kept one.

2026-10-02 23:13:22 +02:00

broker

The machine runs one tool runtime, loading every delivered bundle (hq ADR 0175, to-be 38 WP2.3)

2026-10-02 18:26:54 +02:00

builder

A TypeScript bundle carries what it runs with: the toolchain's runtime directory is copied into it (hq to-be 38 WP3, ADR 0188)

2026-10-02 21:44:44 +02:00

catalogue

A resolved manifest keeps a built reference in the store's own form, never the address it was reached by (hq ADR 0155)

2026-10-02 23:13:22 +02:00

envfile

An address is read from the node's settings where it is used, never recorded with a port