Rhythm 2.0 Specifications

Appearance

FAS-PFM-NOT-02Staff Notification Processing

Markdown

FAS-PFM-NOT-02

Staff Notification Processing

Markdown
  • DocumentProposed
  • Product intentProposed

Planning

Feature
FEAT-PFM-NOT-02
Capabilities
CAP-PFM-NOT-002, CAP-PFM-NOT-003, CAP-PFM-NOT-004, CAP-PFM-NOT-005, CAP-PFM-NOT-006, CAP-PFM-NOT-007, CAP-PFM-NOT-008

Product areaPlatformModuleStaff Notifications and Association CommunicationsRevision1

Read atservices-platform ad3f6a65react-console baf6dae3

Staff Notification Processing: 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 ​

Read the notice, publish another contribution, withdraw the earlier contributions and inspect applicable unread items. Later work has a fresh item; remaining contributions stay visible until their own withdrawal.

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-02 as a whole.

01 A committed event reaches its eligible recipient behaviour proposed
Exercises
CAP-PFM-NOT-002 CAP-PFM-NOT-003 CAP-PFM-NOT-004 CAP-PFM-NOT-007
Relies on
ATS-PFM-NOT-002-01 ATS-PFM-NOT-003-02 ATS-PFM-NOT-004-01 ATS-PFM-NOT-007-01
Preconditions
A current responsibility holder has a locale distinct from the producer.
Steps
Commit an occurrence, resolve the current holder and inspect the rendered console delivery.
Expected
The committed event reaches the current holder with localized wording and immediate console 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-002-tell-people-that-something-happened-with-one-call.md#ATS-PFM-NOT-002-01,rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-003-reach-the-right-people-and-only-people-of-the-organization.md#ATS-PFM-NOT-003-02,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,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
02 Reading and withdrawal change folding eligibility interaction proposed
Exercises
CAP-PFM-NOT-005 CAP-PFM-NOT-006
Relies on
ATS-PFM-NOT-005-02 ATS-PFM-NOT-005-06 ATS-PFM-NOT-006-02
Preconditions
Jane has a folded notice with two open contributions.
Steps
Read the notice, publish another contribution, withdraw the earlier contributions and inspect applicable unread items.
Expected
Later work has a fresh item; remaining contributions stay visible until their own withdrawal.
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-005-fold-quick-repeats-into-one-notice.md#ATS-PFM-NOT-005-02,rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-005-fold-quick-repeats-into-one-notice.md#ATS-PFM-NOT-005-06,rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-006-withdraw-or-expire-a-notice-that-no-longer-applies.md#ATS-PFM-NOT-006-02
03 Withdrawal and expiry stop pending work across the pipeline lifecycle proposed
Exercises
CAP-PFM-NOT-006 CAP-PFM-NOT-008
Relies on
ATS-PFM-NOT-006-01 ATS-PFM-NOT-006-03 ATS-PFM-NOT-006-07 ATS-PFM-NOT-008-04
Preconditions
Prepare delayed, accepted and stale requests with both unsent and sent channels.
Steps
Withdraw delayed work, withdraw accepted work and run expiry reconciliation.
Expected
No stopped work initiates a new send, while previously sent history stays available.
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-006-withdraw-or-expire-a-notice-that-no-longer-applies.md#ATS-PFM-NOT-006-01,rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-006-withdraw-or-expire-a-notice-that-no-longer-applies.md#ATS-PFM-NOT-006-03,rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-006-withdraw-or-expire-a-notice-that-no-longer-applies.md#ATS-PFM-NOT-006-07,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-04
04 Publication and audience selection enforce distinct boundaries permissionnegative proposed
Exercises
CAP-PFM-NOT-002 CAP-PFM-NOT-003
Relies on
ATS-PFM-NOT-002-02 ATS-PFM-NOT-002-06 ATS-PFM-NOT-003-07
Preconditions
Use a console account, an authorized system caller and a foreign-customer audience entry.
Steps
Attempt publication with both callers, then process the authorized request containing the foreign candidate.
Expected
The console submission is refused; the foreign candidate receives no item and the processed request retains its exclusion.
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-002-tell-people-that-something-happened-with-one-call.md#ATS-PFM-NOT-002-02,rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-002-tell-people-that-something-happened-with-one-call.md#ATS-PFM-NOT-002-06,rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-003-reach-the-right-people-and-only-people-of-the-organization.md#ATS-PFM-NOT-003-07
05 Lost acknowledgement does not duplicate recipient work regression proposed
Exercises
CAP-PFM-NOT-002 CAP-PFM-NOT-008 CAP-PFM-NOT-005
Relies on
ATS-PFM-NOT-002-03 ATS-PFM-NOT-008-02 ATS-PFM-NOT-008-03 ATS-PFM-NOT-005-07
Preconditions
Retain a committed queue entry after its first acknowledgement is lost.
Steps
Recover dispatch, process both queue copies and repeat the occurrence.
Expected
Recipient work remains unique through replay and the request identity remains stable.
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-002-tell-people-that-something-happened-with-one-call.md#ATS-PFM-NOT-002-03,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-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-03,rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-005-fold-quick-repeats-into-one-notice.md#ATS-PFM-NOT-005-07

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