Skip to main content

Recruitment Compatibility and Cutover

Purpose​

Documents native, compatibility, public, and gateway boundaries for readiness reviews.

Confirmed implementation​

Native and compatibility/public surfaces operate over shared storage. Client operational pages largely use compatibility paths. Gateway owns routing. Smoke assets exist, but no full parity comparator/backfill/cutover tool exists.

Safe operational guidance​

Require approved route inventory, shadow/read comparison, sanitized smoke evidence, dependency checks, reconciliation, owner sign-off, and rollback readiness.

Signals and evidence​

Route reachability, compatible response shape, shared-record consistency, dependency outcomes, and smoke results.

Risks and escalation​

Exact toggles/values, rollout sequence, rollback switching, backfill, parity thresholds, approvals, and production ownership require confirmation.

Cutover and rollback evidence flow​

Source References​

  • microservices/src/recruitment-service/Api/RecruitmentCompatEndpoints.cs
  • microservices/src/recruitment-service/Application/Compatibility/CompatMapper.cs
  • microservices/src/gateway-api/appsettings.json
  • microservices/scripts/smoke-recruitment.ps1

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