Onboarding & Offboarding Technical Documentation

Summary

The implementation is Transitional and spans a .NET layered Recruitment service, the monolith Recruitment and HR Operations controllers, Employee Service, gateway compatibility routing, downstream read models, and a React client. There is no standalone onboarding/offboarding service or shared aggregate.

Audience

Backend and frontend engineers, architects, QA, support, security reviewers, and operators responsible for lifecycle capabilities.

Overview

This section documents architecture, runtime and structure, layers and domain, onboarding and offer acceptance, offboarding and checklist models, application behavior, persistence, cross-domain integrations, workflow and notifications, security context, observability, compatibility, testing, limitations, and the source map.

All content is Draft. API contracts are intentionally deferred to Epic 14.3.

Requires confirmation

Final service ownership, authorization hardening, cross-service identity mapping, production routing, lifecycle reconciliation, operational objectives, retention, and test ownership require confirmation.

Source References

• microservices/src/recruitment-service/Program.cs
• microservices/src/recruitment-service/Application/Commands/OnboardingCommands.cs
• microservices/src/recruitment-service/Infrastructure/RecruitmentDbContext.cs
• Controllers/RecruitmentController.cs
• Controllers/HrOperationsController.cs
• microservices/src/gateway-api/Program.cs
• UI/salary-ui/apps/client-hrms-portal/src/pages/hr/RecruitmentOnboardingPage.tsx
• UI/salary-ui/apps/client-hrms-portal/src/pages/hr/HrOperationsPage.tsx

Related Articles

• Onboarding & Offboarding
• Architecture overview

See Also

• Technical limitations
• Technical source map

Keywords

• Onboarding technical architecture
• Offboarding implementation
• Transitional lifecycle

Revision Information

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