Do all seven layers have to be MuleSoft?

No. The gateway and the pipes do. Memory can be a graph you already run. The runtime can be Agentforce, or not. We will not force a store into Anypoint to look complete.

What if the broker flags a memory fetch as an attack?

Tighten the cards and the policy. Memory is not prompt injection. If the platform cannot tell, that is a finding, not a reason to turn the gateway off.

MuleSoft

Seven layers. One governed path.

The first week is in the org, reading what already exists. Slack, a browser, or a schedule can start the work. The gateway is the front door for every tool call and model call. The honest no: if the work is a software factory with a named delivery date, we are the wrong partner.

Send the brief

Architecture

How a request should travel.

The gold layer is the gateway. It is not optional.

01
Interaction
Slack · Email · Web · Scheduled
02
Agent runtime
Agentforce · Other runtimes on the same desk
03
Orchestration
Broker · Hooks · Deterministic routers
04
Tool calls
MCP servers · Knowledge · Search · Internal APIs
05
MuleSoft gateway
Client identity · Access control · MCP mapping · Rate limits · LLM proxy · A2A lane
06
Memory
Session · Graph · Decision traces
07
Systems of record
Salesforce · ERP · Policy-gated stores

Public reference architecture for digital labor on MuleSoft. Interaction to runtime to orchestration to MCP to gateway to memory to systems of record. The gateway is the control point.

Mermaid source

flowchart TD
  L1["1 Interaction: Slack, email, web, scheduled"] --> L2["2 Agent runtime: Agentforce and other runtimes"]
  L2 --> L3["3 Orchestration: broker, hooks, routers"]
  L3 --> L4["4 Tool calls: MCP servers"]
  L4 --> L5["5 MuleSoft gateway: identity, policy, LLM proxy, A2A"]
  L5 --> L6["6 Memory: session, graph, traces"]
  L6 --> L7["7 Systems of record: Salesforce, ERP, files"]

What to demand

What must already work before you scale.

If these are missing, you do not have a fabric. You have a demo.

How far

Govern the edge first. Front stores only when proven.

Moving a graph or a warehouse behind a new owner is a one-way door. Front first.

Questions

What we actually say.

Do all seven layers have to be MuleSoft?: No. The gateway and the pipes do. Memory can be a graph you already run. The runtime can be Agentforce, or not. We will not force a store into Anypoint to look complete.
What if the broker flags a memory fetch as an attack?: Tighten the cards and the policy. Memory is not prompt injection. If the platform cannot tell, that is a finding, not a reason to turn the gateway off.

Doors that belong next.

The brief

Draw the path you have today.

We will mark which hops have no gateway, and which should.

Seven layers. One governed path.

flowchart TD L1["1 Interaction: Slack, email, web, scheduled"] --> L2["2 Agent runtime: Agentforce and other runtimes"] L2 --> L3["3 Orchestration: broker, hooks, routers"] L3 --> L4["4 Tool calls: MCP servers"] L4 --> L5["5 MuleSoft gateway: identity, policy, LLM proxy, A2A"] L5 --> L6["6 Memory: session, graph, traces"] L6 --> L7["7 Systems of record: Salesforce, ERP, files"]