Keep delivery coordination separate from application-owned results

Context

A sale can require several applications to deliver different results, while staff need one account of outstanding work.

Decision

Keep delivery coordination and its persisted companion records in Fulfillment, with results owned by the delivering application.

Alternatives Considered

Keep delivery tracking inside each application. Separate application histories duplicate gate and intervention logic and make order-level diagnosis harder.

Move shared findings, adjustments and interventions to Operations. Moving shared records requires a deliberate writer and transaction contract, which is still open.

Use a general Platform workflow engine for the register. The current gates and participant operations are Commerce-specific rather than a generic workflow contract.

Consequences

Applications answer the participant contract. Shared ledger writers remain an explicit boundary decision.