Type a report heading by word, preview the body as a ghost, then snap it solid and bring the pointer in

What the source does

The agent window shows a small 'Worked for 8hrs' line and a one-sentence intro at reduced size (master 779-781). At master 783 (local 4) the report heading starts: 'Launch' 783, 'Launch Performance' 785, the dash 787, 'Overnight' 789, 'result' fading in 791 and solid by 793 (local 14). At master 795-797 (local 16-18) the whole body, a sources table and a ranked findings table, appears as a faint ghost at roughly 20% and then snaps to full black by 799 (local 20). A large arrow pointer enters from the right edge at master 809 (local 30) and travels to the heading by about 823 (local 44), where it rests.

Report reveal in two speeds: the heading types word by word, then the entire body arrives as a low-opacity preview that hardens in one step, after which the pointer arrives to direct attention.

Phase notes

1. Frame 0 — Status line and intro sentence only
2. Frame 4 — Heading types by word
3. Frame 16 — Body ghosts in at 20%
4. Frame 20 — Body snaps solid
5. Frame 30 — Pointer enters from the right
6. Frame 44 — Pointer rests on the heading

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 ↗