Asset paths

Standalone Evolver stores node identity, GEP assets, memory, Skills, and logs in separate locations. Decide what needs backup and what contains credentials before changing any path.

Common directories

Defaults expand from the run directory and repository. Use evolver --print-env to inspect final paths rather than guessing from relative values.

Plan the layout

1. Put EVOLVER_HOME on persistent storage accessible only to the runtime account.
2. Back up GEP_ASSETS_DIR separately from source; if it lives in the repository, define what may be committed.
3. Add log rotation, retention, and redaction.
4. Keep remote-memory URLs and keys outside portable asset archives.
5. Stop writers before migration, verify counts and digests after copying, then switch configuration.

Internal paths in EvoX Desktop

EvoX Desktop pins its built-in Evolver to the application agent directory:

<agentDir>/evolver/
├── assets/
├── memory/evolution/
└── settings.json

<agentDir>/evomap/

When launching managed children, Desktop resets EVOLVER_HOME, EVOMAP_HOME, EVOLUTION_DIR, GEP_ASSETS_DIR, and EVOLUTION_ASSETS_DIR so reuse and recall share one asset root. Ambient shell values should not replace these managed paths.

Backup and restore

Back up node identity, GEP assets, memory, Skills, settings, and necessary logs as separate classes. Test a restore in isolation. Do not restore an old secret over a new node identity. Re-scan .gepx files and shared logs for credentials, personal data, and local paths.

If assets disappear after restart, inspect the effective path for a temporary directory, container layer, or different working directory before re-syncing from Hub.

EvoX Docs · Configuration · Paths and platforms