jschoubben fccc1e6552 The foundation modules claim a mesh-scoped seat named after their server ...

postgres claims mesh-store, lavinmq claims mesh-broker, and the controller's seat is
renamed the-controller -> mesh-controller so all three follow one convention. The resolver
refuses a second holder mesh-wide, so an adopted foundation module assigned to a second node
is refused rather than silently raising a second server. Closes hq issue 056 (ADR 0079).

https://claude.ai/code/session_01D6qtiYU3P9jk3pnAXyAFyx

2026-09-17 02:13:26 +02:00

..

bootstrap

Add lavinmq amqp provider and amqp-ping consumer

2026-09-06 15:50:19 +02:00

provisioner

Add lavinmq amqp provider and amqp-ping consumer

2026-09-06 15:50:19 +02:00

tools

Add lavinmq amqp provider and amqp-ping consumer

2026-09-06 15:50:19 +02:00

client.ts

Add lavinmq amqp provider and amqp-ping consumer

2026-09-06 15:50:19 +02:00

Dockerfile

Convert lavinmq: it is not only a broker, so it has to be built

2026-09-14 21:05:10 +02:00

index.ts

Add lavinmq amqp provider and amqp-ping consumer

2026-09-06 15:50:19 +02:00

module.json

The foundation modules claim a mesh-scoped seat named after their server

2026-09-17 02:13:26 +02:00

package.json

Add lavinmq amqp provider and amqp-ping consumer

2026-09-06 15:50:19 +02:00

tsconfig.json

Add lavinmq amqp provider and amqp-ping consumer

2026-09-06 15:50:19 +02:00