Archived scenarios

Archived scenarios are preserved planning records that are no longer editable.

They help you keep decision history without cluttering active modeling space.

What becomes archived

You will encounter archived records in three common cases:

planning scenario explicitly archived
scenario promoted and stored as applied history
baseline snapshot archives created through promotion/snapshot workflows

Editing behavior

Archived contexts are read-only.

That means:

edit mode controls are unavailable
create/update/delete actions are blocked
only explicit unarchive flows (where allowed) can return a planning scenario to modeling

Baseline archive snapshots are not unarchivable.

Where to view archived scenarios

Scenarios list with archived filter
Snapshots list for baseline archives

Use active vs archived views deliberately so your team knows which scenarios are still open for change.

When to archive a planning scenario

Archive when:

option is superseded by a better scenario
proposal is complete and only needed for reference
review has concluded and scenario is no longer active work

Do not archive while key reviewers are still validating deltas.

Good governance pattern

keep active scenario list short and focused
archive stale branches promptly
keep naming clear so archived records remain interpretable months later