Fork a live scenario
A live scenario is one learners are running right now. Substantive edits to a live scenario can’t happen in place — they would change the work mid-flight for whoever is partway through. Forking creates a new draft from the live version. The new draft goes through validation and promotion again. The previous live version stays put for in-flight engagements until they end. No rug-pulls.
See scenario fork for the full mechanics.
What counts as substantive
These changes require a fork:
- Changing actors — adding, removing, or rewriting a role brief.
- Changing the engagement phases — the sequence the learner moves through.
- Changing the competency vector — which sub-competencies the scenario exercises and at what level.
- Changing weights — how strongly each dimension contributes to evidence.
- Changing success criteria — what a competent run looks like.
What’s cosmetic (no fork needed)
- Fixing a typo.
- Polishing a sentence in the trigger without changing what happened.
- Clarifying a phrase in an actor brief without changing what the actor wants or how they behave.
Cosmetic edits by an admin are allowed in place and are logged. If you’re not sure whether your change is cosmetic or substantive, treat it as substantive and fork.
How to fork
Open the scenario detail. Click Fork. A new draft opens at Step 1 of the authoring flow with all your previous answers pre-filled. Make your changes. Run the realism preview. Submit for peer validation. The new draft moves through the same gates as any other scenario.
Once the new draft is validated and promoted, the previous live version retires. In-flight engagements on the previous version finish on the previous version — they are not migrated.
When something goes wrong
- You forked but a field looks empty. The form autosaves as you type; refresh and the draft should restore. If a field is genuinely missing from the pre-fill, copy it from the previous live version (still readable from the scenario library) and re-enter it.
- You didn’t mean to fork. Discard the new draft from the scenario detail. The previous live version is unaffected — forking does not retire the live version until the new draft is promoted.
- You want to change two unrelated things. Two forks, two drafts. Keep each fork focused on one substantive change so peer validators can sign off without conflating concerns.
- A learner is mid-engagement and asks why their scenario looks different from a peer’s. They are running the previous live version; their peer started after the fork was promoted. Both are correct.