Ruflo v3.32.26 β Safer Self-Improvement
Ruflo v3.32.26 β Safer Self-Improvement
Ruflo can now test improvements to its retrieval behavior without changing the configuration you are currently using.
This release introduces a controlled flywheel:
evaluate β review β promote
Ruflo evaluates candidate settings, records the results in a verifiable receipt, and waits for you to approve an accepted candidate. Nothing is promoted automatically.
Why this matters
Self-improvement should not mean handing control to an optimizer.
With v3.32.26, you can:
- test retrieval-policy improvements against held-out tasks;
- compare quality, latency, token use, failures, and cost limits;
- inspect the evidence before making a change;
- activate an accepted candidate with an explicit command;
- audit what changed through receipts and promotion history.
Darwin can explore and propose candidates, but Ruflo remains responsible for deciding whether a candidate is safe to promote.
Install or upgrade
npm install --global ruflo@3.32.26
ruflo --versionYou can also try this release without a global installation:
npx ruflo@3.32.26 metaharness flywheel status --project-root .Try the flywheel
Check the current state:
ruflo metaharness flywheel status --project-root .Run a local evaluation:
ruflo metaharness flywheel run \
--project-root . \
--proposer local \
--sample 40 \
--private-key /path/to/flywheel-private.pem \
--public-key /path/to/flywheel-public.pemReview the results:
ruflo metaharness flywheel receipts --project-root .
ruflo metaharness flywheel history --project-root .Promote an accepted result:
ruflo metaharness flywheel promote <receipt-id> \
--project-root . \
--public-key /path/to/flywheel-public.pem \
--confirmThe end-user quick start includes signing-key setup and a complete walkthrough.
Also new
- First-class
metaharness flywheelcommands in the CLI and MCP. - Darwin candidate evolution through
metaharness evolve. - Stable benchmark creation and verification through
metaharness bench. - Signed receipts that detect altered evaluation evidence.
- Atomic, one-time promotion with consistent crash recovery.
- Safe local operation when the optional Darwin or Flywheel packages are not installed.
Safe by default
- Evaluation never changes the active policy.
- Promotion requires an accepted receipt and explicit
--confirm. - Stale, changed, untrusted, or already-used receipts are rejected.
- Candidate resource limits are enforced before candidates are considered.
- Darwin failures do not silently become Darwin-authorized promotions.
- Automatic unattended promotion is not enabled in this release.
v3.32.26 currently applies the new loop to bounded retrieval-policy tuning. Tool-policy evolution, model-policy evolution, and unattended autopilot remain disabled until their separate security and spending controls are ready.
Compatibility
This is a backward-compatible patch release. Existing Ruflo workflows continue to work, and the new flywheel remains opt-in.
Published packages:
ruflo@3.32.26
claude-flow@3.32.26
@claude-flow/cli@3.32.26
Validation
The release passed the focused flywheel suite, signed-receipt and tamper checks, stale-state and crash-recovery tests, resource-limit tests, and a 100-way concurrent promotion test that produced exactly one successful promotion.