Rhythm 2.0 Specifications

Appearance

SVC-PFM-TNL-marketing-tenant-lifecycleMarketing Lifecycle Participant

Markdown

SVC-PFM-TNL-marketing-tenant-lifecycle

Marketing Lifecycle Participant

Markdown
  • DocumentDraft
  • ImplementationObserved

KindService contractProduct areaPlatformModuleWorkspace Lifecycle Across ApplicationsRevision1

Read atservices-marketing d071a159services-platform ad3f6a65

Marketing Lifecycle Participant ​

What This Service Is For ​

Marketing’s participant accounts for audience and list records, evaluations, count jobs and audience history. Construction needs no starter data; deletion and reset remove the declared resources.

Boundary ​

Marketing owns the participant and Marketing records. CRM owns consent and subscription records, while Platform controls lifecycle ordering. Marketing exposes no export operation. Availability-gate wiring is outside this module’s source scope.

Operations in Words ​

Description publishes a participant dependent on the workspace record. Provisioning does no work and readiness reports ready. Removal handles jobs, evaluations, audiences and list records before the guarded deletion of audience history. Reset uses that same removal operation. The dispatcher accepts either naming convention, defaults a missing run to an empty value and passes batch size through without a bound check.

Events and Jobs ​

The interface declares no business events. Platform invokes its five-minute lifecycle function for construction, reset and deletion.

Consistency Guarantees ​

Batches commit within the selected workspace and repeated removal continues toward empty resources. The protected audit deletion asserts the session workspace. Platform stores returned counts after the participant commits, leaving a separate accounting boundary.

Repository
services-marketing

Controls

53 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-PRV-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