LMS Runtime Composition

Summary

Verified registrations include shared observability/configuration, shared messaging services, HTTP context access, scoped tenant context, TrainingDbContext, outbox store, Document typed HTTP client, OpenAPI, and framework health checks.

No authentication/authorization service registration or endpoint authorization declarations are confirmed. No Training hosted service is registered. Development-only startup may migrate and seed. OpenAPI is enabled. Request correlation and exception mapping are middleware; domain/application service classes are not registered beyond tenant and Document boundaries.

Requires confirmation

Fine-grained authorization, production ownership, operational governance, and future architectural boundaries require confirmation where not implemented.

Source References

• microservices/src/training-service/Program.cs
• microservices/src/training-service/Application/Common.cs
• microservices/src/training-service/Application/DocumentServiceClient.cs
• microservices/src/shared-kernel/Extensions/ObservabilityExtensions.cs
• microservices/src/shared-kernel/Extensions/MessagingExtensions.cs

Related Articles

• LMS technical documentation
• LMS business documentation

See Also

• Technical limitations
• Technical source map

Keywords

• LMS technical architecture
• Source-backed implementation

Revision Information

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