SpecificationsStaff Notifications and Association Communications
20 acceptance test sets for MOD-PFM-NOT, one per capability, holding 212 scenarios — 178 of them already bound to an existing test. A scenario names the rules and journey assertions it proves; it never restates them.
| Acceptance test set | Proves capability | Scenarios | Bound | Negative | Levels | Status |
|---|---|---|---|---|---|---|
ATS-PFM-NOT-001 | Declare application notification types | 15 | 13 | 9 | 12 api · 3 unit | Proposed |
| Acceptance test set | Proves capability | Scenarios | Bound | Negative | Levels | Status |
|---|---|---|---|---|---|---|
ATS-PFM-NOT-002 | Publish a notification with its business change | 9 | 8 | 5 | 9 api | Proposed |
ATS-PFM-NOT-003 | Select eligible notification recipients | 9 | 8 | 4 | 2 unit · 7 api | Proposed |
ATS-PFM-NOT-004 | Render recipient-specific notification content | 5 | 4 | 0 | 2 unit · 1 browser · 2 api | Proposed |
ATS-PFM-NOT-005 | Combine repeated events into one notice | 10 | 8 | 0 | 10 api | Proposed |
ATS-PFM-NOT-006 | Remove notices that have become stale | 10 | 9 | 3 | 10 api | Proposed |
ATS-PFM-NOT-007 | Route and send notification deliveries | 10 | 9 | 2 | 7 api · 3 unit | Proposed |
ATS-PFM-NOT-008 | Recover notification processing and retain its history | 11 | 8 | 0 | 9 api · 2 unit | Proposed |
| Acceptance test set | Proves capability | Scenarios | Bound | Negative | Levels | Status |
|---|---|---|---|---|---|---|
ATS-PFM-NOT-009 | Manage a personal notification inbox | 10 | 9 | 2 | 7 api · 3 browser | Proposed |
ATS-PFM-NOT-010 | Explain notification selection and delivery | 7 | 6 | 1 | 4 api · 1 unit · 2 browser | Proposed |
ATS-PFM-NOT-014 | Announce explicit responsibility changes | 7 | 2 | 0 | 7 api | Proposed |
| Acceptance test set | Proves capability | Scenarios | Bound | Negative | Levels | Status |
|---|---|---|---|---|---|---|
ATS-PFM-NOT-011 | Review workspace notification activity | 7 | 6 | 2 | 5 api · 2 browser | Proposed |
ATS-PFM-NOT-012 | Investigate and retry notifications from HQ | 6 | 4 | 3 | 1 unit · 5 api | Proposed |
| Acceptance test set | Proves capability | Scenarios | Bound | Negative | Levels | Status |
|---|---|---|---|---|---|---|
ATS-PFM-NOT-013 | Send operational alerts to Rhythm HQ | 11 | 10 | 3 | 7 api · 4 unit | Proposed |
| Acceptance test set | Proves capability | Scenarios | Bound | Negative | Levels | Status |
|---|---|---|---|---|---|---|
ATS-PFM-NOT-015 | Store notification preferences and channel configuration | 13 | 10 | 9 | 13 api | Proposed |
| Acceptance test set | Proves capability | Scenarios | Bound | Negative | Levels | Status |
|---|---|---|---|---|---|---|
ATS-PFM-NOT-016 | Author and publish association e-mail content | 18 | 17 | 9 | 15 api · 2 browser · 1 unit | Proposed |
ATS-PFM-NOT-017 | Submit association communication requests | 15 | 13 | 9 | 15 api | Proposed |
ATS-PFM-NOT-018 | Send association e-mail with retry and capacity control | 15 | 14 | 5 | 13 api · 2 unit | Proposed |
ATS-PFM-NOT-019 | Inspect communication outcomes and provider feedback | 9 | 8 | 3 | 9 api | Proposed |
ATS-PFM-NOT-020 | Apply recipient protection and sender verification | 15 | 12 | 8 | 15 api | Proposed |