mesh-catalog

novox/mesh-catalog

Fork 0

...

Author	SHA1	Message	Date
jschoubben	9f9ce92d0f	lavinmq holds mesh-broker again, now the check reads the store The claim comes back for the third and last time. The store's row says the bus seat answers for `amqp`, lavinmq provides `amqp`, and with mesh-controller#89 the check that judges a claim reads that row instead of a copy compiled into the build machine. So this is accepted for the reason it should have been all along. Restores the holder the controller composes its own bus address through, which is what ends tonight's crash loop. nats takes the seat over when the cutover is done deliberately, not because the seat emptied itself.	2026-09-27 22:23:37 +02:00
jschoubben	6e5b2557ba	Merge pull request 'Undo: claiming mesh-broker made lavinmq unbuildable' (#118 ) from revert/broker-seat-claim into main	2026-09-27 19:53:49 +00:00
jschoubben	f97b7dd544	Undo: lavinmq cannot hold mesh-broker, and claiming it makes lavinmq unbuildable Putting the claim back was wrong on its own terms. `mesh-broker` delivers `mesh-bus`, and a seat that delivers a provision may only be held by a module that provides it — so the claim is refused at registration: lavinmq claims mesh-broker, whose holder answers for "mesh-bus", and lavinmq does not provide "mesh-bus" at mesh scope Which means the merged claim does not restore the holder, it stops lavinmq being built at all. Removed again. The seat being empty is still the live fault, and it has only one valid answer: the holder must provide `mesh-bus`, and the module that does is nats. Recorded against the rollout, because it moves a step that was optional into the critical path.	2026-09-27 21:27:55 +02:00

Author

SHA1

Message

Date

jschoubben

9f9ce92d0f

lavinmq holds mesh-broker again, now the check reads the store

The claim comes back for the third and last time. The store's row says the bus seat
answers for `amqp`, lavinmq provides `amqp`, and with mesh-controller#89 the check
that judges a claim reads that row instead of a copy compiled into the build
machine. So this is accepted for the reason it should have been all along.

Restores the holder the controller composes its own bus address through, which is
what ends tonight's crash loop. nats takes the seat over when the cutover is done
deliberately, not because the seat emptied itself.

2026-09-27 22:23:37 +02:00

jschoubben

6e5b2557ba

Merge pull request 'Undo: claiming mesh-broker made lavinmq unbuildable' (#118 ) from revert/broker-seat-claim into main

2026-09-27 19:53:49 +00:00

jschoubben

f97b7dd544

Undo: lavinmq cannot hold mesh-broker, and claiming it makes lavinmq unbuildable

Putting the claim back was wrong on its own terms. `mesh-broker` delivers
`mesh-bus`, and a seat that delivers a provision may only be held by a module that
provides it — so the claim is refused at registration:

  lavinmq claims mesh-broker, whose holder answers for "mesh-bus",
  and lavinmq does not provide "mesh-bus" at mesh scope

Which means the merged claim does not restore the holder, it stops lavinmq being
built at all. Removed again.

The seat being empty is still the live fault, and it has only one valid answer: the
holder must provide `mesh-bus`, and the module that does is nats. Recorded against
the rollout, because it moves a step that was optional into the critical path.

2026-09-27 21:27:55 +02:00

Compare commits

Diff Content Not Available