Execution, record and meaning of a job have three owners

Context

Background work belongs to many domains, while operators need comparable records across them.

Decision

Assign retries, sequencing and timeouts to orchestration. Keep identity, progress and history in the shared engine. Let each domain define its own tables and tasks; Platform combines the published views and reconciles its own jobs.

Alternatives Considered

Centralizing business tasks would couple unrelated modules. Independent reporting would undermine cross-service monitoring.

Consequences

Owners share the recording protocol while retaining control of business behavior.