Rhythm 2.0 Specifications

Appearance

WF-PFM-INT-010Migrate bindings to another contract major

Markdown

WF-PFM-INT-010

Migrate bindings to another contract major

Markdown
  • DocumentDraft
  • ImplementationObserved

Planning

Implements
CAP-PFM-INT-007

KindWorkflowProduct areaPlatformModuleIntegration access, customer extensions and shared workflow configurationRevision1

Read atservices-platform ad3f6a65

Migrate bindings to another contract major ​

What It Does ​

A contract-major migration copies routing choices through the ordinary binding rules. Each scope commits independently, allowing partial progress and repeat requests. The old major remains available unless the caller explicitly supersedes its bindings.

The Flow ​

When Something Fails ​

Reject malformed migration options. No binding copy is attempted. Report the reason for each refused copy. Successful copies remain even when others fail. Rollback only the failed binding transaction. Other committed scope migrations remain intact.

Open Design Questions ​

The approved gateway milestone deferred major migration, so its implemented availability remains a planning disagreement.

Controls

38 controls apply, from the corpus control catalogue.

TC-AVL-001 TC-AVL-005 TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-CHG-001 TC-CHG-002 TC-CHG-003 TC-CHG-004 TC-CHG-005 TC-CHG-006 TC-CHG-007 TC-DAT-001 TC-DAT-002 TC-DAT-003 TC-DAT-004 TC-IAM-001 TC-IAM-002 TC-IAM-004 TC-IAM-005 TC-LOG-002 TC-LOG-003 TC-LOG-004 TC-LOG-005 TC-MON-001 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-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