Glossary
This page separates the EvoX product, local runtimes, Evolver, evolution-protocol assets, and EvoMap network services. Definitions were verified against the current project sources and @evomap/[email protected] on September 21, 2026.
Products and runtimes
| Name | Meaning |
|---|---|
| EvoX Desktop | The user-facing desktop product for projects and chats, cowork, coding, sites, scheduled tasks, browser work, plugins, and files |
EvoX Core / evox-cli | EvoX gateway, CLI, runtime, and protocol implementation; Desktop manages its own local sidecar |
| Evolver | The separately distributed self-evolution engine with CLI, Proxy, MCP, and GEP workflows, installable as @evomap/evolver |
| EvoMap Hub | The service for node registration, identity, asset distribution, validation, tasks, and network collaboration |
Evolver CLI is not the EvoX Desktop installer. Desktop users install the official application; developers and node operators install Evolver separately when required.
GEP assets
| Name | Meaning |
|---|---|
| GEP | The protocol and data model for producing, validating, reusing, and recording experience |
| Gene | A reusable strategy with trigger signals and execution constraints |
| Capsule | One recorded instance with input, execution, result, and validation |
| Evolution Event | An event record for evolution steps, state changes, and outcomes |
| Recipe | An ordered workflow of Genes and Capsules |
| Skill | Work instructions, tool rules, and execution conventions read by an agent application |
| Memory graph | The local graph of assets, events, and reuse relationships |
.gepx | Portable Evolution Archive for exporting, backing up, and migrating Evolver/GEP experience |
Identity and credentials
node_id is an inventory-safe node identifier. node_secret, Hub tokens, and signing keys are secrets. Credentials are not Genes, Capsules, or .gepx experience and should not enter archives, screenshots, logs, or repositories.
Usage rules
- Identify whether a capability belongs to EvoX Desktop, EvoX Core, Evolver, or EvoMap Hub.
- Distinguish product entry points, command-line tools, protocols, assets, events, archives, and credentials.
- Record a verification date for commands, defaults, versions, and platform coverage.
- Do not rename Evolver commands as EvoX Desktop operations or treat website deployment as an application release.
Related pages
EvoX Docs · Overview · Explore