diff --git a/project-knowledge/03-context/process/communication-rules.md b/project-knowledge/03-context/process/communication-rules.md
index 179c6ea..b13abb7 100644
--- a/project-knowledge/03-context/process/communication-rules.md
+++ b/project-knowledge/03-context/process/communication-rules.md
@@ -26,6 +26,7 @@ These rules keep standups, Jira notes, and Mattermost messages aligned with the
 - Include branch, build, environment, account, flow, or entry-point details when they materially affect reproduction or ownership
 - When reporting several updates for the same Jira item, group them under one top-level `JIRA-ID - Title` bullet with indented markdown sub-bullets
 - Use real flow identifiers and page names when shorthand could be ambiguous
+- Prefer `toggle` over `flag` in Fidelity-facing communication, unless naming a specific external tool concept such as LaunchDarkly feature flags
 - Route ownership explicitly when the issue belongs to a consumer app, service/configuration, or another framework instead of XFlow
 - Do not present a fix as ready if it introduces a new bug or unresolved regression
 - Administrative/project-tracking updates should be prompt when others are visibly waiting on them