Read how a module says each resource is ready, and send it to engines that read it (hq ADR 0240, to-be 48 Phase B) #110

Merged

mesh-admin merged 1 commits from feat/health-the-field into main 2026-10-07 16:32:26 +00:00

Conversation 4 Commits 1 Files Changed 22

+1205 -10

1 Commits

Author	SHA1	Message	Date
jochen	b98fd0f396	Read how a module says each resource is ready, and send it to engines that read it (hq ADR 0240, to-be 48 Phase B) ... A module could say nothing about what ready means for what it runs, so a web application with its port open and its requests hanging passed everything for eleven hours (issue 145). A long-running resource now carries `health` — the image's own check adopted by name, http, tcp, exec, unit or a module's own tool, with its timing — refused near its author when it names a port or an address, an endpoint the module does not declare, a tool it does not serve, a tool check alone, or a timing outside the record's bounds. It is composed with the endpoint as the port this machine published it on, and sent only to a node-engine whose statement says it reads it: an older one would refuse the whole declaration. The engine is granted its own machine's instance of each health tool. `module check` warns of every long-running resource without `health`, counts them for the catalogue, and refuses them from 2026-11-18. A check's findings stay out of a condition's summary. The node-engine's validator is vendored at its Phase B commit, so what is composed is judged by the words the engine takes.	2026-10-07 16:17:50 +02:00