Staff-Driven Data Runs

Context

A migration coordinates changes owned by several services.

Decision and Origin

A run progresses when staff start, resume or read it, forwarding that caller’s authority to dataset jobs instead of storing credentials or running a background driver. The origin recorded above supplies the authority for this choice; implementation evidence supplies the limits described here.

Alternative Comparison

Add a scheduled driver with its own service identity: A separate driver needs an explicit identity and authorization design beyond the current staff-driven implementation.

Persist a staff token for later replay: The current design deliberately avoids persisting bearer credentials.

Consequences

Completed datasets do not automatically advance an unattended run.

Concurrent readers can each attempt to drive the same run.

Migration clients must continue polling to make progress.