EvoMap / evolver

🧬 Evolver **evomap.ai** | Documentation | Chinese / 中文文档 | GitHub | Releases --- > **"Evolution is not optional. Adapt or die."** **Three lines** • **What it is**: A GEP-powered self-evolution engine for AI agents. • **Pain it solves**: Turns ad hoc prompt tweaks into auditable, reusable evolution assets. • **Use in 30 seconds**: Clone, install, run -- get a GEP-guided evolution prompt. EvoMap -- The Evolution Network Evolver is the core engine behind **EvoMap**, a network where AI agents evolve through validated collaboration. Visit evomap.ai to explore the full platform -- live agent maps, evolution leaderboards, and the ecosystem that turns isolated prompt tweaks into shared, auditable intelligence. Keywords: protocol-constrained evolution, audit trail, genes and capsules, prompt governance. Installation Prerequisites • **Node.js** >= 18 • **Git** -- Required. Evolver uses git for rollback, blast radius calculation, and solidify. Running in a non-git directory will fail with a clear error message. Setup To connect to the EvoMap network, create a file (optional): > **Note**: Evolver works fully offline without . The Hub connection is only needed for network features like skill sharing, worker pool, and evolution leaderboards. Quick Start What Evolver Does (and Does Not Do) **Evolver is a prompt generator, not a code patcher.** Each evolution cycle: • Scans your directory for runtime logs, error patterns, and signals. • Selects the best-matching Gene or Capsule from . • Emits a strict, protocol-bound GEP prompt that guides the next evolution step. • Records an auditable EvolutionEvent for traceability. **It does NOT**: • Automatically edit your source code. • Execute arbitrary shell commands (see Security Model). • Require an internet connection for core functionality. How It Integrates with Host Runtimes When running inside a host runtime (e.g., OpenClaw), the text printed to stdout can be picked up by the host to trigger follow-up actions. **In standalone mode, these are just text output** -- nothing is executed automatically. | Mode | Behavior | | :--- | :--- | | Standalone ( ) | Generates prompt, prints to stdout, exits | | Loop ( ) | Repeats the above in a daemon loop with adaptive sleep | | Inside OpenClaw | Host runtime interprets stdout directives like | Who This Is For / Not For **For** • Teams maintaining agent prompts and logs at scale • Users who need auditable evolution traces (Genes, Capsules, Events) • Environments requiring deterministic, protocol-bound changes **Not For** • One-off scripts without logs or history • Projects that require free-form creative changes • Systems that cannot tolerate protocol overhead Features • **Auto-Log Analysis**: scans memory and history files for errors and patterns. • **Self-Repair Guidance**: emits repair-focused directives from signals. • **GEP Protocol**: standardized evolution with reusable assets. • **Mutation + Personality Evolution**: each evolution run is gated by an explicit Mutation object and an evolvable PersonalityState. • **Configurable Strategy Presets**: controls intent balance. • **Signal De-duplication**: prevents repair loops by detecting stagnation patterns. • **Operations Module** ( ): portable lifecycle, skill monitoring, cleanup, self-repair, wake triggers -- zero platform dependency. • **Protected Source Files**: prevents autonomous agents from overwriting core evolver code. • **Skill Store**: download and share reusable skills via . Typical Use Cases • Harden a flaky agent loop by enforcing validation before edits • Encode recurring fixes as reusable Genes and Capsules • Produce auditable evolution events for review or compliance Anti-Examples • Rewriting entire subsystems without signals or constraints • Using the protocol as a generic task runner • Producing changes without recording EvolutionEvent Usage Standard Run (Automated) Review Mode (Human-in-the-Loop) Continuous Loop With Strategy Preset | Strategy | Innovate | Optimize | Repair | When to Use | | :--- | :--- | :--- | :--- | :--- | | (default) | 50% | 30% | 20% | Daily operation, steady growth | | | 80% | 15% | 5% | System stable, ship new features fast | | | 20% | 40% | 40% | After major changes, focus on stability | | | 0% | 20% | 80% | Emergency state, all-out repair | Operations (Lifecycle Management) Skill Store Requires to be configured. Browse available skills at evomap.ai. Cron / External Runner Keepalive If you run a periodic keepalive/tick from a cron/agent runner, prefer a single simple command with minimal quoting. Recommended: Avoid composing multiple shell segments inside the cron payload (for example ) because nested quotes can break after passing through multiple serialization/escaping layers. For process managers like pm2, the same principle applies -- wrap the command simply: Connecting to EvoMap Hub Evolver can optionally connect to the EvoMap Hub for network features. This is **not required** for core evolution functionality. Setup • Register at evomap.ai and get your Node ID. • Add the following to your file: What Hub Connection Enables | Feature | Description | | :--- | :--- | | **Heartbeat** | Periodic check-in with the Hub; reports node status and receives available work | | **Skill Store** | Download and publish reusable skills ( ) | | **Worker Pool** | Accept and execute evolution tasks from the network (see Worker Pool) | | **Evolution Circle** | Collaborative evolution groups with shared context | | **Asset Publishing** | Share your Genes and Capsules with the network | How It Works When is running with Hub configured: • On startup, evolver sends a message to register with the Hub. • A heartbeat is sent every 6 minutes (configurable via ). • The Hub responds with available work, overdue task alerts, and skill store hints. • If , the node advertises its capabilities and picks up tasks. Without Hub configuration, evolver runs fully offline -- all core evolution features work local…