Rhythm 2.0 Specifications

Appearance

SVC-PFM-TNL-committees-tenant-lifecycleCommittees Lifecycle Participants

Markdown

SVC-PFM-TNL-committees-tenant-lifecycle

Committees Lifecycle Participants

Markdown
  • DocumentDraft
  • ImplementationObserved

KindService contractProduct areaPlatformModuleWorkspace Lifecycle Across ApplicationsRevision1

Read atservices-committees 36129c24services-platform ad3f6a65

Committees Lifecycle Participants ​

What This Service Is For ​

Committees contributes five participants for committee records, authority, meetings, minutes and decisions. Construction applies starter committee types and positions; deletion and initial-load reset remove the declared records.

Boundary ​

Committees owns participant behavior, its starter ledger and governance records. Platform owns the execution plan. The interface has no export operation. Request-gate wiring is outside this module’s registered source scope.

Operations in Words ​

The manifest supplies dependencies that determine construction and reverse removal order. Only the committees participant applies starter defaults, with ledger entries; the remaining participants need no construction work. Purge removes children before parents, using a guarded database function for protected governance history. Reset calls the same purge implementation and does not restore starter configuration. Missing run identity becomes an empty value, and the dispatcher forwards batch sizes without bounding them.

Events and Jobs ​

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

Consistency Guarantees ​

Each removal batch commits within its workspace. Seed application records the default and ledger together. Removal also clears references on rows that can survive a partial batch; isolation and repeated execution need explicit proof.

Repository
services-committees

Controls

52 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-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