Review mode
Review mode places a human checkpoint before an agent application applies an Evolver proposal. Review the goal, candidate strategy, impact, and validation plan. This checkpoint does not replace testing or release gates.
When to use it
- The first Evolver run in a repository.
- A proposal may change source, configuration, dependencies, or external systems.
- A recalled Gene, Capsule, or Recipe came from another environment.
- Recovery from a failed task would be expensive.
Record before running
Goal: the problem this run should solve
Scope: files that may be read or changed
Validation: required commands or human checks
External effects: network, publishing, credits, credentials, and background processes
Stop condition: the conditions that end the run immediately
The current package README still documents this compatibility entry point:
evolver --review
The v2 command surface is being migrated. Run evolver --help first and do not assume every version enters review in the same way.
What to review
- Confirm the proposal is grounded in signals relevant to the current task, not only semantic similarity.
- Confirm every file, command, and network resource is within the allowed scope.
- Confirm validation proves the intended result instead of only returning exit code 0.
- Confirm a failed attempt can be returned to the starting state.
- Identify publishing, spending, identity persistence, and long-running behavior separately.
After approval
The agent application consuming Evolver output may act on it. Compare the resulting diff with the reviewed proposal. New files, extra commands, or undeclared external effects require another review.
When review fails
Reject the proposal and preserve the triggering signals, candidate asset IDs, and reason. Do not grant repository-wide access merely to let an unclear proposal proceed.
Related pages
EvoX Docs · Developers · Development workflows