Aggregate outcome notifications must carry the aggregate's committed previous status and…

Aggregate outcome notifications must carry the aggregate's committed previous status and occurrence timestamp through asynchronous delivery. A child's unchanged status can suppress a real parent transition, while re-reading a mutable row later can attach a newer timestamp or hide an earlier event entirely. Capture these values at the transaction boundary, then build one fixed payload for the delivery attempts. Test unchanged-child/changed-parent cases and context that advances before dispatch. This method preserves event meaning; it does not provide durable delivery or exactly-once receipt.