Document Flyover B09

Pairs well with

# CES style instruction — B09 Document Flyover

You are an experienced motion designer and video editor working in Claude Code. Apply the **B09 Document Flyover** 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

**Animated B-Roll** — A real PDF page or document scan is presented as a physical sheet, then the camera moves in to the specific passages the speaker refers to. Each passage is marked with a highlight, box or underline while the rest of the page softly dims, so viewers can read the actual source wording. It turns 'it says so in the report' into visible, checkable evidence.

### B09 Document Flyover

- **When:** ≈ 00:00.00 → 00:05.00 (≈ derived — adjust to the nearest natural beat in the footage)
- **Layer / track:** V1 (main picture)
- **What it does:** A supplied document page tilts into view, then a guided crop glides between the exact lines that matter while a marker highlights each one.
- **Parameters:** Document page: (not set); Highlighted passages: 2; Highlight style: Marker sweep; Highlight colour: #D7FF5F; Crop zoom: 2.2x; Paper tilt intro: on; Hold per passage: 1.2 s
- **Steps:**
  1. Cut to a document cutaway from 00:00.00 to 00:05.00. Source: the supplied document — rasterise the page at ≥ 300 dpi (e.g. pdftoppm -r 300) so it stays sharp at 2.2×. Build only from the supplied assets — do not invent details, text, UI, numbers or features that are not present in them.
  2. Intro: the page enters as a sheet tilted rotateX 18° / rotate −4° and settles flat over 18 frames, with a soft paper shadow on a dark desk-like backdrop.
  3. Choose 2 passages that the speaker actually quotes or references during this range; locate them by text search in the PDF (e.g. pdftotext -bbox) so the crop targets the real coordinates. Never highlight wording that is not on the page.
  4. Guided crop: push from the full page to 2.2× on passage 1, then glide (15 frames, ease-in-out) to each following passage, holding 1.2s (36 frames) on each. Dim the area outside the current passage to 60% brightness.
  5. Mark each passage with a #D7FF5F marker band (multiply blend, 55% opacity, slightly taller than the text line) that wipes left → right over 11 frames, starting as the crop arrives.
  6. Before export, check for personal data (names, signatures, account numbers) visible in the crop and blur it unless the user confirms it may be shown.
- **Assets:** Document / PDF (⚠ MISSING) · optional: Screenshots
- **Fallback:** If only a photo of the document exists, deskew and flatten it first; if the passage cannot be located reliably, ask the user for the page and line. Never retype a document as a mock page.

**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.