Glossary
Every term, one line each.
Every term, one line each. For the fuller picture, see Concepts.
- A2A (Agent-to-Agent)
- The JSON-RPC 2.0 protocol brokers speak. Versions 0.3 (default) and 1.0differ in method name, message shape, and header.
- Action
- A callable capability in AgentScript (
@actions.x) — an MCP tool or an A2A send — that a node is allowed to run. Auto-created when you compose an MCP server or agent. - Agent card
- The A2A discovery document describing a broker and its skills; the public contract. Usually served at
/.well-known/agent-card.json. - Agent Network
- The published unit — one Exchange asset bundling
agent-network.yaml,exchange.json, and one broker's.agentfile. Contains exactly one broker. - AgentScript
- MuleSoft's AgentFabric dialect for a broker's node graph, stored in a
.agentfile. Builder generates it from the canvas. - Anypoint CLI v4
- The command-line tool (
anypoint-cli-v4) plus the agent-fabric plugin that Build & Publish shells out to for build/publish/deploy. - Artifact
- A named output a task produces, surfaced in Tracer's Task story.
- Broker
- The deployed, LLM-driven agent runtime that receives A2A requests and runs its graph. A network's only front door.
- Business group
- The Anypoint org scope selected in the left sidebar; governs which assets, environments, and gateways you see. Passed to the CLI as
--organization. - Connection
- A
context.connectionsentry in the YAML that a composed Exchange asset becomes; targeted by actions and LLM bindings. - Context / contextId
- The id grouping multiple tasks into one conversation.
- Echo
- The graph node kind that sends a response to the client. Terminal on a Completed/Failed/Canceled/Rejected status; otherwise must transition onward.
- Enhanced Log Search
- The Anypoint entitlement (Advanced package / Titanium) that unlocks full-fidelity tracing. Without it, Tracer falls back to runtime logs.
- Exchange asset / GAV
- A reusable published artifact identified by
groupId : assetId : version. LLMs, MCP servers, agents, policies, and networks are all Exchange assets. - Executor
- A deterministic node kind — sets variables and runs actions, no LLM. Forbids slot-filling.
- Gateway
- A Flex Gateway used as a deployment target. For shared-space deploys you pick one gateway; the CLI derives the space.
- Generator
- A node kind: a single LLM call to produce text — no tools, no loop.
- LLM binding
- An LLM asset wired into AgentScript (
@llm.x) that reasoning nodes use. On Tracer's graph, LLM nodes are design-time only. - MCP (Model Context Protocol)
- The standard for agents calling external tools. An MCP server exposes named tools; a broker calls them as actions.
- Object Store
- Where brokers persist task state and reasoning — the source of Tracer's Task story. Keys expire (24h default TTL, 30d max).
- Orchestrator
- A subagent node specialized for coordinating multiple agents and MCP tools toward a goal.
- Private space
- A CloudHub 2.0 private space / Runtime Fabric deploy target; needs a space plus ingress and egress gateways.
- Router
- A deterministic branching node — routes on conditions, no LLM. Needs routes plus an
otherwisetarget. - Skill
- A capability a broker advertises on its agent card; Tracer's Invoke rail offers skills as one-click starters.
- Structured outputs
- Declared
outputson a reasoning node, letting a router branch on@node.output.fieldinstead of parsing prose. - Subagent
- A node kind: a generic agent loop with a prompt and a set of actions.
- Task
- One A2A request/turn — the unit Tracer traces. Carries iterations, artifacts, and a terminal status.
- Task story
- Tracer's structured v2 view of a task — conversation history, artifacts, and state — decoded from Object Store.
- Teardown
- Undeploy (stop the running network) and unpublish (erase the Exchange version). Undeploy first.
- Trigger
- The single graph entry point that starts the flow when a message arrives. Can't be deleted; nothing transitions into it.
- v1 vs v2 broker
- v1 = ReAct-style reasoning loop (Tree/List views); v2 = node-graph AgentScript runtime (timeline, Task story, graph overlay). Builder authors v2.
- Variables / properties
exchange.jsondeploy variables referenced as${group.field}, passed to the CLI as--property name:value. Secrets re-entered each session.
