LMS Integration Reference
Summary
Verified boundaries include Document HTTP, Gateway HTTP forwarding/aggregation, shared messaging contracts, Notification consumption, and stored employee references.
Audience
Business, product, engineering, QA, support, operations, architecture, security, and implementation reviewers.
Reference Content
| Boundary | Direction | Evidence | Classification |
|---|---|---|---|
| Document Service | Training outbound HTTP | Material and certificate store/download client | Transitional |
| Gateway | Gateway to Training HTTP | ESS training forwarding and dashboard/route aggregation | Transitional |
| Notification | Training contracts to Notification consumer | Nine recognized names; Training relay trigger absent | Transitional |
| Shared messaging | Training registration and outbox processor abstraction | Staging exists; publication unconfirmed | Foundation |
| Employee | Stored employee-user/contact references | No Training-to-Employee client or event subscription | Foundation |
| Workflow | None found | No Training Workflow integration | Not implemented |
HTTP dependencies are not subscriptions, and contract recognition is not delivery.
Requires confirmation
Policy ownership, fine-grained authorization, operational governance, future-state terminology, and retirement criteria require confirmation where not implemented.
Source References
microservices/src/training-service/Application/DocumentServiceClient.csmicroservices/src/gateway-api/EssEndpoints.csmicroservices/src/notification-service/Application/EventNotificationResolver.csmicroservices/src/training-service/Program.cs
Related Articles
See Also
Keywords
- LMS reference
- LMS Integration Reference
Revision Information
- Status: Draft
- Last reviewed: 2026-07-17
- Review cycle: Quarterly