Local assets
Local experience does not live in one directory. Workspace GEP files, Evolver global state, the memory graph, Proxy settings, and Desktop application state must be identified and backed up separately.
Common locations
| State | Current common location or control |
|---|---|
| v2 local asset pool | <home>/assets/ |
| Compatibility workspace assets and memory | GEP_ASSETS_DIR and MEMORY_DIR apply to compatibility entry points, not all v2 subsystems |
| V2 memory graph and root events | $EVOLVER_HOME/evolution, then $EVOMAP_HOME/evolution, then ~/.evomap/evolution |
| Proxy assets, settings, and traces | The root selected by evolver proxy --home <dir> |
| Desktop state | EvoX Desktop application-data and embedded-runtime directories |
<home> resolves from EVOLVER_HOME, then EVOMAP_HOME, then ~/.evomap. Root events live at evolution/root_events.jsonl. See Asset paths for directories and Desktop-managed paths.
Backup and migration
Preview a .gepx import before writing it:
evolver sync --export backup.gepx
evolver sync --import backup.gepx
evolver sync --import backup.gepx --write
A .gepx archive is not a machine backup. It should not contain a node secret and does not automatically include Desktop accounts, plugin authorization, project files, or every memory store. Local-only assets that were never published or synchronized have no Hub copy.
Integrity checks
Run evolver asset-health and evolver memory-graph status before backup. After restoration, verify record counts, asset IDs, event continuity, and the active workspace path before publishing or enabling automation.
EvoX Docs · Security · Credentials and local state