---
id: ADR-PFM-NOT-016
title: No Notification or Communication Operation Is Published to Submissions
product_area: platform
module: notifications
revision: 1
status: proposed
design_intent: proposed
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: The examined notification and communication operations have no Submissions bindings and retain
  individual nonpublication reasons.
constrains:
- SVC-PFM-NOT-notifications
- SVC-PFM-NOT-communications
origin: R2-ARCH-002 v2.0, approved by Andrew 2026-10-22, services-platform:docs/standards/submission-compatible-operations.md#1.
  The rule (the classification of each operation is this draft's)
alternatives:
- option: Publish the communication request as a binding
  why_not: Publishing the mail primitive directly would move the form outcome outside its owning business
    domain.
consequences:
- Service operation rows expose their proposed publication classification for review.
- A business form that causes mail should use its domain’s intake and transactional communication submission.
supersedes: []
evidence:
- 'services-platform at ad3f6a65: docs/standards/submission-compatible-operations.md; both route files.'
---
# No Notification or Communication Operation Is Published to Submissions

## Context

Each business operation must expose a Submissions contract or explain why publication does not apply.

## Decision

The examined notification and communication operations have no Submissions bindings and retain individual nonpublication reasons.

## Alternatives Considered

Publishing the mail primitive directly would move the form outcome outside its owning business domain.

## Consequences

Service operation rows expose their proposed publication classification for review. A business form that causes mail should use its domain’s intake and transactional communication submission.