The proof follows the real hosted path
The synthetic fixture enters the same architecture used by hosted runs: web intake, Postgres job state, worker execution, object storage artifacts, gate results, and packet download checks.
Product proof
A synthetic wide-bar run proves the hosted gate path, not production approval.
DigitizingFlow's current public proof is a synthetic wide-bar fixture that the hosted worker can process into PES/DST candidates, previews, reports, and a sewout packet. It is software-side evidence only: production approval remains blocked until a physical sewout is stitched and accepted.
Direct answer
What the proof shows
The wide-bar fixture proves the hosted upload, worker, artifact, gate, and packet path can complete for a controlled synthetic design. It does not prove arbitrary customer artwork or production readiness.
Boundary
The production boundary
The correct status for this proof is software_ready_pending_sewout. A sewout-approved claim requires physical stitch evidence tied back to the exact design and artifact hashes.
Evidence table
Evidence boundary table
Each row separates the current implemented proof from the claim it is not allowed to make.
| Evidence | Current proof | Boundary |
|---|---|---|
| Source artwork | Synthetic wide-bar fixture used by local and hosted smoke tests. | Not a customer sample and not proof for every artwork style. |
| Worker result | The worker path can reach software_ready_pending_sewout. | software_ready_pending_sewout is not sewout_approved. |
| Artifacts | Machine files, reports, previews, and packet ZIP evidence are produced. | Operators still inspect hashes, files, and physical sewout results per run. |
| Operations | Rollback and cleanup smokes prove transient records are removed after tests. | Smoke cleanup is not a substitute for a customer retention policy. |
The useful result is visible evidence
Operators can inspect generated machine-file candidates, reports, previews, gate language, and packet manifests without reading Railway logs.
The proof refuses the wrong claim
The product page names the current capability while keeping the final production decision attached to physical sewout evidence.
Questions
What this page can honestly claim
Is the wide-bar proof a customer production sample?
No. It is a synthetic fixture used to prove the hosted pipeline contract without exposing customer files.
Can I call the output production-ready?
No. The proof can support software readiness. Production approval still requires physical sewout evidence.
Next step
Move from claim to reviewable evidence.
Queue artwork, inspect generated evidence, and keep physical sewout approval separate from software readiness.