Skip to content

TASK: Establish notification delivery lifecycle foundation #160

Closed

Description

@ramioooz

Parent: #60

Objective

Create the notification-service foundation needed to consume future transfer outcomes without coupling the service to a specific provider.

Scope

  • Define a transport-neutral notification command and delivery lifecycle.
  • Model correlation, idempotency, retryable failure, and terminal failure boundaries.
  • Keep Kafka consumption, provider integrations, credentials, and external delivery deferred until their event-contract and provider tasks are ready.
  • Add focused unit tests and documentation of the boundary.

Acceptance Criteria

  • Repeated notification requests with the same idempotency key are deterministic.
  • Retryable and terminal outcomes are distinguishable.
  • Provider credentials and message content are not committed.
  • The implementation is reviewable as a non-draft PR and links this task and parent story.
  • Maven verification passes.

Activity

  1. self-assigned this
    on Aug 30, 2026
  2. added theissue type on Aug 30, 2026
  3. ramioooz commented on Sep 1, 2026

    @ramioooz
    MemberAuthor

    Completed by merged Notification Service PR #2. The notification delivery lifecycle foundation is implemented and verified.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions