Follow a Structured Learning Path
Overview
Follow an ordered set of governed flight lessons
User
An AeroSim player
What the user can do
Follow an ordered set of governed flight lessons
Why the user benefits
The player receives one coherent, observable capability.
User need
The player needs AeroSim to follow an ordered set of governed flight lessons.
In scope
Follow an ordered set of governed flight lessons
- StatusProposed
- OwnerAeroSim Scope (proposed; not accepted)
- Parent EpicAEROSIM-EP-7
- Depends onAEROSIM-FT-28
Tasks
AEROSIM-TS-9Planning status: In BacklogRender the governed learning path from lesson and pilot state
The player sees each configured lesson exactly once in governed order with an available, current, or completed state determined from lesson prerequisites and the active pilot's progress snapshot.
- ComponentAPI Service — learning-path projection and Web Application — training path view
- Depends onNone
- RequirementsFR-0014
AEROSIM-TS-10Planning status: In BacklogAdvance and retry lessons from recorded attempt outcomes
A recorded terminal lesson attempt changes the active pilot's progression at most once, while retry creates a new attempt from the lesson's declared initial state without changing progression.
- ComponentAPI Service — lesson-attempt and progression service, Pilot Data Store — lesson attempts, and Web Application — training result client
- Depends onAEROSIM-TS-9
- RequirementsFR-0015, NFR-0001, NFR-0002, NFR-0005, NFR-0006, NFR-0013
Acceptance outcomes
- 01
The learning path shows available, current, and completed lessons in governed order.
- 02
Lesson progression changes only from recorded lesson outcomes.
Functional requirements and measurable criteria
guide training progress
The system shall present the current training objective and observable progress.
Acceptance 01
Givena valid current Feature configuration and defined initial state
Whenthe relevant user action or simulation step occurs
Thenthe observable result must present the current training objective and observable progress
EvidenceFuture reviewed automated and browser evidence must verify this outcome against the current requirement.
Acceptance 02
Givenan invalid or unsupported input at the same boundary
Whenthe system evaluates the input
Thenthe system must reject or recover visibly without publishing a misleading result
EvidenceFuture negative-path tests and browser evidence must verify explicit failure or recovery behaviour.
present training result and retry
The system shall present training feedback and allow retry from the initial state.
Acceptance 01
Givena valid current Feature configuration and defined initial state
Whenthe relevant user action or simulation step occurs
Thenthe observable result must present training feedback and allow retry from the initial state
EvidenceFuture reviewed automated and browser evidence must verify this outcome against the current requirement.
Acceptance 02
Givenan invalid or unsupported input at the same boundary
Whenthe system evaluates the input
Thenthe system must reject or recover visibly without publishing a misleading result
EvidenceFuture negative-path tests and browser evidence must verify explicit failure or recovery behaviour.
Non-functional requirements
- NFR-0001 — Performance
Maintain responsive rendering and simulation.
- NFR-0002 — Determinism
Reproduce defined simulation and restart results.
- NFR-0005 — Resource governance
Keep browser and deployed workload consumption within explicit budgets.
- NFR-0006 — Compatibility
Support the declared browser and input compatibility matrix.
- NFR-0013 — Trustworthy training progression
Every progression change, evaluation, retry, and recommendation resolves to one recorded pilot lesson attempt.
Risks
- Risk
Prototype behaviour may not meet the current acceptance outcomes.
Original source and prototype evidence
- discord: Authoritative clean-slate Scope recommendation.
- discord: Clean-slate Scope discussion 1.
- discord: Clean-slate Scope discussion 2.
- discord: Clean-slate Scope discussion 3.
- 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 application behaviour is discovery evidence only; it establishes no current Scope approval, implementation approval, acceptance, or release state.