LMS Course Events

Summary

Verified absence of course-content lifecycle event contracts.

Audience

Engineering, integration, QA, architecture, security, and product reviewers.

Reference Content

Course creation, publication, archival, import updates, material creation/deletion, and nested module/lesson creation write local state and evidence where implemented. None invokes a Training integration contract.

No CourseCreated, CourseUpdated, CoursePublished, CourseArchived, MaterialChanged, ModuleChanged, or LessonChanged contract is defined in the Training lifecycle contract source. The assignment/start/completion contracts carry course context but are enrollment lifecycle events, not course domain events.

This gap is Not implemented rather than an unmapped domain event because Training has no domain-event abstraction.

Source References

• microservices/src/training-service/Api/TrainingEndpoints.cs
• microservices/src/contracts/Events/TrainingLifecycleEvents.cs
• microservices/src/training-service/Infrastructure/TrainingDbContext.cs

Related Articles

• LMS Events documentation
• LMS technical documentation

See Also

• Verified event catalog
• Event limitations

Keywords

• LMS events
• Training contracts
• Source-backed integration

Revision Information

• Status: Draft
• Last reviewed: 2026-07-17
• Review cycle: Quarterly