Job Lifecycle
Scriptoria treats download and export work as tracked jobs backed by local state.
Download Jobs
A typical download job:
- is created from discovery or library actions;
- records progress in local state;
- stages validated pages first;
- promotes them according to storage policy;
- can be paused, resumed, retried, or cancelled.
Export Jobs
A typical export job:
- starts from a profile or page-level action;
- records progress in local state;
- uses local or temporary remote assets depending on the profile;
- persists output artifacts under managed paths.
Why The Model Matters
The job layer is the safety mechanism that keeps partial work understandable and recoverable.