W-23547085 docs: review doc drift for exp-governance- topics (strategies + cost management)

modules/ROOT/pages/exp-governance-create-strategy.adoc

@@ -24,13 +24,15 @@ Also decide whether you need validation-only monitoring or active runtime enforc
 . Log in and go to *Governance* > *Governance Strategies*.
 . Select *Create Governance Strategy* to start the setup flow.
 
-The setup flow guides you through type, scope, rules or policies, and activation.
+The setup flow guides you through these steps: *Strategy Type*, *Scope*, *What to Apply*, *Name & Description*, and *Review*.
+
+For Controls strategies, the flow also includes a *Notifications* step between *What to Apply* and *Name & Description*. This step doesn't appear for Automated Policy strategies.
 
 == Select Strategy Type
 
 Select from these types:
 
-* *Controls* validate targeted services against control rules. Use controls to monitor compliance and, when supported, block noncompliant activity.
+* *Control* validates targeted services against control rules. Use controls to monitor compliance and, when supported, block noncompliant activity.
 * *Automated Policy* enforces runtime policy requirements across targeted services.
 
 Select the type that matches your governance objective, then proceed.
@@ -72,16 +74,18 @@ Depending on the strategy type, select the controls or policies the strategy enf
 
 Available options depend on your earlier selections and your organization's enabled products.
 
-== Name and Describe the Strategy
+== General Information
 
-Enter a clear *Strategy Name*, such as "PCI Compliance Rules". Add a *Description* that states what the strategy enforces and why.
+Enter a clear *Strategy Name*, such as "PCI Compliance Rules." Add a *Description* that states what the strategy enforces and why.
 
 == Review and Activate
 
 Review your selections: strategy type, scope, rules or policies, and general information.
 
 Select *Create and Activate Strategy*.
 
+For Controls strategies, you can also select *Save as Draft* to save the strategy without activating it.
+
 Strategies are active by default. To disable a strategy, go to *Governance Strategies*.
 
 == After Strategy Activation

modules/ROOT/pages/exp-governance-manage-strategies.adoc

@@ -12,15 +12,16 @@ Go to *Governance* > *Governance Strategies* to view all strategies. Check the n
 * View details: Open a strategy to review scope, rules or policies, and metadata.
 * Enable or disable: Pause a strategy without deleting it.
 * Edit configuration: Update scope, rules, name, or description, then save.
-* Reorder strategies: Change strategy order when multiple strategies govern the same services.
+* Reorder strategies: To change the order of Automated Policy strategies, set the type filter to *Automated Policies* and select *Reorder*.
 * Delete a strategy: Permanently remove a strategy that you no longer need.
+* Change to draft: For Control strategies, select *Change to Draft* to move the strategy back to a draft state without deleting it.
 
 == Filter and Search Strategies
 
 Use the controls above the table to narrow the list:
 
 * Use the strategy type filter to select *All*, *Controls*, or *Automated Policies*.
-* Use the status filter to select *Any Status*, *Active*, or *Disabled*.
+* Use the status filter to select *Any Status*, *Active*, *Draft*, or *Disabled*.
 * Enter text in the search field to match strategy names.
 
 The page updates to show only matching strategies.

modules/ROOT/pages/exp-governance-view-cost-and-token-usage.adoc

@@ -36,33 +36,65 @@ include::partial$exp-navigation-labels.adoc[tag=ExpNavigationLabels]
 == Open Cost Management
 
 . Log in and go to *Governance* > *Cost Management*.
-. Adjust the time range and filters for the services or period you want to analyze.
+. Select a tab:
++
+--
+* The *Budgets* tab (default): View total managed spend and budget breakdowns.
+* The *Optimizations* tab: Analyze MCP server token usage and optimization opportunities.
+--
+. Adjust the time range and filters for the data you want to analyze.
 
-== Usage Metrics
+== Budgets Tab
 
-The experience organizes token and activity data into summary cards and detail views:
+The *Budgets* tab shows financial summaries across your configured budgets:
 
-* *Total Tokens*: Number of tokens processed in the selected time range
-* *Saved Tokens (Est.)*: Estimated tokens saved by optimization policies
-* *Tool Calls*: Number of tool or function calls in the selected time range
+* *Total Managed Spend*: Total spend across all configured budgets.
+* *By Provider*: Spend breakdown by LLM provider.
+* *By Model Proxy Key*: Spend breakdown by model proxy client key.
 
