A push raises what a module hears, not only a start #132

Merged

mesh-admin merged 1 commits from fix/a-push-raises-what-a-module-hears into main

2026-09-28 14:46:55 +00:00

Author	SHA1	Message	Date
jschoubben	878690697e	A push raises what a module hears, not only a start A module's declaration and its consumer are derived from the same records, and only one of them followed a push: the consumers were raised when the control plane started serving, so a module that gained a `consumes` was sent a declaration it could act on and a consumer that never delivered the event — with nothing anywhere saying the two disagreed. Found on review: the catalogue's own replay subscription was recorded, granted and never delivered. Everything the raise does is idempotent, so a push may do it.	2026-09-28 16:46:42 +02:00

Author

SHA1

Message

Date

jschoubben

878690697e

A push raises what a module hears, not only a start

A module's declaration and its consumer are derived from the same records, and only one of them
followed a push: the consumers were raised when the control plane started serving, so a module that
gained a `consumes` was sent a declaration it could act on and a consumer that never delivered the
event — with nothing anywhere saying the two disagreed. Found on review: the catalogue's own replay
subscription was recorded, granted and never delivered.

Everything the raise does is idempotent, so a push may do it.

2026-09-28 16:46:42 +02:00