Retry Incomplete Exercises
Overview
Restart an incomplete exercise from a known training state
User
An AeroSim player
What the user can do
Restart an incomplete exercise from a known training state
Why the user benefits
The player receives one coherent, observable capability.
User need
The player needs AeroSim to restart an incomplete exercise from a known training state.
In scope
Restart an incomplete exercise from a known training state
- StatusProposed
- OwnerAeroSim Scope (proposed; not accepted)
- Parent EpicAEROSIM-EP-7
- Depends onAEROSIM-FT-21
Tasks
No Architecture-owned implementation task is currently defined for this Feature.
Acceptance outcomes
- 01
Retry preserves the lesson while restoring its documented starting state.
- 02
The new attempt is recorded separately from the prior result.
Functional requirements and measurable criteria
Retry Incomplete Exercises
The system shall restart an incomplete exercise from a known training state.
Acceptance 01
GivenAEROSIM-FT-22 is exercised within its governed scope under supported conditions
Whenthe primary capability path is completed
ThenRetry preserves the lesson while restoring its documented starting state
EvidenceFuture reviewed automated and browser evidence must verify this exact outcome against the current requirement.
Acceptance 02
GivenAEROSIM-FT-22 is exercised within its governed scope under supported conditions
Whenthe continuation or repeat path is completed
ThenThe new attempt is recorded separately from the prior result
EvidenceFuture reviewed automated and browser evidence must verify this exact outcome against the current requirement.
Non-functional requirements
- NFR-0013 — Trustworthy training progression
Every progression change, evaluation, retry, and recommendation resolves to one recorded pilot lesson attempt.
Risks
- Risk
Representative browser or input configurations may expose an unmet outcome.
Original source and prototype evidence
- discord: Agreed eight-Epic portfolio and Feature decomposition.
- discord: Agreed eight-Epic portfolio and Feature decomposition continuation.
- discord: RootAtSkic directed publication of the agreed Scope update.
Prototype and discovery boundary
Existing implementation is discovery evidence only; it establishes no current approval, acceptance, or release state.