Does an AI assistant apply changes automatically?
No. A supported connected assistant prepares a proposal. The proposal does not become live until the customer reviews it and explicitly chooses Apply through Mr.AI.
- Proposal is not production.
- Testing does not publish the proposal.
- Apply requires an explicit customer action.
Safe proposal lifecycle
- 1
Open Proposal Review and confirm the affected area, current status, semantic diff, and warnings.
- 2
Validate the proposal against the current workspace configuration.
- 3
If the configuration changed or the proposal is stale or conflicting, create and review a fresh proposal instead of forcing the old one.
- 4
Use Testing when the proposal type supports it. Testing runs separately from production.
- 5
Choose Apply explicitly only when the proposal is ready and the impact is understood.
- 6
After Apply, use Rollback only when that change type has a verified rollback snapshot and Mr.AI offers the action.
How to interpret failures
- Validation failure: the proposal is not ready to apply; inspect the message and refresh the proposal if needed.
- Testing failure: production is not changed by the failed test.
- Apply failure: do not assume the proposal is live; use the returned Mr.AI state as the source of truth.
- Rollback failure: do not assume the previous state was restored until Mr.AI confirms rollback success.
