---
id: ADR-MBR-MEM-013
title: Publish Through the Current Change-Event Transport
product_area: membership
module: memberships
revision: 1
status: proposed
design_intent: open
source_sha:
  services-membership: 5994c270e8a37a30f848e99ba5b5ee6b87c08893
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: >-
  Business writers insert strict event payloads in their transaction and the
  change-event dispatcher delivers configured receiver work afterward.
constrains:
  - SVC-MBR-MEM-events
  - DOM-MBR-MEM-006
  - STATE-MBR-MEM-013
  - WF-MBR-MEM-025
origin: >-
  The events phase record's choice, left to Andrew; open question on the
  integration catalogue and retention
alternatives:
  - option: The integration catalogue's business-events outbox
    why_not: >-
      The integration outbox is a real alternative, but choosing it requires the
      unresolved catalogue and retention decision.
  - option: Publish after commit from the service
    why_not: >-
      Publishing only after commit creates a gap in which the business change
      can persist without its event.
consequences:
  - Publication shares commit and rollback with the described write.
  - >-
    Event keys remain outside the integration catalogue and the log has no
    shorter retention policy.
  - Only configured termination delivery calls Committees.
supersedes: []
evidence:
  - >-
    services-membership at 5994c270: modules/events/**;
    aws/membership.change-events.ts; docs/migrations/events/README.md
---

# Publish Through the Current Change-Event Transport

## Context

Membership already captures database changes for history. The draft uses that transport for partner events, while integration-catalogue ownership remains undecided.

## Decision

Business writers insert strict event payloads in their transaction and the change-event dispatcher delivers configured receiver work afterward.

## Alternatives Considered

The integration catalogue's business-events outbox: The integration outbox is a real alternative, but choosing it requires the unresolved catalogue and retention decision.

Publish after commit from the service: Publishing only after commit creates a gap in which the business change can persist without its event.

## Consequences

Publication shares commit and rollback with the described write. Event keys remain outside the integration catalogue and the log has no shorter retention policy. Only configured termination delivery calls Committees.