Unverified50% confidenceFactExact time
In the demo, the .agent.yaml file of the travel planning Broker project defines node structures including system instructions, Broker configuration, Actions, trigger nodes, sub-agents, routing nodes, and the Agent Card.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/27/2026
First Seen
Valid until: 1/25/2027
Sources
MuleSoft Agent Fabric Local Deployment and Testing in Practice
youtubeMule Ace Academy10/27/2026
Related Entities
Related Claims
VerifiedAgent project architecture should separate deterministic processes from parts requiring judgment — workflows handle processes, agents handle judgment.70% similarVerifiedAll Agents are defined under the agents directory and contain a standard structure including name and description, available tools, working specifications, and deliverables, all of which are reusable.70% similarUnverifiedAgentGuard draws on the middleware pattern from web development, abstracting authorization logic as an independent layer inserted between agent decision-making and tool execution.70% similarUnverifiedIf Agent tools take the automated execution route, they need to solve engineering challenges such as permission management, sandbox security, and task interruptibility.70% similarVerifiedThe core design philosophy of Agent Framework is declarative Agent development, simplifying development through pre-built common Agent pattern templates.69% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1103857API
curl https://kongchang.com/api/v1/knowledge/claims/1103857MCP
get_claim(id=1103857)