Settle Attributed History Before Commit

Context

Staff need a reliable account of record changes, and reconstruction needs previous values. Database capture applies to all supported writers, including partner functions.

Decision

Temporal capture and deferred revision settlement commit attributed history with the business change and reject unacceptable attribution.

Alternatives Considered

History written by each service operation: Per-operation history writes could be omitted by an individual code path.

Versions only, without revisions: Versions alone would not provide the grouped actor and source timeline that staff read.

Consequences

Relevant supported changes cannot commit without the required attribution. The Commerce owner function must use a source accepted by history before placement can succeed. Revision creation has no dispatcher delay; only transport cleanup follows commit.