-Each card also shows how many instances contributed to the metric.
+=== Add a Budget
 
-== Filter and Search
+. In the *Budgets* tab, select *New Budget*.
+. In the *New Budget* dialog, configure the budget:
++
+--
+* *Model Wallet* (required): Select the model wallet to scope the budget.
+* *Provider* (optional): Select an LLM provider to narrow the budget to a specific provider.
+* *Model* (optional): Select a model. This field appears only after you select a provider.
+* *Period*: Select *Daily*, *Weekly*, or *Monthly*.
+* *Resets on Day of Month*: Select the reset day. This field appears for weekly and monthly periods.
+* *Metric*: Select *Spend* to set a dollar limit, or *Tokens* to set a token count limit.
+* *Spend Limit (USD)* or *Token Limit* (required): Enter the maximum allowed value.
+--
+. Select *Create Budget*.
 
-Use controls at the top of the page to narrow the view:
+When usage reaches the budget limit, the system blocks requests. Each model wallet, provider, and model combination supports only one budget.
 
-* Search for service or instance names.
-* Use *Filters* to refine your search by service type, environment, or metadata.
-* Select a time range to search, such as 1 hour (1H), 6 hours (6H), 24 hours (24H), 7 days (7D), or 30 days (30D).
+For information about model wallets and how they combine authentication credentials with budget limits, see xref:exp-model-wallets-manage.adoc[].
 
-The counter updates to show the number of matching services.
+== Optimizations Tab
+
+The *Optimizations* tab shows cost and token savings data across model proxies, agents, and MCP servers.
+
+The summary cards show:
+
+* *Agents Potential Savings*: Estimated cost savings available by applying optimization policies to agents. It shows *Cost Saved* as the amount already saved.
+* *MCP Servers Potential Savings*: Estimated token savings available by applying optimization policies to MCP servers. It shows *Tokens Saved* as tokens already saved.
+
+Treat these metrics as directional, not exact.
+
+The *Top optimization opportunities* section highlights the instances with the highest potential savings and the specific optimization policy to apply.
+
+== Filter and Search
 
-== Saved Token Estimates
+Use the controls at the top of the *Optimizations* tab to narrow the view:
 
-When optimization policies are active, the system estimates saved tokens compared to unoptimized traffic.
+* Select a sub-tab to filter by instance type: *Model Proxies*, *Agents*, or *MCP Servers*.
+* Search for instance names.
+* Use *Filters* to refine the view by *Environment* or *Provider*.
+* Select a time range: *1H* (1 hour), *24H* (24 hours), *7D* (7 days), or *30D* (30 days). The default is *30D*.
 
-Treat this metric as directional, not exact.
+The counter updates to show the number of matching instances.
 
 == Cost Data Use Cases
 
@@ -72,7 +104,7 @@ Cost and performance data inform multiple workflows:
 * Performance triage: Correlate latency or error spikes with deployments or policy changes.
 * Planning and alignment: Share trends with finance and platform teams for forecasting.
 
-This dashboard doesn't automatically cap usage. To limit consumption, apply governance strategies or rate-limiting policies.
+To automatically cap usage, configure budgets in the *Budgets* tab or through model wallets. Budgets block requests once the limit is reached. To limit consumption in other ways, apply governance strategies or rate-limiting policies.
 
 == Cost Data and Governance
 
@@ -82,6 +114,7 @@ For runtime enforcement, attach cost-related controls or policies to a governanc
 
 == See Also
 
+* xref:exp-model-wallets-manage.adoc[]
 * xref:exp-governance-work-with-strategies.adoc[]
 * xref:exp-governance-create-strategy.adoc[]
 * xref:exp-governance-manage-strategies.adoc[]

modules/ROOT/pages/exp-governance-work-with-strategies.adoc

@@ -1,7 +1,7 @@
 = Working with Governance Strategies
 :keywords: governance strategies, api governance, governance workflows, mulesoft governance, strategy management, anypoint platform
 
-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.
+Use governance strategies to apply conformance rules and policies across agents, APIs, Gateways, 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.
 
 
 == Before You Begin