Rhythm 2.0 Specifications

Appearance

SVC-PFM-TNL-crm-tenant-lifecycleCRM Lifecycle Participants

Markdown

SVC-PFM-TNL-crm-tenant-lifecycle

CRM Lifecycle Participants

Markdown
  • DocumentDraft
  • ImplementationObserved

KindService contractProduct areaPlatformModuleWorkspace Lifecycle Across ApplicationsRevision1

Read atservices-crm a8d1364fservices-platform ad3f6a65

CRM Lifecycle Participants ​

What This Service Is For ​

CRM prepares its starter configuration, removes declared CRM resources, resets imported records and exports declared datasets. Deployment reconciliation also applies missing defaults to eligible existing workspaces.

Boundary ​

CRM owns its seven participants, ledger and reconciliation implementation; its business modules retain their records. Platform chooses when to invoke participants and in what order. CRM reads workspace lifecycle facts for its local availability gate and does not own those facts.

Operations in Words ​

Description publishes each participant’s resources, dependencies, seed sets and supported operations. Provisioning applies ledgered defaults, and readiness reports missing requirements. Purge and reset process bounded batches within the selected workspace, with guarded functions for protected histories. Reset preserves or reapplies configuration according to each participant’s classification. Export validates its request and writes one declared dataset batch. Reconciliation invokes initialization for enabled participants with seed sets across active, loading and failed-provisioning workspaces, including disabled ones.

Events and Jobs ​

The interface declares no business events, and removal transactions suppress change capture. Platform drives lifecycle calls through the function. A deployment custom resource requests baseline reconciliation after the release’s migrations and function update; unchanged resource properties do not cause another run.

Consistency Guarantees ​

Default records and seed ledger entries commit together. Each removal batch commits separately from Platform’s progress accounting, so recovery continues forward rather than rolling back completed batches. Reconciliation collects workspace failures while continuing with other workspaces and then reports failure to deployment. Applied defaults remain after stack rollback.

Repository
services-crm

Controls

56 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-DAT-005 TC-DAT-006 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-003 TC-PI-001 TC-PI-002 TC-PI-003 TC-PI-004 TC-PI-005 TC-PRV-001 TC-PRV-002 TC-SEC-001 TC-SEC-002 TC-SEC-003 TC-SEC-004 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-VEN-001 TC-VEN-002 TC-VEN-003

Does Not Own

  • Platform’s orchestration plan, integration switch and recorded workflow accounting.
  • System-owned workspace lifecycle facts.
  • Business record ownership, which remains with the application’s domain modules.

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