The private network writes nothing into the runtime's file; generated resources are collision-checked (hq ADR 0222, issue 190 — 3 of 3) #63

Merged

mesh-admin merged 1 commits from fix/190-the-overlay-writes-no-runtime-file into main

2026-10-05 20:42:32 +00:00

Author	SHA1	Message	Date
jochen	0ebd48a6a8	The private network writes nothing into the runtime's file (hq issue 190) daemon.json and docker.service belong to the docker module, which holds node-container-runtime and now states the registry itself through ${seat:mesh-artifact-store:reach} (hq ADR 0222). The overlay stops generating registry-trust and registry-trust-reload. A generated resource is now held to the collision check every module is, so a second writer cannot come back through computed code; resolution never saw what a generator declares.	2026-10-05 22:19:43 +02:00

Author

SHA1

Message

Date

jochen

0ebd48a6a8

The private network writes nothing into the runtime's file (hq issue 190)

daemon.json and docker.service belong to the docker module, which holds node-container-runtime
and now states the registry itself through ${seat:mesh-artifact-store:reach} (hq ADR 0222). The
overlay stops generating registry-trust and registry-trust-reload. A generated resource is now
held to the collision check every module is, so a second writer cannot come back through
computed code; resolution never saw what a generator declares.

2026-10-05 22:19:43 +02:00