The Request Object Is Written Inside the Caller's Transaction

Context

Association requests need external storage, but their dispatch eligibility must follow the producer’s transaction.

Decision

The communication helper makes a bounded request-object write before inserting the committed pointer within the caller’s transaction.

Alternatives Considered

Writing before business decisions finish can preserve content that disagrees with the eventual committed action.

Consequences

A storage timeout fails the producer transaction rather than leaving an unbounded wait. Rollback can leave an orphan request object that expires after thirty days. Platform receipt doors store the object before opening their own short database transaction.