DENY/delegation-loop
Delegation loop detected
A sub-agent chain would call back into an ancestor — cycle refused.
What it means
The runtime tracks the delegation graph per run. A cycle means the plan cannot terminate; the gate refuses the offending call rather than let the loop close.
Common causes
- Two agents mutually delegating to each other.
- A shared skill that re-enters the caller.
How to fix
- Break the cycle by extracting the shared step into a leaf tool.
- Inspect the delegation graph in `aarmos replay <receipt>`.