---
id: TST-MBR-MEM-015
title: Membership outcome delivery and retries
kind: integration
product_area: membership
module: memberships
revision: 1
status: draft
source_sha:
  services-membership: 5994c270e8a37a30f848e99ba5b5ee6b87c08893
repository: services-membership
files:
  - modules/events/tests/integration/change-events-dispatch.integration.spec.ts
implements:
  - ATS-MBR-MEM-020-06
  - ATS-MBR-MEM-020-07
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 3
isolation: >-
  A suite-owned workspace and test identifiers; suites that use shared seed data
  require the source’s serial execution and cleanup policy.
verification_notes: >-
  Bindings describe the assertions reviewed at the pinned commit; the suite is
  not executed by this documentation job.
coverage_gap: null
evidence:
  - >-
    services-membership:modules/events/tests/integration/change-events-dispatch.integration.spec.ts
assertion_anchors:
  - scenario: ATS-MBR-MEM-020-06
    source: >-
      services-membership:modules/events/tests/integration/change-events-dispatch.integration.spec.ts#hands
      Committees the termination alone, as { version: 1, stream, events } with
      data.contact_id and data.ends_on
  - scenario: ATS-MBR-MEM-020-06
    source: >-
      services-membership:modules/events/tests/integration/change-events-dispatch.integration.spec.ts#gives
      Committees the business event’s own id, so a redelivery names the same
      event
  - scenario: ATS-MBR-MEM-020-06
    source: >-
      services-membership:modules/events/tests/integration/change-events-dispatch.integration.spec.ts#answers
      the events Committees does not act on without calling it
  - scenario: ATS-MBR-MEM-020-07
    source: >-
      services-membership:modules/events/tests/integration/change-events-dispatch.integration.spec.ts#returns
      the message to the queue when Committees answers failed, so SQS retries it
  - scenario: ATS-MBR-MEM-020-07
    source: >-
      services-membership:modules/events/tests/integration/change-events-dispatch.integration.spec.ts#acknowledges
      the retried message once Committees takes it
  - scenario: ATS-MBR-MEM-020-07
    source: >-
      services-membership:modules/events/tests/integration/change-events-dispatch.integration.spec.ts#reports
      a failure on the queue’s last receive too, which moves the message to the
      dead-letter queue
---

# Membership outcome delivery and retries

## Verification Boundary

Business publication or event dispatch runs against the prepared database and local transport fixtures.

## What This Suite Proves

The structured bindings identify the capability and feature cases whose reviewed assertions this suite executes. Source anchors preserve the evidence for each binding.

## What It Does Not Prove

A local pass does not prove deployed queue retries, physical dead-letter transfer or receiver-side deduplication. Registration records existing code and leaves execution and conformance unverified.

## Real Dependencies and Test Doubles

Publication persistence and Membership event handling remain real. Queue submission and receiver invocation use recording transport fixtures where the suite dispatches work.

## Must Not Be Doubled

Keep the prepared database, workspace boundary, exercised owner constraints and the business operation under test real. A partner double cannot substitute for the Membership write this suite claims to exercise.