Rhythm 2.0 Specifications

Appearance

SVC-PFM-TNL-membership-tenant-lifecycleMembership Lifecycle Participants

Markdown

SVC-PFM-TNL-membership-tenant-lifecycle

Membership Lifecycle Participants

Markdown
  • DocumentDraft
  • ImplementationObserved

KindService contractProduct areaPlatformModuleWorkspace Lifecycle Across ApplicationsRevision1

Read atservices-membership 5994c270services-platform ad3f6a65

Membership Lifecycle Participants ​

What This Service Is For ​

Membership prepares relationship types and a daily status sweep, removes its declared records, resets imported data while retaining configuration and exports declared datasets. It also exposes initialization for existing workspaces.

Boundary ​

Membership owns its participants, configuration ledger and business records. Platform owns the orchestration plan. The Membership dispatcher has a separate context-factory contract and supports legacy field aliases. Request-gate wiring is outside the registered scope.

Operations in Words ​

Description reports participants and supported operations. Provisioning applies relationship defaults and ensures the sweep schedule; readiness checks those requirements. Purge removes dependent records before their parents, including protected versions through a guarded function. Reset dispatches participant-specific removal and retains configuration, schedules and the seed ledger. Initialization requests every seed set of the selected participant, while export writes a batch of one declared dataset.

Events and Jobs ​

The lifecycle interface declares no business events. Provisioning ensures a daily sweep schedule that Membership subsequently owns. Platform drives lifecycle calls through a five-minute function.

Consistency Guarantees ​

Removal commits before the caller records progress. Default application retains ledger evidence, while reset keeps the ledger instead of reapplying defaults. Protected version deletion requires the same workspace as the transaction.

Repository
services-membership

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