MOD-PFM-NOT

Staff Notifications and Association Communications Design

How this module will be built: 82 design artifacts, by kind. Design makes the technical choices once, reviewably, and citable by everything they constrain.

42Draft
40Proposed

Domain Objects 3

State Models 15

Workflows 16

Service Contracts 2

Screen Contracts 6

Decision Records 20

ADR-PFM-NOT-001Notifications Is a Platform Module Beside CommunicationsProposed
ADR-PFM-NOT-002Staff Notices and Association E-mail Are Separate ModelsProposed
ADR-PFM-NOT-003Producers Publish Inside Their Own Transaction Through an Insert-Only RoleProposed
ADR-PFM-NOT-004The Queue Holds Only Work and SQS Owns Every RetryProposed
ADR-PFM-NOT-005A Submission Is Validated Whole and Travels CompleteProposed
ADR-PFM-NOT-006The Request Object Is Written Inside the Caller's TransactionProposed
ADR-PFM-NOT-007Definitions Are Registered at Deploy and Retired, Never DeletedProposed
ADR-PFM-NOT-008Audiences Resolve at Processing, Inside the Workspace, Capped at Two HundredProposed
ADR-PFM-NOT-009Withdrawal Ends Unsent Work and Never Recalls What LeftProposed
ADR-PFM-NOT-010An Uncertain Hand-off Waits Out a Fifteen-Minute WindowProposed
ADR-PFM-NOT-011Rhythm HQ Alerts Are Hard-Coded Slack Deliveries in a System ScopeProposed
ADR-PFM-NOT-012Console, E-mail and Text Are Native; Customer Chat Goes Through IntegrationsProposed
ADR-PFM-NOT-013Preferences and Workspace Settings Are Stored but Not Applied YetProposed
ADR-PFM-NOT-014The Person Is Always the Signed Caller; Support Reads Need a GrantProposed
ADR-PFM-NOT-015Notification and Communication Records Carry No Custom FieldsProposed
ADR-PFM-NOT-016No Notification or Communication Operation Is Published to SubmissionsProposed
ADR-PFM-NOT-017Dispatch, Provider Delivery and Engagement Are Separate FactsProposed
ADR-PFM-NOT-018A Record Owns Its Template and Composes It Through Its Own APIProposed
ADR-PFM-NOT-019Three Rendering Modes Decide Who Supplies the ContentProposed
ADR-PFM-NOT-020Purpose-Classified Lanes Keep Transactional Mail Ahead of Bulk MailProposed

Domain Objects 3

State Models 15

Workflows 16

Service Contracts 2

Screen Contracts 6

Decision Records 20

Capability Test Specifications 20