Type a prompt, drop a source chip inline, click send, and hard-cut to the running session

What the source does

On a white field a centred 'What should we work on?' heading sits above a rounded composer with a plus, a mode pill, a model label and a black send circle. The first clause types on at local ~0-15, an inline source chip with a small icon pops in at ~28, the rest of the sentence types across two lines from ~30 to ~75. The pointer travels in and clicks the send circle at ~88; at ~103 the picture hard-cuts to a browser window on a dark starfield showing the prompt echoed at the top and a 'Thinking' status.

Composer build-to-send: character type-on interrupted by an inline chip insertion, a pointer click on send, then a hard cut to the resulting session view.

Phase notes

1. Frame 0 — First clause types on
2. Frame 28 — Inline source chip pops in
3. Frame 30 — Remaining sentence types across two lines
4. Frame 75 — Prompt complete
5. Frame 88 — Pointer clicks send
6. Frame 103 — Hard cut to session window

Use this example

1. Watch the source and draft at normal speed. Compare the order of actions, the held states, and the transition into the result.
2. Download the project and read its README before changing inputs. The package includes its implementation and declared dependencies.
3. Replace the sample content through the package's documented input or content builder. Keep source footage in the research comparison.
4. Render your adaptation and inspect text fit, framing, intermediate states, and entry and exit frames.

Recorded limits

• Visual fidelity is an authored draft judgement from sampled source frames; no independent blind review or native Resolve execution.
• Both variants rerendered from the packaged text renderer to repair a prior code/preview mismatch.

Inspect the original verification record ↗