W-22511751 add shared spaces support to agent network docs

modules/ROOT/pages/_partials/af-shared.adoc

@@ -84,12 +84,12 @@ If you're using the Anypoint CLI to create agent network projects, ensure you me
 [[step-1-setup]]
 === Step 1: Set Up Your Agent Network
 
-. Use Anypoint Runtime Manager to set up a private space in CloudHub 2.0 or deployment target in Runtime Fabric.
+. Use Anypoint Runtime Manager to set up a space in CloudHub 2.0 or deployment target in Runtime Fabric.
 +
-See xref:anypoint-code-builder::af-get-started.adoc#setup-space[Set Up the Private Space or Deployment Target for Your Environment].
-. Set up Ingress and egress Omni Gateways for the private space or deployment target.
+See xref:anypoint-code-builder::af-get-started.adoc#setup-space[Set Up the Space or Deployment Target for Your Environment].
+. Set up Omni Gateways for the space or deployment target.
 +
-  * If using Anypoint Code Builder, see xref:anypoint-code-builder::af-get-started.adoc#setup-gateways[Set Up Agent Network Gateways for the Private Space or Deployment Target].
+  * If using Anypoint Code Builder, see xref:anypoint-code-builder::af-get-started.adoc#setup-gateways[Set Up Agent Network Gateways for the Space or Deployment Target].
   * If using the Anypoint CLI, see the xref:anypoint-code-builder::af-build-agent-networks-in-a-ci-cd-environment.adoc#agent-network-setup-gateways[setup gateways command reference].
 
 [[step-2-create]]
@@ -121,7 +121,7 @@ Build and publish your agent network project as Anypoint Exchange assets. When y
 [[step-5-deploy]]
 === Step 5: Deploy Your Agent Network Instances
 
-Deploy your agent network instance to a deployment target. You can deploy to a CloudHub 2.0 private space or to a Runtime Fabric.
+Deploy your agent network instance to a deployment target. You can deploy to a CloudHub 2.0 shared space, a CloudHub 2.0 private space, or to a Runtime Fabric.
 
 * xref:anypoint-code-builder::af-deploy-agent-network-targets.adoc#deploy-dev-agent[Deploy Your Network Using MuleSoft Vibes]
 * xref:anypoint-code-builder::af-deploy-agent-network-targets.adoc#deploy-acb[Deploy Your Network Using Anypoint Code Builder]

modules/ROOT/pages/af-agent-networks.adoc

