LMS Operational Escalation

Summary

Code ownership metadata is not an operational roster. Escalation routing below uses responsibility categories only.

Reference Content

Evidence category	Primary responsibility category	Joint review
Lifecycle/API behavior	Training service	Product and QA
Persistence/migration	Training service and database operations	Security where data scope is involved
Document failure	Training and Document service	Gateway/frontend if user-visible
Staged but unpublished event	Training/messaging ownership	Notification if consumed
ESS forwarding	Gateway	Training and frontend
UI-only issue	Frontend	Training/product
Tenant or authorization ambiguity	Identity/security	Training and Gateway

Named contacts, severity policy, response objectives, and after-hours ownership Require confirmation.

Safety and confirmation boundary

No production command, secret, configuration value, internal address, infrastructure detail, direct data change, or replay instruction is provided. Production ownership, approvals, service objectives, alerting, and recovery authority require confirmation.

Source References

• microservices/src/training-service/Program.cs
• microservices/src/training-service/Application/DocumentServiceClient.cs
• microservices/src/training-service/Api/TrainingEndpoints.cs
• microservices/src/training-service/Program.cs
• microservices/src/training-service/Infrastructure/Persistence.cs
• microservices/src/shared-kernel/Messaging/OutboxProcessor.cs
• microservices/src/training-service/Program.cs

Related Articles

• LMS operations
• LMS troubleshooting

See Also

• Technical documentation
• Events documentation

Keywords

• LMS operations
• LMS Operational Escalation

Revision Information

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