Review-gated improvement

How Evolution works

Evolution is the bounded loop that lets NEXO inspect recurring patterns, propose changes, and keep those proposals reviewable. It exists to compound what works without letting the runtime silently rewrite itself.

Evidence first Draft PRs Rollback capable One open proposal at a time

See release examples Browse release history Contribution guide

1. Observe Runtime evidence, recurring friction, audit findings, and operator patterns accumulate during normal work.

2. Propose NEXO frames bounded changes with rationale, scope, and intended outcome instead of free-form “self-modification”.

3. Review Public-core changes can go through draft PRs and human review; local/runtime changes still need explicit gates and evidence.

What Evolution can do

Refine prompts, tighten release gates, improve product wiring, open bounded public proposals, and turn recurring patterns into explicit product changes.

What it should not do

Silently rewrite the operator environment, bypass review, mutate unrelated user data, or keep opening parallel proposal branches without closure.

Why the loop matters

Without a review-gated improvement surface, an “adaptive” agent drifts. With it, improvements can compound while still being inspected, measured, and reverted.

Operational constraints

The loop is intentionally constrained

One proposal at a time

The public-facing flow stays reviewable by pausing while its own proposal is still open.

Evidence over vibes

Changes should tie back to observed friction, reproducible drift, or concrete operator/runtime outcomes.

Rollback remains possible

Evolution is useful only if the system can back out of wrong changes instead of building mythology around them.