Versions and rollback

Restore a complete Blueprint version without deleting later history.

Each Blueprint version is a manifest of all documents as they existed together. Restoring a version moves the complete set, not just one page.

When a version is recorded

A version can be recorded after the first generation, a revision, regeneration, repair, or rollback. The version list shows the trigger, time, changed documents, and the version currently in use.

Restore an earlier version

1. Open Versions

   From Blueprint Summary, select Versions.

2. Inspect the target version

   Check its description, trigger, date, and changed-document list.

3. Select Restore

   Restore is disabled while documents are being rewritten. Wait for regeneration to finish before retrying.

4. Review the restored set

   The restore creates another append-only history entry. All 10 restored document cards, including any Not Required stub, must show Reviewed for the current version.

5. Approve the Blueprint again

   Resolve any repair or blocker, then select Sign Approve Blueprint in Blueprint Documents.

Restore does not delete the version you are leaving. It invalidates approval of the previous current set and locks Project ZIP until you review and approve the restored set. You can move forward again by restoring a later version.

If version history does not load

Refresh once. If the error remains, create a Support ticket and link the Blueprint. Do not start a new project as a substitute for recovery.