--- id: JNY-PFM-NOT-003 title: Investigate recipient and empty-request history feature: FEAT-PFM-NOT-04 product_area: platform module: notifications revision: 1 status: draft product_intent: confirmed implementation_evidence: observed supersedes: - NT-ACC-0100 - NT-ACC-0101 - NT-ACC-0202 - NT-ACC-0203 source_sha: services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1 react-console: baf6dae382d6f41dce976c7f848667ccc37e076f actor: ACT-PFM-028 goal: >- Determine which staff received a notice, inspect its delivery explanation and identify requests that produced no items. capabilities: - CAP-PFM-NOT-011 - CAP-PFM-NOT-010 - CAP-PFM-NOT-003 - CAP-PFM-NOT-007 screens: - '/console/{tenantId}/settings/notifications' steps: - 'n': 1 surface: '/console/{tenantId}/settings/notifications' action: The administrator visits notification History in Settings. capability: CAP-PFM-NOT-011 expected: >- Rows list recipients, notification types, times and states in descending time order. provenance: test source: >- react-console:acceptance/notifications/playwright/journeys/history/NT-ACC-0100.spec.ts#NT-ACC-0100 - 'n': 2 surface: listNotificationHistory action: The administrator filters the recipient picker to Jane. capability: CAP-PFM-NOT-011 expected: History retains Jane's rows only. provenance: test source: >- react-console:acceptance/notifications/playwright/journeys/history/NT-ACC-0101.spec.ts#NT-ACC-0101 - 'n': 3 surface: getNotificationRequest action: The administrator opens an item's diagnostic chain. capability: CAP-PFM-NOT-011 expected: >- Detail links the request, recipient explanation and deliveries; intended unused e-mail wording includes its future milestone. provenance: test source: >- react-console:acceptance/notifications/playwright/journeys/history/NT-ACC-0101.spec.ts#NT-ACC-0101 - 'n': 4 surface: listNotificationRequests action: The administrator selects Requests. capability: CAP-PFM-NOT-003 expected: >- An outsider-audience request shows isolation refusal, and a two-hundred-and-one-person audience shows invalidity. provenance: test source: >- react-console:acceptance/notifications/playwright/journeys/pipeline/NT-ACC-0202.spec.ts#NT-ACC-0202 alternates: - from_step: 4 condition: The administrator selects an outcome filter in Requests. path: The list returns only that outcome in descending time order. outcome: Invalid requests can be located through their outcome filter. provenance: test source: >- services-platform:modules/notifications/tests/e2e/notifications.e2e.spec.js#narrows by outcome, definition and since, newest first, and pages by keyset failures: - from_step: 1 condition: >- A staff caller lacking notification-management permission attempts History. path: History and its diagnostic operations deny access. outcome: No workspace history content is returned. provenance: test source: >- services-platform:modules/notifications/tests/e2e/notifications.e2e.spec.js#refuses History and the chain to a caller with only platform.notifications.use - from_step: 3 condition: The delivery table presents an unused channel. path: >- Its current wording omits the future milestone despite displaying the reason. outcome: The pinned handoff retains this known defect. provenance: documented source: 'services-platform:docs/forge-handoff/notifications.md#D. Current state' rules_in_play: - BR-CAP-PFM-NOT-011-01 - BR-CAP-PFM-NOT-011-02 - BR-CAP-PFM-NOT-011-03 - BR-CAP-PFM-NOT-011-04 - BR-CAP-PFM-NOT-011-06 - BR-CAP-PFM-NOT-011-08 - BR-CAP-PFM-NOT-003-06 - BR-CAP-PFM-NOT-003-07 - BR-CAP-PFM-NOT-007-02 assertions: - id: AS-JNY-PFM-NOT-003-01 statement: >- History identifies Jane and the item's type, time and state without exposing another workspace's activity. provenance: test source: >- react-console:acceptance/notifications/playwright/journeys/history/NT-ACC-0100.spec.ts#NT-ACC-0100 - id: AS-JNY-PFM-NOT-003-02 statement: Diagnostic detail explains each unused channel. provenance: test source: >- react-console:acceptance/notifications/playwright/journeys/history/NT-ACC-0101.spec.ts#NT-ACC-0101 - id: AS-JNY-PFM-NOT-003-03 statement: >- Requests producing no notices retain their outcome and explanation in the list. provenance: test source: >- react-console:acceptance/notifications/playwright/journeys/pipeline/NT-ACC-0202.spec.ts#NT-ACC-0202 e2e_policy: required e2e_reason: >- Recipient filtering, request selection and diagnostic navigation are console behavior, and browser acceptance exposes the outstanding delivery-explanation defect. evidence: - >- Pinned evidence inventory 1: react-console:acceptance/notifications/playwright/journeys/history/NT-ACC-0100.spec.ts; react-console:acceptance/notifications/playwright/journeys/history/NT-ACC-0101.spec.ts; react-console:acceptance/notifications/playwright/journeys/pipeline/NT-ACC-0202.spec.ts; services-platform:modules/notifications/tests/e2e/notifications.e2e.spec.js; services-platform:docs/forge-handoff/notifications.md; services-platform:docs/milestones/plans/PLAT-M23-plan.humanized.md intent_sources: - 'services-platform:docs/milestones/plans/PLAT-M23-plan.humanized.md#2. Scope' --- # Investigate recipient and empty-request history ## Story Determine which staff received a notice, inspect its delivery explanation and identify requests that produced no items. The administrator moves from recipient activity to the underlying request and channel records. Requests without notices remain inspectable. The intended milestone explanation in the delivery table has a recorded implementation defect. ## Verification Boundary The structured steps and assertions carry their own provenance and sources. Test references describe inspected assertions at the pinned commits; this examination does not claim a fresh provider or browser execution.