Rhythm 2.0 Specifications

Appearance

WF-PFM-NOT-013Record provider feedback

Markdown

WF-PFM-NOT-013

Record provider feedback

Markdown
  • DocumentDraft
  • ImplementationObserved

Planning

Implements
CAP-PFM-NOT-019, CAP-PFM-NOT-020

KindWorkflowProduct areaPlatformModuleStaff Notifications and Association CommunicationsRevision1

Read atservices-platform ad3f6a65react-console baf6dae3

Record provider feedback ​

What It Does ​

SES publishes delivery or engagement feedback.

The Flow ​

When Something Fails ​

The hop rows identify each retry boundary, any state left behind and the available observer. Derived event identity ignores duplicates; precedence and earliest timestamps tolerate reordering. Database event updates are atomic, but subsequent address suppression has a separate failure boundary.

Open Design Questions ​

Copy-recipient events remain historical without changing primary-recipient delivery outcome. Untagged provider events are acknowledged as unrelated. Tagged messages not yet visible can be retried before dead-letter handling.

Controls

46 controls apply, from the corpus control catalogue.

TC-AVL-004 TC-AVL-005 TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-AZ-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-DAT-006 TC-IAM-001 TC-IAM-002 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-PI-001 TC-PI-002 TC-PI-003 TC-PI-004 TC-PI-005 TC-PRV-001 TC-PRV-002 TC-PRV-004 TC-SEC-001 TC-SEC-002 TC-SEC-003 TC-SEC-004 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