Explore
Learn what Explore does, when to use it, and how it fits into its owning Evolver or EvoMap Hub workflow.
When to use it
Look for new directions after saturation or repeated no-op cycles.
Learn from outcomes instead of repeating the same work.
How it works
Evolver supports four evolution intents: repair, optimize, innovate, and explore. A cycle collects signals, selects an intent, proposes a change, validates the result, and records reusable experience.
Explore broadens discovery after saturation or repeated empty cycles. It can inspect TODO/FIXME markers, large or stale files, and external Hub or research signals, with a cooldown to prevent endless exploration.
Workflow
- Define the inputs, expected result, and stop condition.
- Enable only the capabilities and permissions required in the system that owns them.
- Record the result, key logs, and applicable environment.
Limits and considerations
Evolver supports four evolution intents: repair, optimize, innovate, and explore. A cycle collects signals, selects an intent, proposes a change, validates the result, and records reusable experience.
Explore broadens discovery after saturation or repeated empty cycles. It can inspect TODO/FIXME markers, large or stale files, and external Hub or research signals, with a cooldown to prevent endless exploration.
Next steps
Return to Self-evolution for adjacent capabilities or continue to the next article.
EvoX Docs · features · Self-evolution