ADR 0103: a unit is found when an administrator installed it or the machine uses it

02-DECISIONS/0103-what-an-adopted-node-holds-and-what-its-guard-refuses.md

@@ -40,11 +40,13 @@ for a module not yet taken:
 
 - a **directory** present with no record is held: its mode and owner are left, and nothing in it
   is touched;
-- a **service** the machine runs — a unit running or enabled at boot — with no record is held: its
-  state and whether it starts at boot are left. A reload named by the module still happens, since
-  a reload stops nothing ([ADR 0102](0102-the-mesh-writes-into-a-shared-file-never-over-it.md)).
-  A unit file a package merely ships, which nothing runs, is not found: the private network's own
-  tunnel unit is one;
+- a **service** with no record is held when an administrator installed its unit — the service
+  manager reads the unit from outside the packages' own directory — or when the machine uses it,
+  running or started at boot. Its state and whether it starts at boot are then left. A reload
+  named by the module still happens, since a reload stops nothing
+  ([ADR 0102](0102-the-mesh-writes-into-a-shared-file-never-over-it.md)). A unit a package merely
+  ships that nothing runs and nothing enables is not found: the private network's own tunnel unit
+  is one, and holding it kept the private network from ever coming up;
 - an **archive** whose target is present with no record is not unpacked or re-owned; a
   **process** whose unit file is present with no record is not written over or restarted; a
   **user** that exists with no record keeps its shell and groups;