LMS Events Overview

Summary

Source-backed overview of Training event concepts and current delivery maturity.

Audience

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

Reference Content

Concept	Confirmed Training state
Domain event	No abstraction, collection, or type found
Integration contract	Nine shared immutable contract types
Outbox record	Eight invoked contracts can be staged with business changes
Relay	Processor type and dependencies registered; no Training trigger
Inbound consumer	None found
Confirmed consumer	Notification recognizes all nine names
HTTP integration	Gateway proxy/aggregation and Document client
Delivery maturity	Foundation until an active Training relay is verified

“Notification recognition” means the consumer binds an event name and can map a compatible message. It does not prove that Training publishes the message. Contract definitions, staged outbox rows, broker publication, and notification delivery are separate states.

Source References

• microservices/src/contracts/Events/TrainingLifecycleEvents.cs
• microservices/src/training-service/Program.cs
• microservices/src/training-service/Infrastructure/TrainingDbContext.cs
• microservices/src/notification-service/Application/EventNotificationResolver.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