Rhythm 2.0 Specifications

Appearance

WF-PFM-INT-017Route integration events to application consumers

Markdown

WF-PFM-INT-017

Route integration events to application consumers

Markdown
  • DocumentDraft
  • ImplementationObserved

Planning

Implements
CAP-PFM-INT-015

KindWorkflowProduct areaPlatformModuleIntegration access, customer extensions and shared workflow configurationRevision1

Read atservices-platform ad3f6a65

Route integration events to application consumers ​

What It Does ​

Applications declare consumers for provider event types at deploy. Routing claims a numbered attempt, invokes each matching consumer and records outcomes separately. Completion events restrict that selection to the application that requested the provider call.

The Flow ​

When Something Fails ​

Return registration refusal to the deployment. The preceding consumer declaration remains. Reject the complete invalid event batch. No partial batch is retained. Keep failed publication work for another pass. Repeated queue delivery is possible and must be claimed by attempt number. Retry invocation failure or an explicit retry outcome, then mark dead after the limit. Consumers already successful can be invoked again on a later attempt. The consumer contract can request retry. Application records may lag while the event remains unresolved. A settlement failure does not undo earlier consumer calls or earlier committed event results. Unrecorded outcomes need recovery even if some applications already acted.

Open Design Questions ​

The approved planning layer already describes repeat delivery and consumer deduplication; this design cites that obligation rather than claiming a new decision. Host effects are outside the examined code boundary.

Controls

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