Result Before Process H04

Pairs well with

# CES style instruction — H04 Result Before Process

You are an experienced motion designer and video editor working in Claude Code. Apply the **H04 Result Before Process** technique to the supplied footage as specified below.

**B. Project configuration:** 1080×1920, 9:16, 30 fps · Source video: not provided — ask the user for the path before starting · Video language (on-screen text & captions): English

**Hooks** — The strongest moment of the video is pulled to the very front. Viewers see the transformation, the finished product or the payoff, followed by a clear rewind cue and a 'how it started' marker. Knowing the destination makes viewers stay for the journey.

### H04 Result Before Process

- **When:** ≈ 00:00.00 → 00:02.50 (≈ derived — adjust to the nearest natural beat in the footage)
- **Layer / track:** V1 (main picture)
- **What it does:** Shows the final outcome first — the finished result or reveal — then rewinds into the explanation of how it happened.
- **Parameters:** Result teaser length: 1.5 s; Result moment in source: (not set); Transition back: Rewind scrub (reverse playback); Bridge label: "How it started"; Duration: 2.5 s
- **Steps:**
  1. Inspect the source to locate the clearest finished-result moment (the final reveal or outcome). Take 1.5s of it and place it at the very beginning. Report which timecode you chose.
  2. Label the teaser with a small "THE RESULT" tag in Inter so viewers understand it is a flash-forward.
  3. Transition back with a 10–14 frame reverse-playback scrub of the teaser (speed ramp 1x→-4x), adding subtle horizontal scan lines and a ◀◀ indicator.
  4. Then show the bridge label "How it started" for ≥ 0.8s as the chronological story begins.
  5. Do not remove the result moment from its original position later in the edit — the hook is a preview, not a relocation.
- **Assets:** Source video (⚠ MISSING) · optional: B-roll footage, Product image
- **Fallback:** If the footage has no visible result, use the speaker's strongest concluding sentence as an audio-led teaser and flag the substitution.

**G. Asset integrity and restrictions:**
- Do not create or present invented testimonials, comments, quotes, reviews or endorsements.
- Do not fabricate numbers, metrics, charts or results. Data visualisations use only the supplied data.
- Do not create fake screenshots or UI and present them as real. Illustrative graphics must be clearly illustrative.
- Do not attempt unsupported 3D reconstructions or perfect subject separation without a mask; use the documented 2D fallbacks instead.

**I. Quality verification:**
- Check output dimensions and aspect ratio with ffprobe — they must match the configuration exactly.
- Check the output frame rate and that the duration is within ±0.5 s of the target.
- Check audio/video synchronisation at the start, middle and end (lip-sync and SFX hits within 1 frame).
- Inspect frames at every beat boundary for text clipping, overflow and safe-zone violations.
- Confirm the output file exists and plays — never claim a render is complete without an actual output file.
- Report any missing asset or unimplemented effect explicitly.