Overview
A goal-driven loop contains two primary roles:
- An acting agent performs the work.
- A judging process reviews the work against the goal criteria.
If the criteria have not been met, the work returns to the agent for another pass. The loop continues until the system judges that the goal is complete or the operator stops it.
This changes the interaction model. In ordinary chat, the user repeatedly asks for another step. In a goal loop, the system carries the task forward without requiring a new prompt at each stage.
The quality of the loop depends on the quality of the goal. A useful goal states not only the subject but also the required output and the conditions that must be true. For a keyword research application, the goal included several constraints: the keywords should be real, the tool should adapt to the user's niche, the system should understand the supplied context, and the output should be a usable application rather than a code-only artifact.
A second loop type is a schedule loop. A goal loop continues until completion. A schedule loop runs again at a defined time or interval. The two can be combined: each scheduled execution can itself be a goal-directed job.