---
id: ADR-PFM-NOT-001
title: Notifications Is a Platform Module Beside Communications
product_area: platform
module: notifications
revision: 1
status: proposed
design_intent: confirmed
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: Platform hosts staff Notifications alongside Communications so shared identity and responsibility
  data can be read in process.
constrains:
- SVC-PFM-NOT-notifications
- SVC-PFM-NOT-communications
- DOM-PFM-NOT-003
- RESP-PFM
origin: D-01, Andrew 2026-10-21 17:15 ET, services-platform:docs/proposals/notifications/23-decisions.md#D-01.
  Where the capability lives
alternatives:
- option: A separate notifications macroservice
  why_not: A separate deployment would add network dependencies and lifecycle administration around a
    capability every application needs.
- option: Each module keeps sending its own e-mail
  why_not: Independent producer sending would duplicate recipient selection, content, deduplication and
    outcome history.
consequences:
- Platform can resolve accounts, authority and responsibility holders without a cross-service request.
- External producers use committed queue entries and invocation capabilities to reach shared delivery.
- One corpus module describes two implementation service modules and one responsibility boundary.
supersedes: []
evidence:
- 'services-platform at ad3f6a65: docs/proposals/notifications/23-decisions.md D-01; docs/notifications.md
  opening.'
---
# Notifications Is a Platform Module Beside Communications

## Context

Applications need a shared way to announce staff changes without rebuilding delivery for each producer.

## Decision

Platform hosts staff Notifications alongside Communications so shared identity and responsibility data can be read in process.

## Alternatives Considered

A separate deployment would add network dependencies and lifecycle administration around a capability every application needs. Independent producer sending would duplicate recipient selection, content, deduplication and outcome history.

## Consequences

Platform can resolve accounts, authority and responsibility holders without a cross-service request. External producers use committed queue entries and invocation capabilities to reach shared delivery. One corpus module describes two implementation service modules and one responsibility boundary.