Skip to main content

Notification Boundary Operations

Purpose​

Sets accurate expectations for missing Recruitment notifications.

Confirmed implementation​

Recruitment produces events, but Notification Service has no Recruitment resolver mapping and no confirmed Recruitment subscription. Publication does not prove notification intent or delivery.

Safe operational guidance​

Confirm originating business state and outbox publication, then establish whether an approved notification path exists outside inspected source. Do not repeatedly trigger business actions.

Signals and evidence​

Recruitment state changes and an outbox message may exist while no notification evidence exists.

Risks and escalation​

Consumer ownership, templates, recipients, channels, retries, delivery evidence, and guarantees are Not implemented or require confirmation.

Source References​

  • microservices/src/recruitment-service/Domain/Recruitment/RecruitmentDomainEvents.cs
  • microservices/src/notification-service/Application/EventNotificationResolver.cs
  • microservices/src/notification-service/Messaging/NotificationEventConsumer.cs

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