Data Run

What It Models

A data run coordinates one initial migration package across the applications that own its datasets. It records dependency order, child jobs and copied progress. A separate readiness answer helps staff assess the resulting load. The run delegates all business writes to those child jobs.

Identity and Attributes

The package identity relates attempts to the producer’s delivery, while the run identity distinguishes each registration. A duplicate unfinished package is refused when visible to the registration transaction; concurrent absence checks remain a gap. Manifest claims and system-computed progress remain separate.

Relationships

Manifest and dataset uploads can be reused by later runs. Child jobs belong to CRM or Platform and their counts are copied onto steps when polled. Producer mappings support reconciliation without becoming run-owned records.

Invariants

Registration gates the destination, available upload evidence and dependency graph. The driver forwards staff authority and limits blocked work to one additional attempt. Final runs remain final, and no parent outcome removes committed business records.

How It Is Stored and Shared

Platform owns runs and steps under workspace row security and exposes them through staff-only system routes. Remote datasets use the current staff token; Platform datasets execute locally in a workspace context. Reset preserves migration evidence, while deletion removes it. Runs enable no custom fields.

Open Design Questions

Readiness neither blocks activation nor detects excess counts. Submission failures and concurrent passes can leave untracked child work; cancellation can finish while a child still writes. Unexpected progress responses can remain unsettled indefinitely. Membership participation is still incomplete.