Runtime Composition
Audience
Developers, QA engineers, support engineers, security engineers, solution architects, and implementation partners.
Reference Content
This page records source-verified technical behavior and boundaries for the workforce-scheduling capability.
Summary
The .NET 8 web process composes scheduling with attendance, messaging, persistence, authentication, observability, health reporting, and transitional compatibility. Repositories and application services are scoped to a request; the outbox relay runs as a hosted worker.
Startup composition
The process registers shared tracing and messaging, tenant context, database context, repositories, unit of work, audit and timeline writers, resolver, commands, queries, compatibility services, and a payroll-lock client. Schema migration is performed during ordinary startup unless explicitly suppressed; development-only seed behavior is also present. A separate backfill execution path exists.
Request pipeline
Correlation runs before documentation UI, authentication, authorization, tenant-error translation, and endpoint mapping. Health and service-information endpoints are mapped beside attendance, direct shift-policy, and compatibility surfaces.
Caveat
Authorization middleware registration does not itself secure an endpoint. The mapped scheduling groups do not declare an authorization requirement and no fallback policy was verified.
Source References
microservices/src/attendance-service/Program.csmicroservices/src/shared-kernel/Extensions/ObservabilityExtensions.csmicroservices/src/shared-kernel/Middleware/CorrelationIdMiddleware.cs
Related Articles
See Also
Keywords
- Workforce scheduling
- Shift policy
- Attendance integration
Revision Information
- Status: Draft
- Last reviewed: 2026-07-20
- Next review: 2026-10-20