Skip to main content

Compatibility Persistence

Audience​

Developers, QA and support engineers, data reviewers, implementation partners, solution architects, privacy reviewers and security reviewers.

Reference Content​

Summary​

Compatibility routing reaches an independent application context containing candidate-onboarding, workforce, user, task, notification and exit models. It is not a view over extracted service databases.

Parallel models​

Confirmed persistence behavior​

Compatibility Recruitment stores generic HR module records for candidate/offer behavior and a dedicated CandidateOnboarding model. Completion creates compatibility workforce/login records and can persist onboarding-related document, bank and compensation payloads in compatibility-owned fields. HR Operations stores ExitRequest and ExitRequestAuditLog in the same compatibility context.

Schema management​

The application context has no authored EF migration files or model snapshot. Startup uses a schema initializer with provider-aware compatibility logic and initial configuration/permission population. This documentation does not reproduce or run that logic.

Risks​

Route changes can redirect writes between independent models. No shadow write, backfill, canonical merge, drift detector or rollback-safe migration between compatibility and extracted stores was found.

Requires confirmation​

Unless explicitly confirmed above, production migration governance, rollback, reconciliation, retention, privacy, performance, concurrency and operational ownership require confirmation.

Source References​

  • Data/AppDbContext.cs
  • Data/DatabaseSchemaInitializer.cs
  • Controllers/RecruitmentController.cs

See Also​

Keywords​

  • Onboarding database
  • Offboarding database
  • Lifecycle persistence

Revision Information​

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