Rhythm 2.0 Specifications

Appearance

WF-PFM-NOT-014Compose a record-owned template across services

Markdown

WF-PFM-NOT-014

Compose a record-owned template across services

Markdown
  • DocumentDraft
  • ImplementationObserved

Planning

Implements
CAP-PFM-NOT-016

KindWorkflowProduct areaPlatformModuleStaff Notifications and Association CommunicationsRevision1

Read atservices-platform ad3f6a65react-console baf6dae3

Compose a record-owned template across services ​

What It Does ​

An owning record creates, updates or clears its e-mail template setting.

The Flow ​

When Something Fails ​

The hop rows identify each retry boundary, any state left behind and the available observer. Identical merged content retains its publication, and repeated clear retains archived history. The active-owner uniqueness constraint coordinates first creation; owner and template saves cross independent commit boundaries.

Open Design Questions ​

The documented owner pattern validates first and compensates after a later template-save failure.

Controls

38 controls apply, from the corpus control catalogue.

TC-AVL-004 TC-AVL-005 TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 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-004 TC-IAM-005 TC-IAM-006 TC-LOG-002 TC-LOG-003 TC-LOG-004 TC-LOG-005 TC-MON-001 TC-PI-001 TC-PI-002 TC-PI-003 TC-PI-004 TC-PI-005 TC-PRV-001 TC-PRV-002 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-TEN-004 TC-VEN-001 TC-VEN-002 TC-VEN-003

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