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.