Plan, execute and review changes
Keep preparation, execution and canonical Apply distinct.
Read as MarkdownPrepare a plan
Use the Plan button, or Shift+Tab while the composer has focus. Specify your objective, constraints and acceptance conditions. Review the structured project plan and edit it before execution. A saved plan is not evidence that its steps ran.
Execute in isolation
Explicitly approve execution. The assistant works on an isolated candidate; that is not yet your accepted project. Inspect command results, warnings and simulation evidence. Approval applies to the particular action and revision, not to unrelated later work.
Compare and decide
Changes shows the current candidate against its baseline. Project History contains retained revisions and lifecycle records. Review files and supported object/visual comparisons, then Apply or reject. Unsupported comparisons must say so. A candidate modified after review needs fresh approval.
Recover safely
If your trusted project changes concurrently, resolve the conflict instead of overwriting it. Rollback must preserve unrelated later edits. Save a backup before major changes and distinguish a visually attractive result from a validated simulation.