Rhythm 2.0 Specifications

Appearance

WF-CRM-ACT-003Write a task and keep its overdue item in step

Markdown

WF-CRM-ACT-003

Write a task and keep its overdue item in step

Markdown
  • DocumentDraft
  • ImplementationObserved

Planning

Implements
CAP-CRM-ACT-010, CAP-CRM-ACT-011, CAP-CRM-ACT-012, CAP-CRM-ACT-015

KindWorkflowProduct areaCRMModuleActivities, Follow-ups and Task WorkRevision1

Read atservices-crm a8d1364freact-console baf6dae3

Write a task and keep its overdue item in step ​

What It Does ​

Task writes combine work persistence with conditional overdue publication. The drawer uses ordinary patches for field and assignee changes, with separate commands for completion, cancellation and reopening. The structured hops describe API-only deletion as well.

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 ​

Validation and lifecycle failures return without a committed task change. When publication is enabled, its failure also refuses the write. Shared-list revalidation after a closing action does not guarantee that manually held drawer details have been reread.

Open Design Questions ​

Product needs to settle replacement completeness, task history and the availability cost of making attention publication part of the task transaction.

Controls

27 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-MON-001 TC-MON-002 TC-PI-001 TC-PI-003 TC-PI-004 TC-PI-005 TC-PRV-001 TC-PRV-002 TC-TEN-001 TC-TEN-002 TC-TEN-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