ADR 0103: what an adopted node holds and what its guard refuses; the node host and connectivity designs name 0102 and 0103

03-DESIGN/01-to-be/05-the-node-host.md

@@ -5,6 +5,8 @@ code: [mesh-host]
 updated: 2026-09-22
 decisions:
   - 02-DECISIONS/0100-a-node-in-use-is-adopted-before-it-is-converged.md
+  - 02-DECISIONS/0102-the-mesh-writes-into-a-shared-file-never-over-it.md
+  - 02-DECISIONS/0103-what-an-adopted-node-holds-and-what-its-guard-refuses.md
   - 02-DECISIONS/0019-how-this-repository-works.md
   - 02-DECISIONS/0004-a-node-and-how-it-joins.md
   - 02-DECISIONS/0005-the-node-host.md
@@ -150,6 +152,18 @@ checked:* unit tests hold the host to keeping a found file and container, conver
 taken, never removing a held file and reporting one that changed; the adoption bed asserts a found
 file byte for byte unchanged until its module is taken.
 
+**Found reaches every kind that can touch what the machine has**
+([ADR 0103](../../02-DECISIONS/0103-what-an-adopted-node-holds-and-what-its-guard-refuses.md)). For a module not yet taken, a directory present with no record
+keeps its mode and owner, a unit present with no record keeps its state and boot setting, a
+container that would mount found data is not created, and an action run in a held container
+waits for the cutover. **A file the machine shares is written into, never over**
+([ADR 0102](../../02-DECISIONS/0102-the-mesh-writes-into-a-shared-file-never-over-it.md)): the host sets the mesh's keys in the object already there,
+keeps every other key, records what each of its keys held before and gives them back when the
+file is undeclared. Such a file replaces nothing, so it is never held. A service that re-reads
+its configuration is **reloaded** for what it names in `reload-on`, never restarted. *How it is
+checked:* unit tests hold the host to each of these, and the adoption bed asserts the runtime's
+own settings survive adoption and a container without a restart policy keeps running.
+
 ## Where a declaration comes from
 
 One behaviour, two sources