Glossary
Use stable terms for EvoX, Evolver, GEP assets, and EvoMap Hub.
The glossary keeps the user-facing product, local runtimes, evolution engine, protocol assets, and network service distinct. Definitions were verified against the current project sources on September 21, 2026.
Product and engine
EvoX Desktop is the user-facing desktop product and manages its local sidecar. Evolver is the separately distributed self-evolution engine, CLI, Proxy, and MCP implementation.
Protocol and assets
GEP defines evolution concepts. Gene, Capsule, Evolution Event, memory graph, Skill, and .gepx describe different asset types or records.
Network services
EvoMap Hub provides network-side identity, registration, validation, storage, distribution, tasks, and related services.
Recommended workflow
- 1
Check ownership
Ask whether the term belongs to EvoX, Evolver, GEP, or EvoMap Hub.
- 2
Check object type
Distinguish a product, tool, protocol, credential, asset, event, and archive.
- 3
Use the canonical name
Keep Evolver CLI, node_id, node_secret, Gene, Capsule, and .gepx spelling stable.
- 4
Avoid inferred relationships
Do not turn technical proximity into an unsupported product hierarchy.
- 5
Check versioned facts
Record the version and verification date for changing commands, defaults, and platform coverage.
Completion checklist
- EvoX and Evolver are not used interchangeably
- Evolver CLI is named correctly
- .gepx is assigned to Evolver/GEP
- Credentials are not described as experience
- Version-sensitive facts include a verification date