Shivanath Devinarayanan · Updated
On this page
A request walks seven layers. Interaction, agent runtime, orchestration and hooks, tool calls, the governed gateway, memory, then systems of record. Skip the gateway and you have a private pipe. Skip memory and you cannot replay the run. Skip identity and the actor is a shared robot.
This is the signature diagram of the cluster. The gateway band is the stamp: client ID, ABAC, tool mapping, rate limit and mTLS, an LLM lane, and an A2A lane. Agents do not go around it. The visual is stacked dossier bands. The list below is the seven layers a crawler still gets if it never sees the cards.
- Interaction Slack, email, web, and scheduled jobs. The surface the company already uses. Identity starts here, not after the agent replies.
- Agent runtime The Agentforce agent, or a peer worker that is allowed to take the next step. Runtime is not the whole architecture.
- Orchestration and hooks Guided determinism. Known paths stay deterministic. Model judgment where the path is not known. Hooks fire before and after the risky step.
- Tool calls MCP is how agents get tools. Hosts and maps live on the gateway, not as a private pipe from the agent to a system of record.
- Governed gateway The front door: client ID, ABAC, tool mapping, rate limit and mTLS, an LLM lane, and an A2A lane. Agents do not go around it.
- Memory Built-in session memory, temporal memory, peer memory, a context graph, and decision traces. Memory is an asset with an owner.
- Systems of record Salesforce and other policy-gated stores. The agent acts here only with a named identity and a trail that can be replayed.
The seven layers
Also in this file: Home · About · Services · Portfolio · Success Stories · Writing · Events · Contact · Media kit · Privacy Policy