A free text preview inside a paid media workflow creates a very specific UI problem: what, exactly, has the user approved?

I am the maker of AI Rap Videos , where a person or pet photo becomes a short rap performance. The public flow lets people preview and edit four English lyric lines before purchasing a video. That gives a concrete example for the design pattern below. This is a suggested frontend model, not a description of our private backend or a claim about conversion results.

Separate three promises

A lyric preview shows the words. It does not preview the final voice, timing, facial motion or complete video. A price quote describes a purchase. A generation result proves that a file exists.

Those three promises should have different labels and states.…