Declarative vs Imperative Agents
An imperative agent is told the steps: call this, then that, in this order. A declarative agent is told the goal and the constraints, and chooses the steps. Imperative is predictable and brittle — it breaks when a dependency changes. Declarative is adaptable and harder to audit — it can reach a goal by a path nobody anticipated. Production agents blend them: declarative intent at the top, imperative guardrails underneath.
The tradeoff
Latitude buys adaptability and costs auditability. An imperative agent does exactly what you wrote and nothing else; a declarative one solves problems you did not foresee and occasionally solves them in ways you would not have allowed. The engineering question is never "which" but "how much latitude, bounded by what policy, recorded how".
Questions
Which should I build?
Start imperative for critical paths where the steps are known, declarative where the space of situations is too large to script. Most real systems need both.
Does declarative mean no control?
No. Control moves from the steps to the constraints — the policy plane and the intent’s bounds — rather than disappearing.
Where this lives in the estate
FlashyID — bounded authority is what makes declarative latitude safe
Keep reading
By Michael Gord · published 2026-10-04 · part of the Agentic Encyclopedia. Dates are the day of publication; events are cited at their own dates.