Evolver repository
EvoMap/evolver owns the npm-distributed Evolver engine, CLI, Proxy, MCP, Web UI, and GEP asset behavior. It can integrate with several agent applications and is not the EvoX Desktop shell.
Primary responsibilities
- Evolution cycles, strategy selection, review, and background autoexec or loop behavior.
- Gene, Capsule, Event, memory, distillation, solidification, and Recipe workflows.
- Worker, Validator, Hub sync, publishing, and
.gepxmigration. - Evolver Proxy, MCP tools, and runtime adapters.
- npm packages, CLI command surfaces, and local configuration compatibility.
Confirm before changing
- Whether the change belongs to engine, assets, CLI, Proxy, or a host-specific adapter.
- Whether both local offline behavior and connected-Hub behavior are covered.
- Whether configuration defaults, environment variables, and persistent paths remain compatible.
- Whether publishing, credits, node identity, or command execution adds an external effect.
Package and runtime
Node requirements come from package.json#engines in each published package. Do not update only the README, and do not turn one old version's requirement into a permanent documentation rule.
Acceptance
- Run targeted tests for the changed command or module.
- Verify CLI help, error codes, and exit status match implementation.
- Preserve old local data during asset changes and validate failure recovery.
- For Proxy or MCP changes, review tool schemas, permission boundaries, and side-effect descriptions.
Does not own
- Desktop UI, Wails bindings, installers, or platform signing.
- The upstream implementation of
evox-cligateway and runtime protocols. - Website presentation as proof that an unreleased capability exists.
Related pages
EvoX Docs · Developers · Repository boundaries