You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
entry.sh stops the judge swarm after three cycles despite the documented convergence behavior #297
The README says that judges run in cycles until no new facts are produced, but entry.sh:32 hard-codes --max-cycles=3. A swarm whose rules need a fourth cycle silently stops with an incomplete factbase, even though the documented execution model promises convergence.
A chain such as A -> B -> C -> D needs four update cycles: the first creates B, the second C, the third D, and the fourth confirms that no new facts remain. The current entry point exits after the third cycle and leaves D missing.
Either let judges update run to its normal fixed point or expose/validate a cycle limit and document the bounded behavior. Add a fixture with a dependency chain longer than three cycles so the entry point cannot report success with incomplete output.
Activity