Snapshots
A snapshot is an archived baseline state you can revisit later.
Snapshots are read-only and designed for traceability, not day-to-day editing.
Where snapshots appear
- Snapshot index:
/snapshots - Snapshot detail:
/snapshots/{scenario}
From the snapshots page, you can inspect historical baselines and restore an eligible snapshot back to baseline when needed.
How snapshots are created
Snapshots come from two paths:
- Manual snapshot: taken from the Snapshots page
- Automatic snapshot: created during scenario promotion before baseline is replaced
Both are represented as baseline archive scenario kinds internally and remain immutable.
What a snapshot gives you
- point-in-time structural baseline
- read-only historical reference for review/audit
- delta context linked to promotions
- restore path to make an older baseline live again
Snapshot restore flow
- Open
/snapshots. - Choose a snapshot.
- Click Restore.
- Confirm in the restore modal.
- Wait for async promotion task completion.
Restore operation archives current baseline first, then restores selected snapshot values as the new live baseline.
Read-only expectations
In snapshot context:
- no create/edit/delete for structural entities
- no edit-mode drag/drop
- no placement mutation actions
You can analyze and export, but not mutate.
When to use snapshots
- before high-risk restructuring
- before cross-functional promotion windows
- for post-incident baseline recovery
- for governance and historical reporting