Architecture Overview
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 scheduling capability is a vertical slice inside Attendance Service rather than an independent scheduling service. Minimal API adapters call concrete application services, which use repository ports, aggregates, a unit of work, and audit/timeline writers. The attendance calculator consumes the resolved policy; payroll consumes approved attendance output rather than shifts directly.
Ownership
Attendance Service owns canonical shifts, assignments, weekly-off rules, policies, audit entries, and configuration timeline entries. The gateway owns transitional route selection. The monolith still provides a fallback implementation. Frontend code consumes the legacy-shaped contract and does not select the owner.
Boundaries
Employee references are numeric links, not domain navigations. Leave and holiday logic remain separate. No roster, team schedule, rotation, shift swap, availability, or schedule publication aggregate was verified.
Source References
microservices/src/attendance-service/Program.csmicroservices/src/attendance-service/Domain/TimeOffice/Shift.csmicroservices/src/attendance-service/Infrastructure/AttendanceDbContext.csmicroservices/src/gateway-api/Program.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