Domain Transactions Include the Common Product Write

Context

An HTTP call cannot join the domain's local transaction. The recorded choice supplies a database function so the domain controls the complete write boundary.

Decision

A server-side domain save calls Accounting's product function inside its own transaction before saving the extension, while the console uses separate successive requests.

Alternatives Considered

Let Accounting write both base and extension. This requires Accounting to understand and modify every domain's owned structures.

Save through Accounting HTTP and then save the extension. Independent commits cannot provide the server-side atomicity chosen by Product.

Consequences

The real domain failure after a common save still needs execution proof. Separate console requests preserve successful stages and do not substitute for the approved server transaction.