---
id: ADR-PFM-NOT-011
title: Rhythm HQ Alerts Are Hard-Coded Slack Deliveries in a System Scope
product_area: platform
module: notifications
revision: 1
status: proposed
design_intent: confirmed
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: HQ operational alerts use code-defined Slack destinations through the notification pipeline
  in a reserved system workspace.
constrains:
- DOM-PFM-NOT-003
- SVC-PFM-NOT-notifications
- WF-PFM-NOT-006
- WF-PFM-NOT-001
origin: PLAT-M23 D1, Andrew 2026-10-21 18:05 ET, and D-12 (add a Rhythm-wide scope now), services-platform:docs/milestones/PLAT-M23-notifications-core-and-in-app.md#Decisions;
  the reserved system workspace itself is an implementation choice (FND-PFM-NOT-001)
alternatives:
- option: A static e-mail list as before
  why_not: The recorded HQ choice replaces the previous static mail distribution.
- option: A workspace-less notice table
  why_not: A separate workspace-free store adds special policies and routes, though the chosen reserved
    workspace remains disputed.
- option: Customer-style Slack connections through integrations
  why_not: Customer connection setup would make operational alerts depend on configurable customer infrastructure.
consequences:
- Only system-scoped notices omit a personal recipient.
- The reserved workspace participates in operational history and retention.
- A separate system publication helper compensates for the ordinary producer library’s audience restriction.
supersedes: []
evidence:
- 'services-platform at ad3f6a65: docs/notifications.md §10; modules/notifications/services/{channels/slack-system,system-scope,requests/publish-system-notification}.ts.'
---
# Rhythm HQ Alerts Are Hard-Coded Slack Deliveries in a System Scope

## Context

Rhythm operations needs provisioning alerts independent of customer channel configuration.

## Decision

HQ operational alerts use code-defined Slack destinations through the notification pipeline in a reserved system workspace.

## Alternatives Considered

The recorded HQ choice replaces the previous static mail distribution. A separate workspace-free store adds special policies and routes, though the chosen reserved workspace remains disputed. Customer connection setup would make operational alerts depend on configurable customer infrastructure.

## Consequences

Only system-scoped notices omit a personal recipient. The reserved workspace participates in operational history and retention. A separate system publication helper compensates for the ordinary producer library’s audience restriction.