---
id: ADR-PFM-ELG-016
title: >-
  Attention sends nothing itself; reminders go through Notifications and start
  off
product_area: platform
module: eligibility
revision: 1
status: proposed
design_intent: confirmed
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: >-
  Retain the approved Notifications boundary and administrator-enabled reminders
  as the product target, recording the current communications sender and
  automatic enabling as disagreements.
constrains:
  - DOM-PFM-ELG-005
  - SVC-PFM-ELG-attention
  - WF-PFM-ELG-017
  - WF-PFM-ELG-018
  - SCR-PFM-ELG-011
origin: >-
  Responsibilities and attention architecture D-10 (never automatic tasks or
  messages), approved 2026-10-18; PLAT-M16 change "use the notifications
  platform capability" and D2 (reminders off until an administrator turns them
  on), approved by Andrew 2026-10-21
alternatives:
  - option: Send attention email through a separate delivery path
    why_not: A separate path duplicates delivery preferences and history.
  - option: Enable reminders whenever an application declares them
    why_not: >-
      A declaration would opt organizations into messages without administrator
      action.
consequences:
  - The current sender and timing preferences need migration.
  - Declared reminder policies currently disagree with default-off approval.
  - >-
    Attention should retain reminder planning while Notifications owns delivery
    and preferences.
supersedes: []
evidence:
  - >-
    services-platform at ad3f6a6:
    docs/proposals/responsibilities-and-attention/16-decisions.md;
    docs/milestones/PLAT-M15-home-attention-and-responsibilities.md (Decisions)
  - >-
    services-platform at ad3f6a6: docs/milestones/PLAT-M16-attention-follow-up-
    and-tuning.md (Decisions); docs/milestones/plans/PLAT-M16-plan.md;
    services/reminders/send-reminders.ts
---
# Attention sends nothing itself; reminders go through Notifications and start off

## Context

The later approved scope puts message delivery and preferences in Notifications.

## Decision

Retain the approved Notifications boundary and administrator-enabled reminders as the product target, recording the current communications sender and automatic enabling as disagreements.

## Alternatives Considered

Send attention email through a separate delivery path: A separate path duplicates delivery preferences and history.

Enable reminders whenever an application declares them: A declaration would opt organizations into messages without administrator action.

## Consequences

The current sender and timing preferences need migration. Declared reminder policies currently disagree with default-off approval. Attention should retain reminder planning while Notifications owns delivery and preferences.