Data Job

What It Models

A data job records one requested change across a set of records. Staff use its saved input, progress and outcomes to review a preview, follow an import and account for partial completion. Record outcomes belong to the job as receipts and refusals.

The shared library defines the model, while CRM and Platform keep separate instances beside the business records they administer.

Identity and Attributes

Item positions remain stable after submission, allowing an operator to relate a result to the original input. The job combines caller-supplied change data with system-computed lifecycle state, impact, progress and evidence. A submission key recognizes repeated requests while its ledger entry exists; simultaneous first requests can produce a conflict for the losing caller.

Relationships

Completed uploads supply file input. Producer mappings connect external keys to saved records, and migration steps retain the identities of their child jobs. File admission reads the shared capacity factor. Later jobs can correct, revalidate or compensate an earlier job.

Invariants

The structured invariant rows identify the transactional boundaries and their enforcement limits. Item receipts protect redelivery of one job; they do not establish uniqueness across independent jobs using the same new producer key. Controls and automatic settlement also have different transition enforcement.

How It Is Stored and Shared

Each adopter stores the shared engine family under workspace row security. CRM adds durable execution records for its file workflow. The record owner performs each business write and supplies history and change events. CRM job inspection uses its API; Platform migration work can call its local job services directly. These engine records enable no custom fields.

Open Design Questions

Evidence retention remains unenforced, and Platform has neither a submission-key purge nor scheduled recovery for interrupted request execution. Job completion has no notification event. File grouping, producer-key concurrency and the remaining recovery findings require attention before stronger guarantees are accepted.