Editing & Saving

Editing happens on the same in-app editor described in Writing a Scenario — opened from Edit content on an existing Scenario rather than New scenario.

Who can edit

Owner, Admin, Member, and Editor Project roles can edit Scenario content. Reviewer and Reader cannot — see Roles & Permissions for the full breakdown. If you lack edit permission, the edit page shows a read-only message naming your current role. Reviewers can still change either status axis from Explore or the Scenarios list even without edit access.

A Deprecated Scenario stays editable — retiring a fact doesn’t freeze it.

Opening the editor

From Scenarios, click Edit content on any row. The edit page shows the Scenario’s index label, title, and Place; the Relationships pickers; and the Path — its ordered Conditions and Results with their evidence blocks and per-Condition Grounding choice. See Relating Scenarios.

Save flow and version conflicts

Click Save. ArtlessDev writes the change straight to the Project’s database — there’s no external sync step. Every Scenario carries a version counter: your save states the version you started from, and if someone else saved the same Scenario first, the version no longer matches and the save is rejected rather than silently overwriting their change. You’ll be prompted to reload the latest version and reapply your edit on top of it.

Drift notes

When a Scenario’s verification status is a gap, the edit page shows a plain Drift note text box for describing what actually happens instead. This is separate from the Scenario’s own path and evidence, and it’s available on every plan — documenting a gap is never gated. See Scenario Status.

Retiring a Scenario

Retirement is asymmetric, and happens from the status control rather than the editor. A Draft can be deleted and restored later from Deleted scenarios in Project settings; a Published Scenario can never be deleted, because something may already cite it — set its lifecycle to Deprecated instead. See Managing Status.