LMS Operational Checklist
Summary
This is a read-only evidence checklist, not a deployment or recovery procedure.
Reference Content
- Confirm approved release and ownership categories.
- Confirm configuration categories are present without recording values.
- Confirm migration-state and service-health categories.
- Confirm correlation and sanitized logging are available.
- Confirm Training reads and a synthetic supported lifecycle.
- Confirm Document-dependent features separately.
- Confirm outbox staging without claiming relay delivery.
- Confirm Gateway ESS behavior and data-scope expectations.
- Confirm Notification recognition separately from publication.
- Confirm synthetic smoke evidence in an isolated environment.
- Record limitations, approvals, and escalation owner.
- Stop before any replay, cleanup, direct data change, rollback, or production mutation unless separately authorized.
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.csmicroservices/src/shared-kernel/Extensions/ObservabilityExtensions.csmicroservices/src/shared-kernel/Extensions/ServiceCollectionExtensions.csmicroservices/src/training-service/Infrastructure/Persistence.csmicroservices/src/shared-kernel/Messaging/OutboxProcessor.csmicroservices/src/training-service/Application/DocumentServiceClient.csmicroservices/src/training-service/Api/TrainingEndpoints.csmicroservices/src/gateway-api/EssEndpoints.csmicroservices/src/gateway-api/Program.csUI/salary-ui/apps/client-hrms-portal/src/ess/EssPages.tsxmicroservices/scripts/smoke-training.ps1
Related Articles
See Also
Keywords
- LMS operations
- LMS Operational Checklist
Revision Information
- Status: Draft
- Last reviewed: 2026-07-17
- Review cycle: Quarterly