Change agent configuration through evidence and rollback.
Propose, preregister, evaluate, review, promote, export, and roll back changes to agent instructions, skills, or routing while keeping governance outside candidate control.
1. See it
2. How it works
3. Why it wins
4. Use it to…
Improve a research instruction
Compare a candidate that adds counterevidence requirements with the current version on registered cases.
Evaluate a routing change
Record paired results and independent review before activating new local configuration.
Roll back a regression
Restore a recorded prior version and export it back to your host.
5. The shift it creates
- Prompt edits ship after one appealing example
- Candidates can overwrite their own evaluation policy
- A bad live configuration is hard to reconstruct
- Tie each candidate to the version it replaces
- Require paired training cases, a held-out case, and separate review
- Keep prior configuration available for rollback
6. What's inside
7. The details
How it actually works
Exactly what it does — and when.
An operator proposes a new routing rule, registers matched cases before testing, and records paired evidence plus an independent review. The local configuration changes only after promotion; if later tasks regress, the prior version remains available for rollback.
Who it's for
Teams maintaining agent prompts
need changes evaluated before activation
Skill and router owners
need versioned promotion and rollback
Host developers
can supply trusted evaluators and permission boundaries
Questions, answered
Ready to put Agent Evolution to work?
Instant download · one-time price · own forever · all sales final