From 578b90490eaa3535f81a2c822e2db1b396d75534 Mon Sep 17 00:00:00 2001 From: Luana Dos Santos Date: Tue, 7 Jul 2026 12:23:40 -0300 Subject: [PATCH 1/2] docs: doc-drift branch for pr-1331_governance-work-with-strategies From 4c6131fbca08dbdce7811602879ce9d1e5faac66 Mon Sep 17 00:00:00 2001 From: Luana Dos Santos Date: Tue, 7 Jul 2026 12:27:51 -0300 Subject: [PATCH 2/2] W-23349167 docs: clarify controls vs strategies terminology Add a note explaining that the UI uses "controls" for guardrail-based strategies and "automated policies" for the other type, while the docs use "strategy" as the umbrella term for both. --- modules/ROOT/pages/exp-governance-work-with-strategies.adoc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/modules/ROOT/pages/exp-governance-work-with-strategies.adoc b/modules/ROOT/pages/exp-governance-work-with-strategies.adoc index 382d8d1a0..331db9d76 100644 --- a/modules/ROOT/pages/exp-governance-work-with-strategies.adoc +++ b/modules/ROOT/pages/exp-governance-work-with-strategies.adoc @@ -3,6 +3,8 @@ Use governance strategies to apply conformance rules and policies across agents, APIs and MCP servers. When your tenant includes *Governance* and your account has the required role, you can create, manage, and monitor these strategies to validate service design compliance, automate runtime enforcement, and maintain visibility as your portfolio grows. +NOTE: The MuleSoft interface uses two terms for strategy types: *controls* (for guardrail-based strategies) and *automated policies*. In this documentation, "strategy" refers to both types unless otherwise specified. + == Before You Begin