Skip to main content

Gateway Event Boundaries

Summary​

Gateway selects and forwards compatibility or extracted routes. It does not publish, consume, enrich or persist onboarding/offboarding events.

Audience​

Gateway owners, integration engineers, QA, support, security, and architects.

Reference Content​

Route selection materially changes which persistence and event behavior is reached:

  • Extracted Recruitment can raise domain events and stage integration contracts.
  • Compatibility Recruitment/HR Operations does not emit verified lifecycle contracts.
  • Gateway itself adds no domain event, integration event or correlation mapping for this lifecycle.

Routing telemetry must not be interpreted as a business event. Changing a compatibility flag can change event availability without changing the client-facing operation.

Requires confirmation​

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

Source References​

  • microservices/src/gateway-api/Program.cs

See Also​

Keywords​

  • Onboarding events
  • Offboarding events
  • Integration contracts

Revision Information​

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