Paths and platforms
This group covers two different but commonly confused topics: where Evolver stores identity, assets, memory, and logs, and how EvoX Desktop separates Pre, Beta, and Stable update channels.
Choose by object
| Object | Documentation |
|---|---|
| Asset paths | Configure standalone Evolver home, GEP, memory, Skills, and logs, and understand Desktop path isolation. |
| Beta and Stable | Understand desktop release channels, version shapes, and signed manifest verification. |
| Containers and CI | Persist identity and assets on stateless runners without leaking credentials or sharing unsafe writable state. |
Path ownership principles
- Give identity, assets, memory, Skills, logs, and workspaces explicit owners.
- Put data that must survive restarts on persistent storage.
- Keep secrets separate from portable asset backups.
- Do not let multiple processes write the same asset directory without coordination.
- EvoX Desktop uses managed internal paths; shell path variables apply to standalone CLI operation.
Platform and release principles
The installed EvoX Desktop version and managed policy determine its update channel. Pre, Beta, and Stable each use a separate manifest, and the client only accepts versions on the selected channel. Before applying a download, the updater checks declared size, SHA-256, and Ed25519 signature.
Ordinary users should not edit feed URLs. Managed environments can pin a supported channel or feed through policy. Unknown channel values are refused rather than guessed.
EvoX Docs · Configuration · Paths and platforms