Rhythm 2.0 Specifications

Appearance

WF-CRM-ACT-004Claim and release shared work

Markdown

WF-CRM-ACT-004

Claim and release shared work

Markdown
  • DocumentDraft
  • ImplementationObserved

Planning

Implements
CAP-CRM-ACT-012, CAP-CRM-ACT-013, CAP-CRM-ACT-015

KindWorkflowProduct areaCRMModuleActivities, Follow-ups and Task WorkRevision1

Read atservices-crm a8d1364freact-console baf6dae3

Claim and release shared work ​

What It Does ​

Shared work is taken through a conditional assignment rather than a preliminary availability read. Queue and role-only claims have distinct authorization paths. Release clears the holder while preserving the shared route and queue arrival where present.

The Flow ​

The numbered hops specify the request, persistence and integration boundaries in order. Each hop identifies its evidence anchor, synchronization seam and observable failure outcome. Branches distinguish optional and delegated paths.

When Something Fails ​

A lost race leaves the winner’s assignment intact and returns a conflict. The console simplifies claim conflicts and can hide the service’s actual lock or lifecycle reason. Role lookup and enabled attention failures also prevent claim commitment, so successful arbitration alone is not a guarantee of a committed winner.

Open Design Questions ​

Role-offer discovery in the console remains unresolved. Platform’s actual security implementation is outside these source pins, and inactive queue behavior still needs its planning decision.

Controls

26 controls apply, from the corpus control catalogue.

TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-AZ-006 TC-DAT-001 TC-DAT-002 TC-DAT-003 TC-IAM-001 TC-IAM-005 TC-IAM-006 TC-LOG-001 TC-LOG-002 TC-LOG-003 TC-LOG-004 TC-LOG-005 TC-PI-001 TC-PI-002 TC-PI-003 TC-PI-005 TC-PRV-001 TC-PRV-002 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-TEN-004

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