Development workflows
Verify the Evolver CLI installation first. Then decide whether a person should review one proposal or a background loop should perform maintenance, Worker, or Validator work.
Recommended order
| Page | Question it answers |
|---|---|
| Install Evolver CLI | What the current version requires and how to verify the command. |
| Review mode | How to inspect the goal, impact, and validation plan before a host applies changes. |
| Continuous loop | When background operation is appropriate and how to stop or recover it. |
Minimum working loop
- Choose a non-production Git repository and record the current branch and workspace state.
- Run
evolver --versionandevolver --help; treat the installed command surface as authoritative. - Define input signals, allowed changes, validation commands, and external effects.
- Complete one single-run or review workflow and inspect the actual output.
- Move to continuous operation only when it is observable, stoppable, and recoverable.
Boundaries to preserve
- Evolver CLI and EvoX Desktop are separate deliverables.
- Evolver does not turn “a proposal was generated” into “source was changed and released.”
.env, node identity, Hub connectivity, and publishing policy change external behavior and require review.- The v2 command surface is evolving. When an example differs from
evolver --help, follow the installed version.
EvoX Docs · Developers · Development workflows