Rollout checklist
Use one node as a pilot and verify installation, identity, policy, service lifecycle, and recovery before expanding to a team or long-running environment.
Commands on this page were verified on September 21, 2026 against
@evomap/[email protected]. That package requires Node.js^22.13.0 || >=23.4.0; check package metadata andevolver --helpwhen using another version.
Before the pilot
- Assign an owner, environment, Hub, identity home, and data home.
- Pin the sources of Node.js, Evolver, and related application versions.
- Back up node identity, GEP assets, configuration, and events.
- Disable unneeded Worker, Validator, auto-publish, and paid behavior by default.
- Set task-level file caps, line caps, forbidden paths, and validation commands.
Start and inspect
evolver doctor
evolver status
evolver lifecycle status
evolver lifecycle check
For continuous operation, choose the supported Windows service, systemd, or launchd installation. After startup, verify process identity, latest heartbeat, data home, and the stop path rather than checking only that a process exists.
Legacy scheduled tasks
Check for legacy scheduled tasks and duplicate startup entries before and after an upgrade. Preview cleanup first:
evolver lifecycle cleanup-legacy-tasks --dry-run
Clean only after confirming the targets and preserving the preimage. If cleanup removes the wrong entry, restore from the saved preimage instead of guessing the original task arguments.
Acceptance criteria
- One bounded task completes with inspectable evidence.
- Stop, restart, and operating-system restart match policy without duplicate processes.
- A backup restores into an isolated directory and its events and assets can be read.
- Network roles, publishing, and budget behavior match the inventory.
- The owner can locate a failed request without reading clear-text secrets.
Keep any failure within the pilot, restore the old configuration or stop the service, and investigate before expansion.
Related pages
EvoX Docs · Administration · Getting started