Skip to main content

Attendance Future Evolution

Summary​

Only evolution directions evidenced by compatibility, migration, parity, and cutover assets are documented.

Audience​

Architects, developers, product owners, QA engineers, DevOps engineers, and support engineers.

Evidence-backed direction​

Current assets support progressive migration of attendance-record and Time Office ownership from the monolith to Attendance Service. Direct/shadow validation, compatibility adapters, idempotent backfill, parity comparison, go/no-go evaluation, independent routing decisions, and rollback capability show an intended staged cutover rather than a single replacement event.

After verified ownership transfer, compatibility adapters and legacy routing may become candidates for retirement, but no approved retirement date or removal plan is confirmed. Completing employee-profile synchronization, Leave/holiday coordination, stronger health and metrics, dedicated automated tests, policy/scheduling extensions, and Payroll consistency controls are reasonable gaps identified by source; they remain Requires confirmation, not roadmap promises.

Future detailed API, database, events, UI, operations, reference, and troubleshooting documentation is already reserved in the portal. Contract versioning, consumer migration, data reconciliation, and security review must accompany any boundary change. No delivery dates, target architecture beyond verified cutover assets, or new feature commitments are asserted.

Source References​

  • microservices/src/gateway-api/Program.cs
  • microservices/docs/attendance-shift-cutover-runbook.md
  • microservices/scripts/compare-attendance-shift-parity.ps1
  • microservices/src/attendance-service/Backfill/ShiftWeeklyOffBackfillRunner.cs
  • microservices/src/attendance-service/Api/AttendanceCompatibilityEndpoints.cs

See Also​

Keywords​

  • Attendance Service
  • Attendance Future Evolution

Revision Information​

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