Recruitment Business Rules
Summary
These rules are enforced by the inspected domain and command code; organizational policy not represented in source is excluded.
Audience
Recruitment operations, hiring stakeholders, product, engineering, QA, support, and architecture teams. Candidate-facing behavior is identified explicitly.
Overview
These rules are enforced by the inspected domain and command code; organizational policy not represented in source is excluded.
Confirmed rules
| Area | Rule |
|---|---|
| Requisition | Requires title; valid range; rejection reason; workflow-managed decisions use Workflow |
| Opening | Requires title; public application requires Open; count is at least one |
| Application | Requires name and email or phone; duplicate contact application to the same opening is refused |
| Candidate | Stage changes append history; notes require content |
| Interview | Scheduling requires an eligible candidate stage; feedback recommendation is Selected, Rejected, or Hold |
| Offer | Creation requires a candidate and generates a letter reference; terminal guards vary by command |
| Onboarding | Requires Accepted offer; active record is reused; Completed is terminal |
| Employee handoff | Employee provisioning must succeed before completion and joined events |
Governance gaps
No complete endpoint permission model, hiring approval matrix, compensation threshold policy, candidate owner model, opening-limit enforcement, or data-retention policy is implemented.
Requires confirmation
Formal ownership, production policy, authorization parity, and approved operating procedures require confirmation.
Source References
microservices/src/recruitment-service/Domain/Common/Enums.csmicroservices/src/recruitment-service/Domain/Recruitmentmicroservices/src/recruitment-service/Application/Commands
Related Articles
See Also
Keywords
- Recruitment
- Hiring lifecycle
- Business Rules
Revision Information
- Status: Draft
- Last reviewed: 2026-07-16
- Review cycle: Quarterly