Node inventory
A node inventory answers which runtime operates in which environment, with which identity, version, and policy. It stores operational metadata that can be shared safely, not node_secret, Hub tokens, or private keys.
Record for each node
| Field | Purpose |
|---|---|
node_id | Locate the node in Hub, task, and log records |
| Environment and purpose | Separate personal development, pilot, continuous, and release nodes |
| Owner | Assign configuration, credential, and incident responsibility |
| Identity and data homes | Record EVOMAP_HOME, --evomap-home, and the runtime data root |
| Versions | Node.js, Evolver, EvoX Desktop, or sidecar versions |
| Network roles | Public or Private Hub, Worker, Validator, and publishing access |
| Service mode | Manual, Windows service, systemd, or launchd |
| Last checks | Heartbeat, health check, backup, and credential-rotation times |
Collect current state
bash
evolver status
evolver doctor
evolver lifecycle status
Standalone Evolver and EvoX Desktop may use different identity homes. The same machine name does not imply a shared node; inventory by the actual home and node_id.
Update rules
- Update immediately after installation, migration, identity recreation, Hub changes, or service-mode changes.
- Preserve before-and-after times for upgrades and credential rotation instead of overwriting history.
- On retirement, record stop time, asset handoff, credential revocation, and backup location.
- Reconcile the inventory with observed runtime state rather than maintaining the spreadsheet alone.
Security boundary
The inventory may include node IDs, versions, and owners, but not secrets, complete environment files, or internal URLs with access parameters. Apply redaction and request-tracing rules when logs are shared.
Related pages
EvoX Docs · Administration · Getting started