--- id: FAS-PFM-NOT-04 title: Notification Review and Operator Support feature: FEAT-PFM-NOT-04 product_area: platform module: notifications revision: 1 status: proposed product_intent: proposed source_sha: services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1 react-console: baf6dae382d6f41dce976c7f848667ccc37e076f capabilities: - CAP-PFM-NOT-011 - CAP-PFM-NOT-012 scenarios: - id: FAS-PFM-NOT-04-01 title: An administrator follows a notice through its processing chain kind: behaviour exercises: - CAP-PFM-NOT-011 - CAP-PFM-NOT-010 relies_on: - ATS-PFM-NOT-011-03 - ATS-PFM-NOT-011-04 - ATS-PFM-NOT-010-04 preconditions: Prepare accepted and recipient-less requests in one workspace. steps: >- Filter History, open diagnostic detail and inspect request and channel explanations. expected: >- Staff connect delivered notices to their requests and can investigate an empty request without inventing a recipient. negative: false data_needs: >- Suite-owned records and repeat keys, named recipient identities and controlled provider outcomes. bound_to: [] provenance: proposed source: - >- rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-011-see-what-the-organization-told-whom.md#ATS-PFM-NOT-011-03 - >- rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-011-see-what-the-organization-told-whom.md#ATS-PFM-NOT-011-04 - >- rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-010-understand-why-i-was-told.md#ATS-PFM-NOT-010-04 - id: FAS-PFM-NOT-04-02 title: Workspace and support history share results under separate authority kind: interaction exercises: - CAP-PFM-NOT-011 - CAP-PFM-NOT-012 relies_on: - ATS-PFM-NOT-011-05 - ATS-PFM-NOT-012-02 preconditions: >- Use an administrator and HQ staff with an active grant for the same workspace. steps: 'Read both lists, compare them, remove the grant and repeat the HQ read.' expected: The granted lists agree; loss of the grant stops customer History access. negative: false data_needs: >- Suite-owned records and repeat keys, named recipient identities and controlled provider outcomes. bound_to: [] provenance: proposed source: - >- rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-011-see-what-the-organization-told-whom.md#ATS-PFM-NOT-011-05 - >- rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-012-support-a-customers-notifications-from-rhythm-hq.md#ATS-PFM-NOT-012-02 - id: FAS-PFM-NOT-04-03 title: Retry reopens only exhausted delivery work kind: lifecycle exercises: - CAP-PFM-NOT-012 - CAP-PFM-NOT-007 relies_on: - ATS-PFM-NOT-012-03 - ATS-PFM-NOT-007-04 preconditions: Retain exhausted and permanently refused deliveries. steps: Retry both from HQ and process the resulting work twice. expected: >- Only exhausted work returns to dispatch, and final redelivery does not repeat a completed send. negative: false data_needs: >- Suite-owned records and repeat keys, named recipient identities and controlled provider outcomes. bound_to: [] provenance: proposed source: - >- rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-012-support-a-customers-notifications-from-rhythm-hq.md#ATS-PFM-NOT-012-03 - >- 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-04 - id: FAS-PFM-NOT-04-04 title: Read-only personal access cannot become administrative review kind: permission exercises: - CAP-PFM-NOT-011 - CAP-PFM-NOT-012 relies_on: - ATS-PFM-NOT-011-01 - ATS-PFM-NOT-012-01 - ATS-PFM-NOT-012-02 preconditions: 'Use a clerk, a workspace administrator and an ungranted HQ account.' steps: Read History under each identity and inspect the granted support route. expected: >- Management and staff grant checks apply independently; personal authority alone is insufficient. negative: true data_needs: >- Suite-owned records and repeat keys, named recipient identities and controlled provider outcomes. bound_to: - TST-PFM-NOT-002 provenance: test source: - >- react-console:acceptance/notifications/playwright/journeys/history/NT-ACC-0100.spec.ts - id: FAS-PFM-NOT-04-05 title: Failed support access returns no customer records kind: regression exercises: - CAP-PFM-NOT-012 - CAP-PFM-NOT-011 relies_on: - ATS-PFM-NOT-012-02 - ATS-PFM-NOT-011-05 preconditions: An authorized HQ identity has an expired or mismatched grant. steps: >- Read customer History and request lists before and after granting the selected workspace. expected: >- The refused reads return no customer list; the granted read uses the same workspace filter. negative: false data_needs: >- Suite-owned records and repeat keys, named recipient identities and controlled provider outcomes. bound_to: [] provenance: proposed source: - >- rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-012-support-a-customers-notifications-from-rhythm-hq.md#ATS-PFM-NOT-012-02 - >- rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-011-see-what-the-organization-told-whom.md#ATS-PFM-NOT-011-05 evidence: - >- rhythm-v2-docs:specs/platform/notifications/planning/features/FEAT-PFM-NOT-04-notification-history-and-support.md - >- rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-011-see-what-the-organization-told-whom.md#ATS-PFM-NOT-011-03 - >- rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-011-see-what-the-organization-told-whom.md#ATS-PFM-NOT-011-04 - >- rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-010-understand-why-i-was-told.md#ATS-PFM-NOT-010-04 - >- rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-011-see-what-the-organization-told-whom.md#ATS-PFM-NOT-011-05 - >- rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-012-support-a-customers-notifications-from-rhythm-hq.md#ATS-PFM-NOT-012-02 - >- rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-012-support-a-customers-notifications-from-rhythm-hq.md#ATS-PFM-NOT-012-03 - >- 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-04 - >- react-console:acceptance/notifications/playwright/journeys/history/NT-ACC-0100.spec.ts - >- rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-012-support-a-customers-notifications-from-rhythm-hq.md#ATS-PFM-NOT-012-02 - >- rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-011-see-what-the-organization-told-whom.md#ATS-PFM-NOT-011-05 regression_record: - revision: 1 change: initial scenarios: - FAS-PFM-NOT-04-01 - FAS-PFM-NOT-04-02 - FAS-PFM-NOT-04-03 - FAS-PFM-NOT-04-04 - FAS-PFM-NOT-04-05 reason: >- Initial cumulative feature acceptance coverage from the pinned planning and design layers. --- # Notification Review and Operator Support: 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 both lists, compare them, remove the grant and repeat the HQ read. The granted lists agree; loss of the grant stops customer History access. The feature cases retain their prerequisite scenario references. A component test alone does not establish execution of the complete feature chain. ## Regression Record | Revision | Change | Scenario | Why | |---|---|---|---| | 1 | initial | All initial cases | Establish cumulative feature coverage and preserve its dependencies for later revisions. |