Graduates research 022 (WP4c). Measured: of the 23 remaining runtime containers, a handful subscribe to events; 12 run provisioners (files + backend + emit, already expressible as a launched bundle); one prepare step; CLIs psql/mosquitto_ctrl/git are system packages, mongosh/sqlcmd are not; five services reached by container name.
Decided: the node's runtime launches a module's long-running code as it does tools and is its bus — mesh/subscribe (the runtime binds the module's own durable consumer, delivers each event as mesh/event, acks only after the child answered) and mesh/ask beside mesh/publish. Prepare steps are run-once processes. Container-network reach becomes loopback ${port:…} and system packages, or a driver in the bundle (mongodb, mssql). Options weighed: per-module bus clients (rejected as in ADR 0188); keep the containers. Design 38 WP4c gains the order and three waves. Checks pass.
Graduates research 022 (WP4c). Measured: of the 23 remaining runtime containers, a handful subscribe to events; 12 run provisioners (files + backend + emit, already expressible as a launched bundle); one prepare step; CLIs psql/mosquitto_ctrl/git are system packages, mongosh/sqlcmd are not; five services reached by container name.
Decided: the node's runtime launches a module's long-running code as it does tools and is its bus — `mesh/subscribe` (the runtime binds the module's own durable consumer, delivers each event as `mesh/event`, acks only after the child answered) and `mesh/ask` beside `mesh/publish`. Prepare steps are run-once processes. Container-network reach becomes loopback `${port:…}` and system packages, or a driver in the bundle (mongodb, mssql). Options weighed: per-module bus clients (rejected as in ADR 0188); keep the containers. Design 38 WP4c gains the order and three waves. Checks pass.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Graduates research 022 (WP4c). Measured: of the 23 remaining runtime containers, a handful subscribe to events; 12 run provisioners (files + backend + emit, already expressible as a launched bundle); one prepare step; CLIs psql/mosquitto_ctrl/git are system packages, mongosh/sqlcmd are not; five services reached by container name.
Decided: the node's runtime launches a module's long-running code as it does tools and is its bus —
mesh/subscribe(the runtime binds the module's own durable consumer, delivers each event asmesh/event, acks only after the child answered) andmesh/askbesidemesh/publish. Prepare steps are run-once processes. Container-network reach becomes loopback${port:…}and system packages, or a driver in the bundle (mongodb, mssql). Options weighed: per-module bus clients (rejected as in ADR 0188); keep the containers. Design 38 WP4c gains the order and three waves. Checks pass.