Rhythm 2.0 Specifications

Appearance

SVC-PFM-TNL-tenantsWorkspace Lifecycle Service (Platform)

Markdown

SVC-PFM-TNL-tenants

Workspace Lifecycle Service (Platform)

Markdown
  • DocumentDraft
  • ImplementationObserved

KindService contractProduct areaPlatformModuleWorkspace Lifecycle Across ApplicationsRevision1

Read atservices-platform ad3f6a65

Workspace Lifecycle Service (Platform) ​

What This Service Is For ​

Platform coordinates workspace construction, controlled initial loading, reset and deliberate removal. It retains the decisions and progress staff need to inspect and recover those operations. Its availability implementation evaluates lifecycle and business standing for gated workspace requests.

Boundary ​

Workspace administration retains ordinary customer and workspace records. Shared jobs own execution and reconciliation; Security owns authority; the Data Job Engine owns imports; export coordination owns packaging and delivery. Application lifecycle functions implement their participant work. Provider sending and identity concerns retain their existing service owners.

Operations in Words ​

Staff can request construction, inspect its attempt, retry failed construction and initialize an existing participant. Import authority opens loading, submits reset and reads reset progress; separate activation authority ends loading.

Deletion-request authority creates a decision and recovers stopped watcher or purge work. Hold authority pauses and releases reversible decisions; cancellation authority withdraws them. Deletion-reading authority exposes retained requests and their notices. Immediate removal is refused. The exact route permission and capability mappings remain in the structured operation rows.

Events and Jobs ​

Construction attempts publish keyed HQ outcome notifications and attempt requester messages. The reconciliation hook repairs stranded construction; it is an in-process callback rather than a business event. Four state machines perform construction, watching, purge and reset. Operator scripts inspect leftovers and disabled candidates or reapply ledger-recorded removal after restore. Notice failures feed an operations alarm. The reviewed lifecycle interface performs no model inference.

Consistency Guarantees ​

Normal admission and irreversible handoff commit their domain records with new job records before execution starts. Provisioning retry and deletion recovery have separate-commit gaps. Participant commits also precede result accounting, so repeated removal can converge while counts remain incomplete. Availability facts expire per process; HQ record routes outside the gate need their own safeguards.

Purge finalization is not one transaction: failure after workspace removal can prevent completion and ordinary retry. Completion also precedes the external ledger write, whose exhausted failure has no ordinary recovery route. Notice records prevent duplicate obligations but do not ensure one message or eventual delivery.

Owns
DOM-PFM-TNL-001DOM-PFM-TNL-002DOM-PFM-TNL-003DOM-PFM-TNL-004DOM-PFM-TNL-005
Repository
services-platform

Controls

56 controls apply, from the corpus control catalogue.

TC-AVL-001 TC-AVL-002 TC-AVL-003 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-DAT-007 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-002 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

  • Ordinary workspace records, administrative business standing and HQ browsing.
  • Customer and identity ownership, evaluated authority and standing staff grants.
  • Shared durable execution and reconciliation.
  • Import execution, uploads and Data Runs.
  • Whole-package export coordination and delivery.
  • Provider sender identity ownership and general communication delivery.
  • Application business records and participant implementations.

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