Planner-executor
An agent architecture that separates planning from execution: a planner decomposes the goal into steps, and an executor carries each step out.
In more detail
The planner-executor pattern divides an agent's work into two roles. A planner takes the goal and produces an ordered set of steps; an executor then carries out each step, calling tools as needed. Separating the two makes the plan inspectable before any action is taken and keeps the execution focused on one step at a time.
The main advantage over a single monolithic loop is legibility and control. A plan can be reviewed, adjusted, or approved before execution, and a failed step can be retried or replanned without discarding the whole effort. It suits processes where seeing the intended steps up front is valuable.
Where this shows up at Ceven
Ceven turns a plain-language request into a plan of steps and then runs them, which mirrors the planner-executor split. Because the plan takes the shape of a workflow, a person can see what Ceven intends to do, approve the consequential steps, and follow the execution in the audit trail rather than trusting an opaque agent loop.