@@ -122,7 +122,7 @@ image::agent-fabric-architecture.png[Agent Fabric showing agents and MCP servers
 . Publish the agentic assets to Anypoint Exchange for discovery and reuse after you define the agent network (brokers, agents, MCP servers) in the agent network YAML in Anypoint Code Builder.
 . Deploy the agentic assets to CloudHub 2.0 (managed in Runtime Manager).
 . Enforce policies on incoming traffic to the network with an ingress Omni Gateway, which sits in front of brokers and API endpoints.
-. Enforce policies, manage connections, and emit telemetry data with an egress Omni Gateway, which sits on outbound paths from brokers and agents to external agents and services.
+. Enforce policies, manage connections, and emit telemetry data with an egress Omni Gateway, which sits on outbound paths from brokers and agents to external agents and services. In a shared space, or in a private space using a single-gateway configuration, callouts policies, traffic, and data are handled by one Omni Gateway.
 . Collect logs, metrics, and traces from Omni Gateway and runtimes in Anypoint Monitoring.
 
 [[llm-support]]

modules/ROOT/pages/af-build-agent-networks-in-a-ci-cd-environment.adoc

@@ -41,9 +41,9 @@ For more information, see xref:anypoint-cli::auth.adoc[].
 
 === Create a Target Space for Your Environment
 
-To deploy an agent network, you need a private space on CloudHub 2.0 or a deployment target on Anypoint Runtime Fabric. See xref:af-get-started.adoc#setup-space[Set Up the Private Space or Deployment Target for Your Environment].
+To deploy an agent network, you need a space on CloudHub 2.0 or a deployment target on Anypoint Runtime Fabric. See xref:af-get-started.adoc#setup-space[Set Up the Space or Deployment Target for Your Environment].
 
-After you create a target space, set up the ingress and egress gateways for deployment if you haven't already done so. See xref:af-get-started.adoc#setup-gateways[Set Up Agent Network Gateways for the Private Space or Deployment Target].
+After you have a target space, set up the gateway or gateways for deployment if you haven't already done so. See xref:af-get-started.adoc#setup-gateways[Set Up Agent Network Gateways for the Space or Deployment Target].
 
 == CLI for Agent Fabric Plugin Reference
 

modules/ROOT/pages/af-deploy-agent-network-targets.adoc

@@ -1,7 +1,7 @@
 [[deploy-instances]]
 = Deploy Agent Network Instances
 
-Deploy your agent network instance to a deployment target. You can deploy to a CloudHub 2.0 private space or to a Runtime Fabric. When you deploy, Omni Gateway secures your agent network in the ingress gateway. Also, it secures your brokers, agents, and MCP servers in the egress gateway.
+Deploy your agent network instance to a deployment target. You can deploy to a CloudHub 2.0 shared space, a CloudHub 2.0 private space, or to a Runtime Fabric. When you deploy, Omni Gateway secures inbound traffic to your agent network and outbound traffic from your brokers, agents, and MCP servers.
 
 These Omni Gateway policies are applied automatically at deployment.
 

modules/ROOT/pages/af-get-started.adoc

@@ -4,15 +4,18 @@
 include::anypoint-code-builder::partial$af-shared.adoc[tags=get-started]
 
 [[setup-space]]
-== Set Up the Private Space or Deployment Target for Your Environment
+== Set Up the Space or Deployment Target for Your Environment
 
-To deploy an agent network, you need a private space on CloudHub 2.0 or a deployment target on Anypoint Runtime Fabric.
+To deploy an agent network, you need a space on CloudHub 2.0 or a deployment target on Anypoint Runtime Fabric. On CloudHub 2.0, you can deploy to a shared space or a private space.
 
-If you already have a private space configured in CloudHub 2.0, you can associate it with the business groups and environments where you'll deploy your agent network.
+Use a shared space if you don't require dedicated infrastructure. Use a private space if you need workload isolation or have other requirements that a shared space doesn't satisfy.
 
 Depending on your deployment target:
 
-* CloudHub 2.0:
+* CloudHub 2.0 shared space:
++
+No setup is required. Every Anypoint Platform organization includes a shared space that's available to all business groups and environments.
+* CloudHub 2.0 private space:
 +
 . Create a private space in CloudHub 2.0 or verify that you can access an existing private space.
 +
@@ -28,27 +31,33 @@ Create a target space for Runtime Fabric.
 For information about Runtime Fabric deployments, see xref:gateway::flex-gateway-managed-set-up.adoc#rtf[Managed Omni Gateway on Runtime Fabric].
 
 [[setup-gateways]]
-== Set Up Agent Network Gateways for the Private Space or Deployment Target
+== Set Up Agent Network Gateways for the Space or Deployment Target
+
+After you have a target space, use the `MuleSoft: Set Up Agent Network Gateways` command to create the gateways required for deployment in either CloudHub 2.0 or Runtime Fabric.
 
-After you have a target space, use the `MuleSoft: Set Up Agent Network Gateways` command to create the ingress and egress gateways required for deployment in either CloudHub 2.0 or Runtime Fabric.
+For agent networks, you need at least one Managed Omni Gateway in your environment. A single gateway can handle both ingress and egress traffic, which is the recommended configuration. You can also use separate gateways for ingress and egress traffic in a private space.
 
-For agent networks, you must have at least one small Managed Omni Gateway and one large Managed Omni Gateway in your environment.
 For more information about gateways, see xref:gateway::flex-architecture-basic-deployments.adoc[].
 
 For more information about Runtime Fabric deployments, see xref:gateway::flex-gateway-managed-set-up.adoc#rtf[Managed Omni Gateway on Runtime Fabric].
 
 . In Anypoint Code Builder, from the Command Palette, run the command *MuleSoft: Set Up Agent Network Gateways*.
-+
-If you didn't associate the private space with the business group and environment, you see an error.
 . If you're not logged in, log in to your Anypoint Platform account.
-. Select the business group, environment, and private or target space.
+. Select the business group and environment.
+. Select the deployment target:
 +
-The `MuleSoft: Set Up Agent Network Gateways` command creates these gateways in the private or target space you select:
+* *Shared Space*: The command creates one gateway named `agent-network-shared-gw` that handles both ingress and egress traffic.
+* *Private Space*: Select the target space, then choose a gateway configuration:
 +
-* agent-network-ingress-gw (with public and internal endpoint)
-* agent-network-egress-gw (with internal endpoint only)
+** *Single Gateway* (recommended): The command creates one gateway named `agent-network-gw` that handles both ingress and egress traffic.
+** *Separate Ingress & Egress*: The command creates two gateways:
++
+*** `agent-network-ingress-gw` (with public and internal endpoint)
+*** `agent-network-egress-gw` (with internal endpoint only)
++
+If you didn't associate the private space with the business group and environment, you see an error.
 
-If the gateways already exist in the selected private or target space, the command doesn’t recreate them.
+If a gateway with the expected name already exists in the selected space, the command doesn't recreate it.
 
 [[see-also]]
 == See Also