diff --git a/03-DESIGN/01-to-be/46-the-conversation-with-the-operator.md b/03-DESIGN/01-to-be/46-the-conversation-with-the-operator.md
index 2ba1cca9..d9b060f1 100644
--- a/03-DESIGN/01-to-be/46-the-conversation-with-the-operator.md
+++ b/03-DESIGN/01-to-be/46-the-conversation-with-the-operator.md
@@ -200,10 +200,12 @@ a summary and a point per key, at most three; an instructions proposal's text an
 Details.
 
 *Amended 2026-10-13, ADR 0347 (issue 383):* **every value an approval sets is in the note.** A settings
-proposal's Details list every key with its value, one line each and uncut — masked under the content rule, and
-whole (`WholeDetails`) where the router shows the whole words — so the operator can always read exactly what
-Approve sets; a point cut for the glance says so. A channel that bounds a message's length cuts the body first
-and keeps the note whole, saying where it cut.
+proposal's Details list every key it sets with its value, one line each and never cut, the value masked where the
+content rule requires. Their whole form (`WholeDetails`) is shown in their place where the router shows the whole
+words, held to the secret rule alone: there the operator reads every value Approve sets, but a value shaped like a
+secret, which is withheld and named by its key. A point cut for the glance says so, and no more than the note
+holds. A channel that bounds a message's length cuts the body first and says where it cut; it cuts the note only
+when the title and the note alone do not fit, and says that too.
 
 ### Life