Publish Reparenting Inside the Placement Transaction

Context

Connected services may need to react when a unit changes parent. Structural telemetry and a durable published business event have different roles and guarantees.

Decision

The existing business-event seam covers reparenting only. The registry determines configured recipients afterward, but this examination does not infer delivery bounds or receiver behavior from the outbox declaration.

Alternatives Considered

Publish the business event only from the response path after commit. A post-commit request failure could lose the event for an already committed structural change. Publish business events for all structural lifecycle changes. Additional merge and closure notifications require defined consumers and a product decision; they are not part of the examined event contract.

Consequences

The reparent outbox write commits or rolls back with its placement transaction. No examined handler reacts to reparent events. Connected applications needing merge or closure effects currently require a separately designed integration.