Rhythm 2.0 Specifications

Appearance

FAS-PFM-NOT-06Notification Delivery Configuration

Markdown

FAS-PFM-NOT-06

Notification Delivery Configuration

Markdown
  • DocumentProposed
  • Product intentProposed

Planning

Feature
FEAT-PFM-NOT-06
Capabilities
CAP-PFM-NOT-015

Product areaPlatformModuleStaff Notifications and Association CommunicationsRevision1

Read atservices-platform ad3f6a65react-console baf6dae3

Notification Delivery Configuration: Feature Acceptance Suite ​

What the Feature Must Do as a Whole ​

This suite follows the feature from its initial inputs through the outcomes people inspect. Its cases combine capability results so that a change at one stage is checked against the later stages that depend on it.

Interactions Between Capabilities ​

Process an occurrence and compare its rendered console notice with the stored settings. The current pipeline retains product wording and console delivery despite the stored future configuration.

The feature cases retain their prerequisite scenario references. A component test alone does not establish execution of the complete feature chain.

Regression Record ​

RevisionChangeScenarioWhy
1initialAll initial casesEstablish cumulative feature coverage and preserve its dependencies for later revisions.

Scenarios

5 scenarios proving FEAT-PFM-NOT-06 as a whole.

01 Stored delivery choices remain inspectable behaviour proposed
Exercises
CAP-PFM-NOT-015
Relies on
ATS-PFM-NOT-015-01 ATS-PFM-NOT-015-03 ATS-PFM-NOT-015-07
Preconditions
Use suite-owned recipients and workspace configuration.
Steps
Save valid choices and quiet-hour settings, then read personal and workspace records.
Expected
The saved versions and defaults remain available without activating additional delivery.
Data
Suite-owned records and repeat keys, named recipient identities and controlled provider outcomes.
Source
rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-015-let-the-organization-and-its-people-choose-how-they-hear.md#ATS-PFM-NOT-015-01,rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-015-let-the-organization-and-its-people-choose-how-they-hear.md#ATS-PFM-NOT-015-03,rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-015-let-the-organization-and-its-people-choose-how-they-hear.md#ATS-PFM-NOT-015-07
02 Dormant wording and channels do not alter current inbox output interaction proposed
Exercises
CAP-PFM-NOT-015 CAP-PFM-NOT-007 CAP-PFM-NOT-004
Relies on
ATS-PFM-NOT-015-05 ATS-PFM-NOT-015-04 ATS-PFM-NOT-007-01 ATS-PFM-NOT-004-01
Preconditions
Publish a valid wording override and store a disabled optional definition setting.
Steps
Process an occurrence and compare its rendered console notice with the stored settings.
Expected
The current pipeline retains product wording and console delivery despite the stored future configuration.
Data
Suite-owned records and repeat keys, named recipient identities and controlled provider outcomes.
Source
rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-015-let-the-organization-and-its-people-choose-how-they-hear.md#ATS-PFM-NOT-015-05,rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-015-let-the-organization-and-its-people-choose-how-they-hear.md#ATS-PFM-NOT-015-04,rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-007-deliver-each-notice-on-the-channels-it-may-use.md#ATS-PFM-NOT-007-01,rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-004-word-each-notice-for-the-person-who-receives-it.md#ATS-PFM-NOT-004-01
03 Digest settlement retains collected history lifecycle proposed
Exercises
CAP-PFM-NOT-015
Relies on
ATS-PFM-NOT-015-08 ATS-PFM-NOT-015-09 ATS-PFM-NOT-015-13
Preconditions
Use a stored channel identity, challenge and digest window; these have no current delivery worker.
Steps
Move the identity through activation and revocation, expire a challenge and close a collected digest window through persistence.
Expected
Terminal state remains terminal and retained records describe the stored lifecycle without claiming an active notification channel.
Data
Suite-owned records and repeat keys, named recipient identities and controlled provider outcomes.
Source
rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-015-let-the-organization-and-its-people-choose-how-they-hear.md#ATS-PFM-NOT-015-08,rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-015-let-the-organization-and-its-people-choose-how-they-hear.md#ATS-PFM-NOT-015-09
04 Storage stays within workspace and recipient boundaries permissionnegative proposed
Exercises
CAP-PFM-NOT-015 CAP-PFM-NOT-008
Relies on
ATS-PFM-NOT-015-02 ATS-PFM-NOT-008-08
Preconditions
Create settings for two recipients in two workspaces and use a workspace-scoped execution context.
Steps
Attempt foreign reads and writes and a stale replacement of local choices.
Expected
Foreign settings are unavailable and the refused update does not change local choices.
Data
Suite-owned records and repeat keys, named recipient identities and controlled provider outcomes.
Source
rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-015-let-the-organization-and-its-people-choose-how-they-hear.md#ATS-PFM-NOT-015-02,rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-008-keep-notifications-whole-when-part-of-the-pipeline-fails.md#ATS-PFM-NOT-008-08
05 Rejected configuration does not add audit history regression proposed
Exercises
CAP-PFM-NOT-015
Relies on
ATS-PFM-NOT-015-02 ATS-PFM-NOT-015-06
Preconditions
Capture the current version and audit history for each workspace configuration family.
Steps
Perform a valid update, then repeat with the stale version and compare history.
Expected
Only the accepted update adds its recorded before-and-after change.
Data
Suite-owned records and repeat keys, named recipient identities and controlled provider outcomes.
Source
rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-015-let-the-organization-and-its-people-choose-how-they-hear.md#ATS-PFM-NOT-015-02,rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-015-let-the-organization-and-its-people-choose-how-they-hear.md#ATS-PFM-NOT-015-06

The Markdown files under specs/ in rhythmsoftware/rhythm-v2-docs are the canonical source of truth. This reader is a generated, read-only projection of them.

Rhythm Software