Skip to main content

Compatibility Events

Summary​

The compatibility application contains an integration outbox mechanism, but its interface and implementation are Expense-specific. No onboarding or offboarding lifecycle event is enqueued.

Audience​

Compatibility owners, integration engineers, QA, support, and architects.

Reference Content​

Compatibility onboarding creates local workforce/login state directly. Exit operations update local request, audit, workforce and access state. Exit approval invokes compatibility notification behavior after the save.

There are no verified compatibility CandidateOnboarded, CandidateJoined, EmployeeCreated, EmploymentStatusChanged, ExitApproved or AccessRevoked integration contracts.

Compatibility identifiers appear in extracted contracts where mappings provide them, but no migration event or dual-write contract reconciles extracted and compatibility lifecycles.

Classification: compatibility lifecycle event parity is Not implemented; coexistence is Transitional.

Requires confirmation​

Unless explicitly confirmed above, live delivery, consumer deployment, replay, reconciliation, retention, contract governance, monitoring and production ownership require confirmation.

Source References​

  • Controllers/RecruitmentController.cs
  • Controllers/HrOperationsController.cs
  • Services/IIntegrationEventOutbox.cs
  • Services/IntegrationEventOutbox.cs
  • Models/IntegrationOutboxMessage.cs

See Also​

Keywords​

  • Onboarding events
  • Offboarding events
  • Integration contracts

Revision Information​

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