Learning Lifecycle¶

Why This Exists¶

This document defines core lifecycle states for Learning Domain records.

Owner¶

The owner is the Chief Product Officer and Enterprise Architect.

Business Value¶

Lifecycle definitions make Academy content, learner progress, certificates, and recommendations predictable and auditable.

Course Lifecycle¶

State	Meaning	Allowed transitions
Draft	Course is being designed.	Review, Archived.
Review	Course is ready for quality review.	Published, Draft, Archived.
Published	Course is available for enrolment.	Revised, Archived.
Revised	Course has a new version under preparation.	Published, Archived.
Archived	Course is no longer available for new enrolment.	Draft only by formal restoration.

stateDiagram-v2
    [*] --> Draft
    Draft --> Review
    Review --> Published
    Review --> Draft
    Published --> Revised
    Revised --> Published
    Draft --> Archived
    Review --> Archived
    Published --> Archived
    Archived --> [*]

Learner Progress Lifecycle¶

State	Meaning
Not Started	Learning asset is available but not started.
Enrolled	User has enrolled in a course or path.
In Progress	User has started at least one required activity.
Completed	Completion criteria are satisfied.
Failed	Required assessment was failed and no passing attempt exists.
Deferred	User postponed the learning item.
Expired	Learning completion is no longer current under a policy.

Certificate Lifecycle¶

State	Meaning
Pending	Completion is being evaluated.
Issued	Certificate was issued after criteria were satisfied.
Revoked	Certificate was invalidated by policy.
Expired	Certificate is no longer current because validity period ended.

Recommendation Lifecycle¶

State	Meaning
Created	Recommendation has been generated.
Presented	Recommendation has been shown to the user.
Accepted	User or organization accepted the recommendation.
In Progress	Related learning has started.
Completed	Recommended learning was completed.
Dismissed	User declined the recommendation.
Expired	Recommendation is no longer relevant.

Lifecycle Governance¶

Lifecycle transitions should be event-backed. A UI may request a transition, but the domain must decide whether the transition is allowed under Learning rules and policies.