Skip to main content

Recruitment Data Consistency and Reconciliation

Purpose​

Defines non-destructive evidence collection across native/compatibility and dependencies.

Confirmed implementation​

Native and compatibility surfaces share persistence but apply mappings and compatibility identifiers. Workflow, Employee, and Document cross service boundaries. Outbox publication has no confirmed consumers.

Safe operational guidance​

Compare supported reads, statuses, safe identifiers, audit/timeline, dependency outcomes, and outbox state. Escalate mismatches; do not edit tables, forge callbacks, or replay messages.

Signals and evidence​

Native/compatibility mismatch, Workflow terminal mismatch, Employee without persisted reference, document reference without content, candidate/application duplication, offer/onboarding mismatch, or processed event with no consumer effect.

Risks and escalation​

No formal reconciler, backfill tool, parity comparator, or approved repair procedure was found.

Source References​

  • microservices/src/recruitment-service/Infrastructure/RecruitmentDbContext.cs
  • microservices/src/recruitment-service/Application/Compatibility/CompatMapper.cs
  • microservices/src/recruitment-service/Application/Commands/OnboardingCommands.cs
  • microservices/src/recruitment-service/Application/Commands/RequisitionCommands.cs

Summary​

This Draft page summarizes source-backed Recruitment behavior and explicitly marks incomplete governance or implementation.

Audience​

Recruitment stakeholders, product, engineering, QA, support, operations, architecture, security, and implementation partners as applicable to this page.

Overview​

Use the source-backed sections above as the authoritative scope. Unsupported behavior remains Requires confirmation or Not implemented.

See Also​

Keywords​

  • Recruitment
  • Hiring lifecycle
  • Draft documentation

Revision Information​

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