LMS Technical Source Map
Summary
Audience
Engineering, QA, support, documentation, security, and architecture reviewers.
Reference Content
| Capability | Source path | Layer/ownership | Purpose | Maturity |
|---|---|---|---|---|
| Project/runtime | microservices/src/training-service/training-service.csproj | Process | Framework/dependencies | Implemented |
| Bootstrap | microservices/src/training-service/Program.cs | Runtime | Registration/middleware/startup | Transitional |
| HTTP operations/DTOs | microservices/src/training-service/Api/TrainingEndpoints.cs | API | Writes, reads, reports, mappings | Implemented/direct |
| Domain/data model | microservices/src/training-service/Domain/TrainingEntities.cs | Domain | Entities, values, statuses | Transitional |
| Tenant context | microservices/src/training-service/Application/Common.cs | Application | Request tenant/actor abstraction | Partial |
| Document boundary | microservices/src/training-service/Application/DocumentServiceClient.cs | Application/integration | Binary store/download port+adapter | Transitional |
| Persistence/outbox mapping | microservices/src/training-service/Infrastructure/TrainingDbContext.cs | Infrastructure | EF model, filters, event staging | Implemented |
| Outbox/evidence adapters | microservices/src/training-service/Infrastructure/Persistence.cs | Infrastructure | Store, audit, timeline | Implemented |
| Shared contracts | microservices/src/contracts/Events/TrainingLifecycleEvents.cs | Contracts | Outbound schemas | Implemented |
| Notification resolver | microservices/src/notification-service/Application/EventNotificationResolver.cs | Consumer | Training notification intents | Implemented consumer |
| Gateway ESS | microservices/src/gateway-api/EssEndpoints.cs | Gateway | Employee learning composition | Transitional |
| Smoke coverage | microservices/scripts/smoke-training.ps1 | Test asset | Broad HTTP/integration evidence | Partial |
Each authoritative path appears once in this source-map table. Local verification completed on 2026-07-17.
Requires confirmation
Fine-grained authorization, production ownership, operational governance, and future architectural boundaries require confirmation where not implemented.
Source References
microservices/src/training-service/training-service.csprojmicroservices/src/training-service/Program.csmicroservices/src/training-service/Api/TrainingEndpoints.csmicroservices/src/training-service/Domain/TrainingEntities.csmicroservices/src/training-service/Application/Common.csmicroservices/src/training-service/Application/DocumentServiceClient.csmicroservices/src/training-service/Infrastructure/TrainingDbContext.csmicroservices/src/training-service/Infrastructure/Persistence.csmicroservices/src/contracts/Events/TrainingLifecycleEvents.csmicroservices/src/gateway-api/EssEndpoints.csmicroservices/src/notification-service/Application/EventNotificationResolver.csmicroservices/scripts/smoke-training.ps1
Related Articles
See Also
Keywords
- LMS technical architecture
- Source-backed implementation
Revision Information
- Status: Draft
- Last reviewed: 2026-07-17
- Review cycle: Quarterly