Record machine context
Operators can set machine profile, hoop size, fabric profile, and thread weight before the run is queued.
Run the hosted digitizer
The worker consumes queued jobs, runs the pipeline, and persists DST output candidates with reports and previews.
Escalate risky output
The status model keeps manual-review, software-ready, and sewout-approved states distinct across APIs and UI.
Designed for shop handoff
The packet workspace gives production teams a single place to inspect run settings, readiness checks, and downloadable artifacts.
DST is not the last gate
A DST artifact is not a production claim. The final approval step is still physical sewout evidence tied to the design.
Operator questions
What this page can honestly claim
Does DigitizingFlow support DST output?
The hosted worker stores DST candidates for supported runs and exposes them through artifact downloads and packet ZIPs.
What if the DST candidate needs correction?
The run can remain in manual review, and admin/support tooling can inspect jobs, artifacts, notes, and audit events.
Next step
Run the workflow with the production boundary visible.
Queue artwork, inspect generated evidence, and keep physical sewout approval separate from software readiness.