Rhythm 2.0 Specifications

Appearance

SVC-PFM-NOT-notificationsNotifications Service Module

Markdown

SVC-PFM-NOT-notifications

Notifications Service Module

Markdown
  • DocumentDraft
  • ImplementationPartially observed

KindService contractProduct areaPlatformModuleStaff Notifications and Association CommunicationsRevision1

Read atservices-platform ad3f6a65react-console baf6dae3

Notifications Service Module ​

What This Service Is For ​

Notifications lets applications announce changes to staff without choosing personal addresses or delivery channels. It maintains declarations, processed requests, personal inbox items and channel history.

Boundary ​

Communications owns association templates, recipient mail and sender protection; future staff e-mail uses that delivery service. Eligibility owns responsibility changes and their producer integration. Security and workspace lifecycle own provisioning and its alert trigger; operational system scope uses the shared workspace store. Security owns accounts, roles, evaluated permissions and support access grants used for audience and support reads. Eligibility owns the bell’s attention presentation and the legacy attention redirect. Integrations owns customer chat connections, while Operations supplies job execution and partition maintenance.

Operations in Words ​

Expose the API health and deployed build for operational checks.

Page through the caller’s inbox by newest item, optionally restricting personal view, category or time. Return unread totals for applicable, unarchived personal notices and their categories. Return the caller’s notice, channel results and saved audience explanation. Record that the caller has read a notice, preserving an existing read timestamp. Clear the read mark on a notice belonging to the caller. Move a personal notice out of ordinary inbox views and unread totals. Return a personal archived item to ordinary inbox views. Read all qualifying personal items, with optional category and creation-time cutoff. Submit a diagnostic notice addressed only to the signed-in person. Page through workspace notices with recipient facts and channel summaries. Inspect processed requests, including outcomes that produced no personal item. Inspect a processed request and the notices and deliveries it produced. Inspect one workspace notice with its audience and channel explanation. Inspect a delivery’s recorded events and related notice and request.

Accept a system publication through the same transactional submission helper used by producers. Submit withdrawal of a known request on behalf of a system caller. Inspect registered application definitions by application or status without returning content templates. Read customer notice history after the service establishes an active workspace access grant. Read customer request outcomes after the service establishes an active workspace access grant. Inspect exhausted channel deliveries across operational workspaces without a customer grant check. Create fresh delivery work for an exhausted failure under the HQ operator permission.

Deploy an application manifest into the notification registry after complete validation and retire omitted definitions. Accept IAM publication or cancellation through the notification request service. Write notification publish or cancel transport rows within the producer’s business transaction. Wake the workspace dispatcher after a producer commits notification work.

Events and Jobs ​

The request and chat consumers work behind the scheduled dispatcher. Nightly reconciliation uses a durable state machine to handle ambiguity, expiry, lost work and retention. Text delivery has queue infrastructure but no deployed consumer. Operational heartbeats and channel-failure alarms expose failures to staff.

Consistency Guarantees ​

Rollback removes the entry without separate compensation. Queue redelivery finds the request identity; failed processing consumes receives until dead-lettering. A minute schedule recovers a lost nudge, but cannot guarantee a one-minute delivery bound or recover every dead-lettered request. Already submitted messages cannot be recalled; retirement currently follows a weaker settlement path. A failed summary refresh has no general repair for final deliveries. Ambiguous sends fail without resubmission; missing queued work is recreated and expired undispatched entries are recorded.

Owns
DOM-PFM-NOT-003
Repository
services-platform

Controls

57 controls apply, from the corpus control catalogue.

TC-AVL-001 TC-AVL-004 TC-AVL-005 TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-AZ-005 TC-AZ-006 TC-CHG-001 TC-CHG-002 TC-CHG-003 TC-CHG-004 TC-CHG-005 TC-CHG-006 TC-CHG-007 TC-CRY-001 TC-CRY-002 TC-CRY-003 TC-CRY-004 TC-DAT-001 TC-DAT-002 TC-DAT-003 TC-DAT-004 TC-IAM-001 TC-IAM-002 TC-IAM-003 TC-IAM-004 TC-IAM-005 TC-IAM-006 TC-LOG-001 TC-LOG-002 TC-LOG-003 TC-LOG-004 TC-LOG-005 TC-MON-001 TC-MON-002 TC-MON-003 TC-PI-001 TC-PI-002 TC-PI-003 TC-PI-004 TC-PI-005 TC-PRV-001 TC-PRV-002 TC-PRV-004 TC-SEC-001 TC-SEC-002 TC-SEC-003 TC-SEC-004 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-TEN-004 TC-VEN-001 TC-VEN-002 TC-VEN-003

Does Not Own

  • Communications owns association templates, recipient mail and sender protection; future staff e-mail uses that delivery service.
  • Eligibility owns responsibility changes and their producer integration.
  • Security and workspace lifecycle own provisioning and its alert trigger; operational system scope uses the shared workspace store.
  • Security owns accounts, roles, evaluated permissions and support access grants used for audience and support reads.
  • Eligibility owns the bell’s attention presentation and the legacy attention redirect.
  • Integrations owns customer chat connections, while Operations supplies job execution and partition maintenance.

The Markdown files under specs/ in rhythmsoftware/rhythm-v2-docs are the canonical source of truth. This reader is a generated, read-only projection of them.

Rhythm Software