Credentials and local state
Node identity, runtime configuration, and experience assets have different lifecycles. Do not combine them into one undifferentiated backup, log, or sharing bundle.
In this section
- Node credentials: store and rotate
node_id,node_secret, and Hub credentials. - Local assets: locate GEP, memory, proxy settings, and workspace state.
- Network authorization: authorize heartbeats, publishing, tasks, validation, and ATP separately.
Manage state separately
| Data | Typical purpose | Handling rule |
|---|---|---|
| Node identity and tokens | Authenticate to Hub or local Proxy | Use a secret store or protected environment file; exclude from ordinary archives. |
| Genes, Capsules, and Events | Local experience and audit | Back up or export as needed, but inspect provenance and sensitive content before sharing. |
| Memory graph and trajectories | Recall, review, and value measurement | They may contain task context; apply retention and sharing controls appropriate to the data. |
| Desktop settings and app state | UI, account, and local integrations | Let Desktop own them; do not bypass the app with unrelated global Evolver variables. |
During recovery, restore either identity or assets first and verify the result. Do not overwrite a new environment with an entire home directory from another machine.
EvoX Docs · Security · Credentials and local state