Production judge path for the public PatternProof deployment. No account or credentials are required.
- Open https://patternproof-nu.vercel.app/create.
- Use Next to see the recorded YouCam result and byte-identical repeat evidence.
- Confirm that a human Not feasible decision changes Cut Readiness to blocked.
- Continue to see a customer veto become a traceable V1 → V2 revision rather than an editable approval.
- Watch three independent keys—YouCam evidence, tailor judgment, and customer consent—bind to one Expectation Checksum and change DO NOT CUT to CUT RELEASED.
- End on the privacy-exit state, then open the immutable public record.
The sample opens immediately and never writes a customer record. Choose Create with my photos to open an isolated, consent-bound guest workspace without an email or password. /s/demo-olive is the byte-pinned, read-only frozen record.
The zero-login sample uses byte-pinned synthetic assets and cannot write a customer or database record. It demonstrates product logic and recorded provider evidence, not a new live YouCam call. The separate Create with my photos path opens a tenant-isolated private guest record and uses live provider jobs.
No invited account is required. Use only images you own or the rights-cleared fixtures in test-assets/.
- Open
/create, choose Create with my photos, confirm both consent statements, and create the isolated private brief. - Optionally run Clean garment background. Background Removal rescues a difficult reference before the core try-on; the original reference and rescue hash remain distinguishable provenance.
- Generate the body-specific YouCam Clothes VTO V3 preview. PatternProof admits one two-unit task, polls it, validates the result host/body, and re-hosts the image privately.
- Choose one server-validated predefined fabric direction. Fabric VTO creates a comparison artifact; it is explicitly not an uploaded swatch, colorimetry test, or drape simulation.
- Add the construction non-negotiables and record the human feasibility decision for each. A single Not feasible decision blocks sharing.
- Create the 14-day customer link, open it in a private window, inspect the frozen digest, and approve the exact snapshot. To inspect the veto branch instead, request a change and watch Revision Replay create a traceable V2.
- Return to the approved owner record and create the fixed five-second 480p Image-to-Video V2 presentation proof. It is admitted only after approval and never changes the construction checksum.
- Use Erase customer photo. The private body input disappears while the garment reference, approved preview, decisions, and proof remain auditable.
This clean production chain passed on August 14, 2026 with four YouCam jobs, exact 10-unit internal accounting, no automatic provider retry, and 164.5-second end-to-end latency. See RELEASE-ACCEPTANCE.md.
- Technological implementation: four apparel-relevant YouCam jobs with distinct lifecycle roles: Background Removal rescue, Clothes VTO V3 evidence, predefined Fabric VTO direction, and post-approval Image-to-Video V2; plus private signed inputs, normalized/re-hosted outputs, content-addressed idempotency, one exact-cost circuit breaker, RLS, atomic approval/veto serialization, and cleanup fencing.
- Design: one continuous intake → preview → human feasibility → customer veto/revision → private approval → immutable Cut Card journey, including honest failure states.
- Potential impact: a specific pre-cut communication checkpoint. The formative research supports problem discovery; VALIDATION-PROTOCOL.md defines the prospective test. No remake-reduction claim is made without results.
- Idea quality: virtual try-on becomes one key in a physical-production interlock. AI evidence, craft judgment, and customer consent must resolve to the same frozen SHA-256 Expectation Checksum before cutting is released.
The preview communicates visual intent only. It does not guarantee measurements, physical fit, construction, fabric drape, or final appearance. Customer links are unguessable expiring bearer links; possession grants access. The public example is synthetic and immutable.
If a live dependency is unavailable, the zero-login path remains deterministic. Do not describe a dependency failure as successful live integration; consult D1-RESULTS.md for recorded provider evidence.