Skip to main content

Value Conversions and Owned Values

Audience​

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

Reference Content​

Summary​

Enum-to-string conversions and owned value mappings preserve readable domain semantics while coupling storage compatibility to domain evolution.

Confirmed conversions​

  • Recruitment Candidate stage and compensation-approval state use string storage.
  • Recruitment Offer and Onboarding statuses use string storage.
  • Employee status uses string storage.
  • Candidate name and Offer compensation are owned values.
  • Employee employment is an owned value.

Evolution considerations​

Renaming an enum member can make existing values unreadable without a data transition. Adding values requires all readers to tolerate them. Owned-value changes belong to the owner's migration and retention boundary.

Privacy​

Owned compensation, employment and name details contain sensitive data. Their structural presence is documented; values, precision details and physical columns are not.

Open conversion questions​

Backward-compatible enum evolution, unknown-value handling, encryption and field-level masking policies were not established by the mappings.

Requires confirmation​

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

Source References​

  • microservices/src/recruitment-service/Infrastructure/RecruitmentDbContext.cs
  • microservices/src/employee-service/Infrastructure/EmployeeDbContext.cs
  • Data/AppDbContext.cs

See Also​

Keywords​

  • Onboarding database
  • Offboarding database
  • Lifecycle persistence

Revision Information​

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