diff --git a/02-DECISIONS/0272-the-operator-reaches-the-controller-with-mesh-cli-on-every-node-and-a-node-is-the-terminal-only-where-no-agent-runs-as-its-operator.md b/02-DECISIONS/0272-the-operator-reaches-the-controller-with-mesh-cli-on-every-node-and-a-node-is-the-terminal-only-where-no-agent-runs-as-its-operator.md
index f6e0b67d..65089322 100644
--- a/02-DECISIONS/0272-the-operator-reaches-the-controller-with-mesh-cli-on-every-node-and-a-node-is-the-terminal-only-where-no-agent-runs-as-its-operator.md
+++ b/02-DECISIONS/0272-the-operator-reaches-the-controller-with-mesh-cli-on-every-node-and-a-node-is-the-terminal-only-where-no-agent-runs-as-its-operator.md
@@ -170,6 +170,8 @@ The answer is the command's standard output, its standard error, its exit status
 and why or why not. `mesh-cli` prints the two streams and exits with the status. An answer larger than one bus
 message is cut there and the cut is said; it is never silently short. Standard input is not carried: a command
 that reads it gets nothing and fails saying so. Streaming the output and carrying the input are later steps.
+A path in a line names a file where the controller runs, read by the controller's account, never a file beside
+`mesh-cli`: settings are given inline, `"$(cat settings.json)"` in the operator's own shell.
 
 ### 6. What is shared, and where it lives