Timeline Evidence P08
0.0s
Previews are illustrative demonstrations of the technique — not your footage. Your real edit is produced later by Claude Code.
P08 · Proof · intermediate · 3–12s
A chronological track draws across the frame and real dated events pop onto it one at a time, each with its date label and supporting capture.
A thin timeline extends through the frame while dots light up at each supplied event, in date order. Each stop shows its real date and a short observation — optionally with a thumbnail of the supporting screenshot — and holds long enough to read before the line advances. Laying evidence out in time makes a sequence of cause and effect easy to follow and hard to dispute.
Try the parameters
Best used for
- — Investigations and explainers
- — Project or company history
- — Documenting a case or dispute
- — Growth journeys with dated proof
Assets
- ● Verified data required
- ○ Screenshots optional
- ○ Document / PDF optional
- ○ Photos optional
- ○ Source video optional
Pairs well with
If assets are missing
If events lack dates or sources, show only those that have both and ask about the rest. With no supplied events at all, omit the timeline — never reconstruct a chronology from assumptions.
Accessibility
Each event's hold must cover reading time (≈ 3 words/second + 0.8s). Dates must be readable text, not just dot positions; keep the line and labels at ≥ 4.5:1 contrast.
Individual prompt
updates with the parameters above# CES style instruction — P08 Timeline Evidence You are an experienced motion designer and video editor working in Claude Code. Apply the **P08 Timeline Evidence** 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 **Proof** — A thin timeline extends through the frame while dots light up at each supplied event, in date order. Each stop shows its real date and a short observation — optionally with a thumbnail of the supporting screenshot — and holds long enough to read before the line advances. Laying evidence out in time makes a sequence of cause and effect easy to follow and hard to dispute. ### P08 Timeline Evidence - **When:** ≈ 00:00.00 → 00:06.00 (≈ derived — adjust to the nearest natural beat in the footage) - **Layer / track:** V2+ (overlay above the picture) - **What it does:** A chronological track draws across the frame and real dated events pop onto it one at a time, each with its date label and supporting capture. - **Parameters:** Events (one per line: date | observation): (not set); Max events on screen: 4; Orientation: Vertical (best for 9:16); Date display: Exactly as supplied; Hold per event: 1.4 s; Show evidence thumbnails: on; Accent colour: #D7FF5F - **Steps:** 1. No events are set. Read them from the user's supplied data/document (date + observation per line). Do not infer dates from memory or fill gaps — every stop needs a real date and a source. 2. Lay out a vertical track at 18% from the left edge spanning 20–80% of frame height (from 00:00.00 to 00:06.00). The line draws downward in #D7FF5F (0.5% of frame width) segment by segment, reaching each stop over 11 frames. 3. At each stop: the dot pops (scale 0 → 1.15 → 1 over 8 frames), then the date label (Inter mono-style, ≈ 2.8% of frame width, exactly as supplied) and the observation (Inter semibold, ≈ 3.6%) slide in from the track side. 4. Where an event has a supporting screenshot or photo from the user's assets, show it as a small rounded thumbnail (≈ 22% of frame width) beside the text. Never add thumbnails for events without a supplied asset. 5. Hold each stop ≥ 1.4s (longer when the observation exceeds 4 words) before advancing; previous stops stay visible at 60% opacity. After the final stop, hold the whole timeline 1s, then fade over 9 frames. - **Assets:** Verified data (⚠ MISSING) · optional: Screenshots, Document / PDF, Photos, Source video - **Fallback:** If events lack dates or sources, show only those that have both and ask about the rest. With no supplied events at all, omit the timeline — never reconstruct a chronology from assumptions. **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.
More proof styles
Use proof whenever you make a claim. Every proof style requires authentic, supplied assets — never fabricated ones.
- P01Screenshot PunchA real screenshot drops in over the speaker at a precise scale, lands with a soft overshoot and a deep shadow, holds long enough to read, then clears.
- P02Comment SpotlightOne real comment is lifted out of the feed onto a clean card, the rest of the frame dims, and the key phrase is marked with a highlighter sweep.
- P03Metrics Count-UpA verified number ticks up from a meaningful starting value to its exact final figure in large tabular numerals, with its source label underneath.
- P04Before and After WipeTwo aligned real visuals share the frame while a clean divider line sweeps across, revealing the after state over the before, then rests on a split.
- P05Search-to-ResultA search bar types the exact query character by character, a short loading beat follows, and it resolves into the real captured result card.
- P06Receipt StackSeveral real proof captures deal onto the frame one by one, each fully readable before the next lands, building a tidy stack of receipts.
- P07Annotation MarkerA hand-drawn circle, arrow, underline or box draws itself onto the exact part of a real screenshot, with the rest of the image gently dimmed.
- P09Quote Card RevealA supplied quotation is set in elegant type on a card, revealed line by line behind large quote marks, with the author and source fading in last.
- P10App UI BreakdownThe camera zooms from a real full-screen capture into one interface element, dims the rest, and a callout line labels what that element actually does.