gonuExplore the impact before the change.
Trace possible code impact, inspect related tests and compare explicit assumptions before approving implementation.
Public demo · no login needed. Real workspace use requires sign-in, project access and a configured release.
TAKE A LOOK INSIDE
See how the workflow fits together.
All screens use synthetic sample content. Clicking through this demo does not run a model, access your files, change an account or use your allowance.
Choose the files involved and state the proposed change in Future Scenarios.
Enter known measurements only when useful. Keep the input values and calculation basis visible.
Open Verification → Change Rehearsal. Review a baseline, explicit alternatives and the command before running separate offline copies.
Scenario / Replace session cache
src/session-store.ts
Auth and session handlers
Session expiry test candidates
A useful first request
What might removing this cache affect? Show source references, test candidates and uncertainty before proposing an experiment.
MADE FOR Engineers and architecture reviewers
When it earns its place.
Review a dependency removal or design change without treating an AI estimate as a measured production result.
A smaller, evidence-led experiment and a clear review boundary.
Rehearsal requires separate approval and an isolated executor. It cannot silently deploy a proposed change.
CURRENT CAPABILITIES
Know exactly what to expect.
Implemented beta workflow. Your server needs the matching release, project access and required setup.
Implemented in the beta
- Transitive static impact candidates and related records/tests.
- Visible assumption-based arithmetic.
- Existing offline baseline/alternative rehearsal workflow.
Not available yet
- Production-equivalent simulation.
- Automatic reliable predictions of cost, races or response time.
GET READY
Start with the right context.
- A scanned project and selected file paths.
- Your own measurements for optional capacity or cost calculations; an offline executor for rehearsal.
Brain workflows require the matching API/Web release and an authorized managed project. The model, executor and integrations must be configured for the task you choose. Opening a demo does not enable an integration.
Explore future scenarios