Rhythm 2.0 Specifications

Appearance

WF-PFM-SEC-007Suspend, reinstate, revoke or delete a membership

Markdown

WF-PFM-SEC-007

Suspend, reinstate, revoke or delete a membership

Markdown
  • DocumentDraft
  • ImplementationObserved

Planning

Implements
CAP-PFM-SEC-009, CAP-PFM-SEC-008, CAP-PFM-SEC-016

KindWorkflowProduct areaPlatformModuleSecurity, Customers and WorkspacesRevision1ExaminercodexExamined on2026-10-23

Read atservices-platform ad3f6a65react-console baf6dae3

Suspend, reinstate, revoke or delete a membership ​

What It Does ​

The workflow separates database authority from provider synchronization. Revocation and deletion persist queue work atomically with membership changes; suspension and reinstatement issue one provider call after commit.

The Flow ​

The diagram separates the relevant success, alternative and failure paths. The numbered hop rows retain the detailed authority checks, delegated work and retry limits.

When Something Fails ​

Fresh authorization observes membership changes. Cached decisions and signed contexts can lag within their expiry bounds, and provider removal can require dead-letter redrive. The console’s successful action message is not evidence that provider synchronization succeeded.

Repeated revocation retains its first timestamp. Removal work identifies pool and username; provider not-found is successful absence. Replayed consumer work converges, though a crash after provider success and before acknowledgement can repeat history. Dispatcher claims lapse for work not accepted by the queue.

Membership changes transact with related records and applicable lockout guards. Durable removal rows are written for revocation/deletion and dispatched across membership boundaries; suspension/reinstatement remain separate post-commit single attempts.

Open Design Questions ​

The recorded findings retain any stronger planning expectation, missing writer or unproved recovery path. Observed behavior does not approve those outstanding product choices.

Controls

55 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-CRY-001 TC-CRY-002 TC-CRY-003 TC-CRY-004 TC-DAT-001 TC-DAT-002 TC-DAT-003 TC-DAT-004 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-SEC-001 TC-SEC-002 TC-SEC-003 TC-SEC-004 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-TEN-004 TC-VEN-001 TC-VEN-002 TC-VEN-003

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