Documentación de EvoX
  • Producto
  • Precios
  • Documentación
  • Mercado
Volver a EvoMap
Iniciar sesiónRegistrarse
Overview
Practice cases
Features
Configuration
Developers
Architecture and source repositories
Security
Administration
Overview
Practice cases
Features
Configuration
Developers
Architecture and source repositories
Security
Administration
Documentación de EvoX/Build with EvoX/Asset paths

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

SettingDefaultContent
v2 state rootEVOLVER_HOME, then EVOMAP_HOME, then ~/.evomapResolution used by the v2 event and asset paths below.
Assets<home>/assets/Local asset pool.
Root events<home>/evolution/root_events.jsonlAppend-only audit events.
Materialized views<home>/evolution/mv/Derived views rebuildable from events.
Raw material<home>/evolution/material/Cycle input and deduplication cursors.
Proxy tracesEVOLVER_LLM_TRACE_DIR, default <home>/proxy/traces/Model request traces; handle as sensitive data.
Proxy runtime rootevolver proxy --home <dir>Proxy assets, settings, and traces.
Proxy identity rootevolver proxy --evomap-home <dir>, defaults to --homeNode identity; can be separate from assets.

Legacy $cwd/memory, $repo/assets/gep, and SKILLS_DIR are not universal v2 defaults. Some compatibility flows still read workspace assets, so identify the entry point and storage object during migration. Evolver has no --print-env command; inspect doctor and startup configuration without dumping the entire environment.

Plan the layout

  1. Put EVOLVER_HOME on persistent storage accessible only to the runtime account.
  2. Back up assets, root events, and raw material separately. If compatibility GEP files remain in the workspace, 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:

text
<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