Rhythm 2.0 Specifications

Appearance

SVC-PFM-TNL-websites-tenant-lifecycleWebsites Lifecycle Participants

Markdown

SVC-PFM-TNL-websites-tenant-lifecycle

Websites Lifecycle Participants

Markdown
  • DocumentDraft
  • ImplementationPartially observed

KindService contractProduct areaPlatformModuleWorkspace Lifecycle Across ApplicationsRevision1

Read atservices-websites 5fc6823cservices-platform ad3f6a65

Websites Lifecycle Participants ​

What This Service Is For ​

Websites declares participants for content and Website Studio changes, but Platform does not currently include their work in its lifecycle executions. Content removal remains incomplete even if the integration is enabled.

Boundary ​

Websites owns the participant implementations and website records. Platform’s content switch is off, and its static manifest omits the changes participant. Websites exposes no reset operation. Its registered availability implementation reads workspace facts for a local gate.

Operations in Words ​

Description reports content and changes participants, neither of which needs construction work. Table purge operates in batches. CMS documents and media have no purge implementation, and their participant returns an empty inventory. The changes participant exports declared changes, while content export is deferred. The export dispatcher requires the configured staging bucket.

Events and Jobs ​

The interface declares no business events. The function reserves concurrency one with a four-minute timeout. Platform’s disabled integration keeps its lifecycle jobs from invoking Websites at the pinned revision.

Consistency Guarantees ​

Table removal commits within the selected workspace. Empty reported inventory does not prove CMS content or media was removed, because those resources are outside the implemented purge. Enabling the integration alone does not close that gap.

Repository
services-websites

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