lavinmq, amqp-ping and amqp-email-forwarder leave the catalogue #120

2026-09-27T21:29:17Z

jschoubben commented

2026-09-27 21:29:17 +00:00

AMQP is not a provision (hq ADR 0131, design 28 task 5.4). These were the only three manifests that named it: the broker that provided it, a proof that a grant worked end to end, and a forwarder reading mail off a queue. Removed rather than converted — a module that wants messaging wants the mesh's bus, reached through the sdk and named by the mesh-broker seat; either of the last two is re-done against that if wanted, as a new module under the record.

Pairs with mesh-controller feat/amqp-is-not-a-provision, whose parser refuses a manifest naming amqp from its next release, so these could not be re-registered anyway. Nothing else in the catalogue referenced them.

This removes them from the catalogue. The running mesh keeps its registered lavinmq until the seat is handed to nats and it is unassigned — that is the live half of 5.4, after the cutover.

AMQP is not a provision (hq ADR 0131, design 28 task 5.4). These were the only three manifests that named it: the broker that provided it, a proof that a grant worked end to end, and a forwarder reading mail off a queue. Removed rather than converted — a module that wants messaging wants the mesh's bus, reached through the sdk and named by the `mesh-broker` seat; either of the last two is re-done against that if wanted, as a new module under the record. Pairs with mesh-controller `feat/amqp-is-not-a-provision`, whose parser refuses a manifest naming `amqp` from its next release, so these could not be re-registered anyway. Nothing else in the catalogue referenced them. This removes them from the *catalogue*. The running mesh keeps its registered lavinmq until the seat is handed to nats and it is unassigned — that is the live half of 5.4, after the cutover.

jschoubben added 1 commit 2026-09-27 21:29:17 +00:00

lavinmq, amqp-ping and amqp-email-forwarder leave the catalogue b9605a6e3b

AMQP is not a provision (novox/hq ADR 0131, design 28 task 5.4). These were the
only three manifests that named it: the broker that provided it, a proof that a
grant worked end to end, and a forwarder reading mail off a queue. Removed, not
converted — a module that wants messaging wants the mesh's bus, reached through
the sdk and named by the mesh-broker seat, and either of the last two is re-done
against that if wanted, as a new module under the record.

The controller refuses a manifest naming amqp from its next release, so these
could not be re-registered anyway. Nothing else in the catalogue referenced them.

jschoubben merged commit c0edebefb9 into main

2026-09-27 21:30:20 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-catalog#120