Judge how a module says it is ready, beside whether it stays up (hq ADR 0240, to-be 48 Phase B) #50

Merged

mesh-admin merged 2 commits from feat/health-the-field into main 2026-10-07 16:28:34 +00:00

Conversation 2 Commits 2 Files Changed 16

+1260 -19

2 Commits

Author	SHA1	Message	Date
jochen	96bf9415aa	Ask the merge check for this pull request: opening it announced nothing to the build seat	2026-10-07 16:17:40 +02:00
jochen	bdd44154cc	Judge how a module says it is ready, beside whether it stays up (hq ADR 0240, to-be 48 Phase B) ... Liveness alone could not see a web application whose port was open and whose program ran while every request hung for eleven hours (issue 145). A resource now carries the `health` its module declared: the engine makes http and tcp looks itself from the machine to the endpoint's published port, reads a unit's readiness from the show it already makes, hands an exec command or the image's own check to the runtime as the container's check with the declared timing and reads its state from the inspect it already makes, and asks a module's tool on its own node tools. Starting until the check passed, unhealthy once its looks after the grace fail the declared number of times; never more looks than the measured budget; nothing restarted. The statement says contract 2, which tells the controller this engine may be sent the field.	2026-10-07 14:08:32 +02:00