Changes and engineering versions
Distinguish working changes, named revisions and recovery points.
Open the engineering view
Use Changes and engineering history from the chat header. First confirm that the intended engineering project is bound. A General conversation or unrecognized project is not automatically a versioned engineering repository.
If the view reports a project inspection problem, preserve the project and check its location and current native document. Do not initialize or overwrite another repository to dismiss the error.
Three different kinds of work
- Working changes are edits not yet recorded as a named revision. Inspect file differences and CAD-aware comparisons where supported before staging or committing.
- Named revisions and branches record intentional engineering history. A branch switch, revert or integration can affect project files and must respect unsaved documents and conflicts.
- Recovery points are not interchangeable with named commits or unapplied AI candidates. A candidate may belong to a separate request and isolated workspace.
Do not assume an activity checkmark created a named commit, or that a named commit proves geometry correctness.
Safe workflow
Save or deliberately preserve manual CAD work before a revision-changing operation. Inspect the selected project, working changes and requested target. Compare the relevant revision and property/feature changes, then use only the operations actually offered by the installed edition.
If an integration or restoration reports conflicts, keep both the original and candidate evidence. Do not silently overwrite binary CAD files or claim they were safely merged. A failed operation should leave a clear recovery path rather than force you to discard work.
Relationship to AI Apply
Engineering history does not replace Preview and Apply. Review the candidate produced by its originating request, and apply only the reviewed contents after conflict checks. A later history entry or recovery checkpoint does not retroactively authorize promotion.
For a failure report include the operation, safe project type/path information, unsaved-document state and visible error. Do not send proprietary CAD files without an agreed safe support process.