Domain Saves Own History And Change Events

Context

A job records requested work while each domain owns the evidence of its saved records.

Decision and Origin

The engine emits no business lifecycle event; domain saves create record history and change events under the job and batch context, including initial-load revisions. The origin recorded above supplies the authority for this choice; implementation evidence supplies the limits described here.

Alternative Comparison

Emit started and finished events for every job: Job lifecycle publication is not implemented; completion notification remains an open product choice.

Replace individual history with one bulk history entry: A bulk summary cannot provide each record’s own revision history.

Consequences

History can attribute changed records to their job context.

Clients poll for execution progress.