--- id: FAS-PFM-NOT-03 title: Personal Notification Workspace feature: FEAT-PFM-NOT-03 product_area: platform module: notifications revision: 1 status: proposed product_intent: proposed source_sha: services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1 react-console: baf6dae382d6f41dce976c7f848667ccc37e076f capabilities: - CAP-PFM-NOT-009 - CAP-PFM-NOT-010 - CAP-PFM-NOT-014 scenarios: - id: FAS-PFM-NOT-03-01 title: An assignment is actionable and understandable kind: behaviour exercises: - CAP-PFM-NOT-014 - CAP-PFM-NOT-009 - CAP-PFM-NOT-010 relies_on: - ATS-PFM-NOT-014-01 - ATS-PFM-NOT-009-08 - ATS-PFM-NOT-010-06 preconditions: >- Jane holds the receiving role and has authority for the responsibility destination. steps: >- Assign the responsibility, open the notice and inspect its selection explanation. expected: >- Jane reaches her responsibility and sees the producer explanation; opening updates the personal read state. 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-014-tell-staff-about-changes-to-their-own-responsibilities.md#ATS-PFM-NOT-014-01 - >- rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-009-work-through-my-own-notifications.md#ATS-PFM-NOT-009-08 - >- rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-010-understand-why-i-was-told.md#ATS-PFM-NOT-010-06 - id: FAS-PFM-NOT-03-02 title: Ending one scope leaves another scope available kind: interaction exercises: - CAP-PFM-NOT-014 - CAP-PFM-NOT-005 - CAP-PFM-NOT-009 relies_on: - ATS-PFM-NOT-014-03 - ATS-PFM-NOT-005-03 - ATS-PFM-NOT-009-04 preconditions: Jane receives assignment notices for two resource scopes. steps: End the first assignment and inspect both notices and unread results. expected: >- The ended scope becomes inapplicable while the other notice remains unread and applicable. 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-014-tell-staff-about-changes-to-their-own-responsibilities.md#ATS-PFM-NOT-014-03 - >- rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-005-fold-quick-repeats-into-one-notice.md#ATS-PFM-NOT-005-03 - >- rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-009-work-through-my-own-notifications.md#ATS-PFM-NOT-009-04 - id: FAS-PFM-NOT-03-03 title: Assignment ending preserves delivered history kind: lifecycle exercises: - CAP-PFM-NOT-014 - CAP-PFM-NOT-009 relies_on: - ATS-PFM-NOT-014-03 - ATS-PFM-NOT-009-05 - ATS-PFM-NOT-009-04 preconditions: Jane has a delivered unread assignment notice. steps: >- End the assignment, read the old item and inspect the ending item and total. expected: >- The old wording remains readable outside unread results; the ending announcement is a separate unread item. negative: false data_needs: >- Suite-owned records and repeat keys, named recipient identities and controlled provider outcomes. bound_to: - TST-PFM-NOT-008 provenance: test source: - >- react-console:acceptance/notifications/playwright/journeys/inbox/NT-ACC-0004.spec.ts - id: FAS-PFM-NOT-03-04 title: A colleague cannot organize or investigate a personal item kind: permission exercises: - CAP-PFM-NOT-009 - CAP-PFM-NOT-010 relies_on: - ATS-PFM-NOT-009-02 - ATS-PFM-NOT-010-01 preconditions: >- Jane and a colleague have personal access; the colleague lacks management authority. steps: >- The colleague lists, reads and marks Jane’s item and tries workspace History. expected: >- Jane’s item remains unchanged and neither personal detail nor administrator history exposes it to the colleague. 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-03-05 title: Responsibility screens and attention totals keep working kind: regression exercises: - CAP-PFM-NOT-009 - CAP-PFM-NOT-014 relies_on: - ATS-PFM-NOT-009-09 - ATS-PFM-NOT-014-01 preconditions: Use the assignment dialog and capture attention totals before the change. steps: >- Save an explicit assignment through the console and compare responsibility, notice and attention views. expected: >- The responsibility persists and its notice appears; attention totals retain their own meaning. negative: false data_needs: >- Suite-owned records and repeat keys, named recipient identities and controlled provider outcomes. bound_to: - TST-PFM-NOT-001 provenance: test source: - >- react-console:acceptance/notifications/playwright/journeys/cross-application/NT-ACC-0300.spec.ts evidence: - >- rhythm-v2-docs:specs/platform/notifications/planning/features/FEAT-PFM-NOT-03-notification-centre.md - >- rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-014-tell-staff-about-changes-to-their-own-responsibilities.md#ATS-PFM-NOT-014-01 - >- rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-009-work-through-my-own-notifications.md#ATS-PFM-NOT-009-08 - >- rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-010-understand-why-i-was-told.md#ATS-PFM-NOT-010-06 - >- rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-014-tell-staff-about-changes-to-their-own-responsibilities.md#ATS-PFM-NOT-014-03 - >- rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-005-fold-quick-repeats-into-one-notice.md#ATS-PFM-NOT-005-03 - >- rhythm-v2-docs:specs/platform/notifications/design/tests/ATS-PFM-NOT-009-work-through-my-own-notifications.md#ATS-PFM-NOT-009-04 - >- react-console:acceptance/notifications/playwright/journeys/inbox/NT-ACC-0004.spec.ts - >- react-console:acceptance/notifications/playwright/journeys/history/NT-ACC-0100.spec.ts - >- react-console:acceptance/notifications/playwright/journeys/cross-application/NT-ACC-0300.spec.ts regression_record: - revision: 1 change: initial scenarios: - FAS-PFM-NOT-03-01 - FAS-PFM-NOT-03-02 - FAS-PFM-NOT-03-03 - FAS-PFM-NOT-03-04 - FAS-PFM-NOT-03-05 reason: >- Initial cumulative feature acceptance coverage from the pinned planning and design layers. --- # Personal Notification Workspace: 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 End the first assignment and inspect both notices and unread results. The ended scope becomes inapplicable while the other notice remains unread and applicable. 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. |