jschoubben b58a3b487d A build's outcome belongs to the role, not to the module holding it ...

ADR 0121. The builder declared `built` as its own event, so every consumer depended
on which module happens to be the build machine today. It is the build-machine
role's event now: the builder declares none of its own, and the catalogue listens
for `mesh-build-machine.built` rather than `builder.built`.

Nothing changes about what reaches the catalogue. What changes is that it survives
the build machine being a different module, which is the whole reason the mesh has a
word for a role.

2026-09-27 15:37:21 +02:00

..

tools

The graph holds what a module declares, not only what it was built on

2026-09-13 01:44:56 +02:00

Dockerfile

Modules compile in the toolchain and ship on the runtime

2026-09-14 01:57:06 +02:00

index.ts

A build's outcome belongs to the role, not to the module holding it

2026-09-27 15:37:21 +02:00

module.json

A build's outcome belongs to the role, not to the module holding it

2026-09-27 15:37:21 +02:00

package.json

The catalogue, as a module that owns the module graph

2026-09-12 23:16:05 +02:00

pg.d.ts

The catalogue, as a module that owns the module graph

2026-09-12 23:16:05 +02:00

store.ts

Six modules take their secrets from files; the rest say precisely why not

2026-09-21 12:29:25 +02:00

tsconfig.json

The catalogue, as a module that owns the module graph

2026-09-12 23:16:05 +02:00