Evolution behavior
Evolution behavior controls what kind of work Evolver prefers, when it continues, when it broadens exploration, and how much one cycle may change. Strategy, loop behavior, and hard boundaries should be configured together.
Three layers
| Layer | Question | Main configuration |
|---|---|---|
| Strategy | Should the cycle favor features, optimization, or repair? | EVOLVE_STRATEGY |
| Loop and explore | Should it keep running, and what happens when idle or saturated? | EVOLVE_LOOP, EVOLVE_MIN_INTERVAL, EVOLVER_EXPLORE_* |
| Change boundaries | How much may one cycle touch, and how does failure recover? | EVOLVER_HARD_CAP_*, EVOLVER_ROLLBACK_MODE |
Recommended order
- Choose a strategy that matches the current stage; keep
balancedwhen uncertain. - Validate the strategy, workspace, and test commands with review mode or one cycle.
- Set file, line, path, and rollback boundaries.
- Enable a loop only after observing a success, a no-change result, and a failure path.
- Decide separately whether Explore may reach the Hub or external research sources.
Strategy is not permission
innovate, harden, and repair-only change intent weighting. They do not expand filesystem access, skip tests, authorize publication, or override workspace controls. Commit, pull request, publication, and production actions remain governed by their own settings and approvals.
EvoX Desktop long-running goals, scheduled tasks, and Code sessions are also not synonyms for an Evolver loop. Use their product workflows separately; these variables apply to standalone Evolver and the managed Evolver child inside Desktop.
EvoX Docs · Configuration · Evolution behavior