iterative-retrieval

To validate sub-agent task completion, you can enforce a coordinator-validated exit criteria using a max-3-cycle protocol. This requires coordinator validation before output acceptance to prevent drift.

Spawned sub-agents lose context and blow up cycles due to vague handoffs. Requiring WHY context on every spawn clarifies motivation and goals, ensuring deterministic cycles.

A 3-cycle protocol for sub-agent coordination is a deterministic mechanism that enforces a maximum of three cycles for sub-task completion. It requires a coordinator to validate exit criteria before closing work.

To spawn a sub-agent with WHY context, provide the motivation and goals alongside the scoped task. This enforces a structured handoff and limits iterations to a max-3-cycle protocol for validated outputs.

Yes, you can limit sub-agent iterations to prevent infinite loops by enforcing a max-3-cycle protocol. This deterministic cycle constraint ensures sub-tasks complete within three iterations before coordinator validation.

You need coordinator validation for sub-task completion when agents spawn sub-tasks to complete scoped work. This prevents drift and ensures the coordinator accepts outputs only after validating exit criteria.