diff --git a/04-ISSUES/169-a-machine-shares-its-files-and-the-mesh-does-not-know/00-report.md b/04-ISSUES/169-a-machine-shares-its-files-and-the-mesh-does-not-know/00-report.md
index 1b44232..addacf0 100644
--- a/04-ISSUES/169-a-machine-shares-its-files-and-the-mesh-does-not-know/00-report.md
+++ b/04-ISSUES/169-a-machine-shares-its-files-and-the-mesh-does-not-know/00-report.md
@@ -88,7 +88,11 @@ A binding tells a consumer *where* the share is; it does not put the files on it
 is something done on a machine, and something done on a machine is a module's work — not the host's
 (the vocabulary stays closed; no `mount` resource kind).
 
-**A consumer-side module, `network-share`,** assigned on the node that wants the files:
+**A consumer-side module, `network-share` — the module responsible for setting up the network
+shares a node uses** (the operator's framing). A node role, like `node-uplink` or
+`node-dns-resolver`: each machine has it at most once, which is a reason for it to hold a
+node-scoped seat, so two modules can never both be writing mount units on one machine. Assigned on
+the node that wants the files:
 
 - `requires nfs-share` (or `smb-share`); several shares on one node are several local names of
   the requirement (ADR 0094);