Shivanath Devinarayanan · Updated
On this page
The runtime plane is where agents actually loop. An intent broker routes known jobs on a deterministic path and asks a model only when the path is ambiguous. Custom code agents, headless workers, and Salesforce Agentforce talk to each other as peers over an agent-to-agent (A2A) envelope. Tools are not credentials in a prompt. They are remote MCP servers grouped by job: research, fetch, graph, infra.
Claude Agent SDK, OpenAI SDK, LangGraph, and Agentforce ADKs are public scaffolds. New agents inherit telemetry, on-behalf-of checks, and error handling from the template. They do not start as a one-off notebook. Salesforce wrapping is on Agentforce as a peer . Tool hosting is on governed MCP tools .
Why it matters
If every new worker is bespoke, the bottleneck is a person, not a model. A broker with a skill registry makes the next agent a row: name, runtime, identity, allowed actions, owner, trail. Circuit breaking sends a degraded node to a fallback queue or a human, not into a silent retry storm.
A2A needs hop budgets and request traces. Without them, two agents delegate in a circle until the bill arrives. Identity travels with the task. Agent B does not become a superuser because Agent A called it.
In a generic org
Pipeline risk is a known job. The broker sends it to a research agent without a frontier model. A messy inbound email is not a known job. The broker asks a model, then hands a CRM agent an A2A task. The CRM agent is Agentforce. The research agent is a LangGraph worker. They share a gateway, not a shared password.
A2A
Peer delegation is a JSON-RPC envelope with a task id, a context id, and a hop count. Conversational memory only when identity is stable. A wrapper should not claim streaming, push, or history it does not implement. Identity still applies when Agentforce is the peer.
MCP categories
Tools group by job: research, fetch, graph, infra. Credentials stay on the tool host. Each category still sits behind the gateway: client id, access control, tool mapping, spike control, logging.
- Research Long-running lookup and synthesis. Poll, do not block the human surface.
- Fetch Authenticated page and API fetch. Credentials stay on the tool host, not in the prompt.
- Graph Knowledge-graph read and write through a scoped tool, not a raw database string in context.
- Infra Diagnostics and provisioning behind the same gateway and identity as every other tool.
Stack
Home · About · Services · Portfolio · Success Stories · Writing · News · Events · Contact · Media kit · Privacy Policy