The New AI Agent Primitive: Why Policy Needs Its Own Language (And Why YAML and Rego Fall Short)

AI agents are no longer experiments. They’re writing code, moving money, and operating infrastructure. But as they gain autonomy, one question keeps coming up: how do you safely control what they can do? Most teams start with system prompts and YAML configs. Some move to generic policy engines like OPA/Rego or Cedar. But neither approach was designed for agents. YAML lacks native concepts like budgets, phases, and delegation. Rego is powerful but generic and it treats “deny” as a runtime afterthought. Thanks for reading Amjad! Subscribe for free to receive new posts and support my work. That’s why we built FPL (Faramesh Policy Language), a domain‑specific language purpose‑built for AI agent governance. It’s not a repurposed config format. It’s a new primitive for the agentic stack. Let’s compare how the three approaches handle real‑world agent policies. The Problem: YAML Is a Convention, Not a Contract A typical agent policy in YAML with expression evaluation looks like this (abbreviat