Standardize customer artwork review
Every run captures the source file, target size, colors, settings, and notes that downstream operators need.
Track queue and artifact health
Admin views expose counts for designs, jobs, artifacts, audit events, environment configuration, and actionable failed jobs.
Download packet evidence
The packet workspace and ZIP route gather source, machine files, reports, previews, and manifest data for production review.
Built for repeatable work
The target user is an operator or shop manager who needs fewer mystery files and more visible status, evidence, and support context.
Shop-ready does not mean sewout-approved
The app can help prepare work for a shop floor, but the product must still record physical sewout evidence before production approval.
Operator questions
What this page can honestly claim
Can a shop use this to manage multiple runs?
The current app has dashboard, catalog, history, settings, upload, packet, and admin surfaces backed by Postgres.
Can support see why a run failed?
Admin users can inspect failed jobs, artifacts, audit events, support notes, and retry controls without shell access.
Next step
Run the workflow with the production boundary visible.
Queue artwork, inspect generated evidence, and keep physical sewout approval separate from software readiness.