Technical Limitations and Confirmation Register

Summary

The implementation is transitional: extracted Recruitment onboarding, compatibility routing, Employee integration, and event foundations coexist with monolith offboarding and incomplete cross-domain orchestration. The items below are evidence-based limitations, not claims about roadmap commitment.

Audience

Engineering, QA, support, security, architecture, and product owners.

Reference Content

Area	Verified limitation or concern	Status
Ownership	No standalone lifecycle coordinator; onboarding and offboarding have different owners and stores	Require confirmation
Consistency	No distributed transaction across Recruitment, Employee, events, projections, and HR Operations	Implemented boundary
Completion parity	Legacy and extracted completion have different profile and login side effects	Transitional
Authorization	Extracted authentication is registered, but required endpoint policies were not found	Security review required
Tenant access	One active-onboarding repository query bypasses global filters without explicit tenant predicate	Security review required
Profile completeness	Extracted completion does not fully map organization, manager, or location data	Implemented limitation
Login	Extracted Employee handoff does not provision login	Not implemented in this boundary
Checklist	No enforced onboarding/offboarding checklist dependency engine was found	Not implemented
Documents	Document completeness is not enforced by onboarding completion	Not implemented in inspected flow
Assets	Clearance query exists but is not invoked by exit processing	Not integrated
Attendance	Direct onboarding/employee lifecycle projection was not confirmed	Require confirmation
Notifications	Extracted onboarding events lack a verified notification resolver	Not integrated
Workflow	Feature-flagged Workflow behavior applies to requisition approval, not lifecycle orchestration	Not implemented for lifecycle
Health	Health signal does not prove dependency readiness	Foundation
Observability	No verified lifecycle SLO, backlog alert, or unified trace dashboard	Require confirmation
Testing	Smoke evidence exists; dedicated exit, unit, persistence, parity, security, and UI suites were not found	Coverage gap
Reconciliation	No automated cross-store or cross-service lifecycle reconciler was found	Not implemented
Compliance	Retention, archival, erasure, and regulatory controls are not established by inspected code	Require confirmation

Priority confirmation themes

1. Protect extracted endpoints and verify tenant isolation before expanding direct-service access.
2. Define one authoritative employee lifecycle identity and reconciliation model.
3. Establish completion parity or document intentional behavioral differences before compatibility cutover.
4. Decide whether asset, payroll, access, documents, and approvals are blocking workflow dependencies.
5. Add automated offboarding, failure-path, parity, and security evidence.

Source References

• microservices/src/recruitment-service/Program.cs
• microservices/src/recruitment-service/Api/Policies.cs
• microservices/src/recruitment-service/Infrastructure/Persistence.cs
• microservices/src/recruitment-service/Infrastructure/EmployeeServiceClient.cs
• microservices/src/recruitment-service/Application/Compatibility/CompatCommands.cs
• Controllers/HrOperationsController.cs
• microservices/src/notification-service/Application/EventNotificationResolver.cs
• microservices/src/asset-service/Application/Queries/AssetQueries.cs

Related Articles

• Architecture overview
• Compatibility and transition
• Testing architecture

See Also

• Authentication and tenant context
• Source map

Keywords

• Technical limitations
• Security review
• Reconciliation

Revision Information

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