Getting started

Inventory nodes and data before enabling long-running loops or network roles. A working installation is not automatically ready for unattended or team operation.

In this section

• Node inventory: record identity, version, environment, purpose, and owner.
• Runtime policy: decide strategy, review, network, publishing, and budget boundaries.
• Rollout checklist: prove recovery, upgrade, and failure behavior on one pilot node.

Minimum administrative baseline

1. Record each node_id, but never store node_secret in clear text.
2. Pin the source of Evolver, Node.js, Desktop, and sidecar versions.
3. Run evolver doctor and address credential, proxy, legacy scheduled-task, and local-state warnings.
4. Decide whether Hub, Worker, Validator, automatic publishing, ATP, and automatic issue reporting are allowed.
5. Establish backup and recovery paths for GEP assets, the memory graph, configuration, and identity.

Only then choose a lifecycle service, continuous loop, or team network role.

EvoX Docs · Administration · Getting started