Managing Status
Scenario Status covers what the two axes mean — lifecycle (Draft / Published / Deprecated) and verification (Not attempted / Fit / Gap). This page covers changing them in the app.
Who can change status
Section titled “Who can change status”Owner, Admin, Member, Reviewer, and Editor Project roles can change either axis. Reader cannot — they see status badges read-only. See Roles & Permissions. A banner at the top of the page explains your access when it’s limited.
Opening the status control
Section titled “Opening the status control”Click a status badge, or Change status, to open the status popover (a sheet on mobile) from Explore, the Scenarios table, or a Scenario’s own header. It has one section per axis — Lifecycle and Verification — because the two are set independently. Changing one never changes the other.
Lifecycle
Section titled “Lifecycle”Pick Draft, Published, or Deprecated. There is no gate and nothing to confirm: publishing says the team stands behind the Scenario as written, whether or not anyone has checked it, and Deprecated retires a fact without freezing it — a deprecated Scenario stays editable and verifiable.
Below the picker, retirement is offered asymmetrically. A Draft gets a Delete draft button: it stops appearing everywhere and can be restored from Deleted scenarios in Project settings. A Published Scenario has no delete — something may already cite it — so retiring it means setting its lifecycle to Deprecated.
Verification
Section titled “Verification”Pick Not attempted, Fit, or Gap, then Save. Fit and Gap are blocked until every callee — nested children, chain successors, and cross-cutting Features — is itself a fit; the popover names whichever one is holding it up. Picking Not attempted saves immediately, resetting the Scenario to be checked again.
Saving from the popover records the outcome and nothing else. Evidence belongs to a verification pass, below.
Recording a verification pass
Section titled “Recording a verification pass”Picking Fit or Gap also surfaces a Record a verification pass link, which opens the Scenario’s own Verify page — where a check is actually written down. Start pass opens one — a Scenario can have only one open at a time — then walk the path and Record step against each step you checked, with a finding and any evidence. A step you looked at but couldn’t call is a real finding, and is not the same as a step you never checked; everything in a pass is optional.
Finish with Close as fit or Close as gap. Closing publishes that outcome onto the Scenario’s verification status, leaving its lifecycle untouched. Abandon discards the attempt without ruling either way. Past passes stay on the page as the Scenario’s verification history.
Verify all
Section titled “Verify all”When a Scenario’s callees aren’t a fit yet, the popover offers Verify all: record this Scenario and those callees as a fit in one action. Include nested descendants is checked by default; chain successors are individual opt-ins. It only ever records a fit — never a gap, and never a lifecycle change. A Scenario that became a fit this way shows a rollup note saying so, rather than reading as its own check.
Activity history
Section titled “Activity history”Open Activity history from the Scenarios list, or via a status hint on Explore. The log shows changes on both axes, Verify all batches, evidence previews, and content-edit events, each tagged with who or what made the change — see Who changed a status, and how for the five possible sources. Use Load more for older events.
Status vs. content
Section titled “Status vs. content”Changing either status never touches a Scenario’s title, Conditions, or Results — only editing and saving the Scenario itself does that. The overlays and the content live in different places by design; see Scenario Status.