# Showcase video guide

Scope: short launch and social videos of the product's own interface, cut from scenes that a director specifies beat by beat. Covers the default look, the cursor, the camera, timing, transitions, composites, data honesty, recording and review. It does not cover voiceover, music or captions.

> **Scope:** The product's own animations play as the product ships them. The camera, the window's entrances and exits, and composited overlays follow this guide, not the [product UI motion tokens](../../product-ui/references/motion.md).

This guide gives the method and the defaults. The director owns the story, the scene list, each scene's beats, its surface in the product and its time limit, written as a [scene spec](scene-spec.md). Distinguish three kinds of rule:

- **Requirements** hold in every scene: time limits, the shared frame, declared composites, honest data.
- **Defaults** apply until the director or the shot asks for something else: the look, cursor pacing, zoom speeds.
- **Choices** are the director's: what each beat shows, where it happens, how a scene enters and leaves.

When a beat is ambiguous, build the most likely reading, say which reading you chose, and let the director correct it on the cut. A rendered draft settles more than a question.

## Choose the surface for the story

A beat's meaning depends on where it happens. Teaching an agent a lasting rule reads as guidance in an ongoing chat with finished work above it, not as a setting changed in a workbench. Before staging, ask what the viewer should believe just happened, then pick the surface and the prior state that say it. Seed that prior state (earlier messages, completed work, existing records) so the beat lands as a continuation.

## Every action has a consequence

Each click opens, sends, changes or reveals something on the next frames. Remove hovers and clicks that only point at things. One click that opens a work thread beats two hovers over its cards. Hide the cursor for a scene with nothing to click.

## Default look

The default is a ScreenStudio-style shot: the real product in a rounded window on a soft wallpaper, with a drawn cursor that moves like a hand. Every scene shares one frame so that hard cuts between scenes never jump. These are the canonical values for that frame.

| Property | Value |
| --- | --- |
| Aspect | Match the director's reference file. Default 16:9. |
| Canvas | 1600 × 900 CSS px, captured at 2x |
| Output | 1920 × 1080 H.264, 30 fps, plus a poster PNG |
| Window rect | x 40, y 40, 1520 × 820 on the canvas |
| Corner radius | 14 px |
| Window shadow | `0 0 0 1px rgba(20,20,40,.08), 0 24px 60px -12px rgba(30,30,60,.28), 0 8px 20px -8px rgba(30,30,60,.18)` |
| Wallpaper | `radial-gradient(120% 120% at 15% 10%, #f4efe8 0%, #e9e4f2 45%, #dfe8f1 100%)` |

Render above the reference resolution when it downscales cleanly; it leaves headroom for the edit.

Presentation CSS may hide carets and scrollbars, pin a height that would jump, or hide a development banner. It never restyles the product.

### Break the mold when the shot needs it

The default is a starting point, not a rule. A beat may leave the window when that reads better: a split screen of three clips, a table floating free on the wallpaper, a foreground avatar over a blurred app, a confetti burst scaled up to read at video size. Composites and simplifications are allowed throughout.

Build composite elements from the product's own code and assets: its avatar drawing code, fonts, icons, keyframes and effects. A composite drawn by the product's own code stays on brand and stays honest about what the product looks like. Declare every composite in the scene report.

## Cursor

The cursor narrates. It moves like a hand, not a pointer on rails.

- Ease every move, with a slight bow and small seeded offsets, so it reads as human and re-renders identically.
- Aim off centre: cards on their preview, rows on their left third, buttons on their label.
- Show an arrow over content, a pointing hand over anything clickable, and a ripple on click.
- Keep the cursor hidden until an entering window has landed.
- After the last action, drift the cursor clear of the subject.

Pacing defaults. A launch scene runs faster than a walkthrough; start fast and slow down only where the viewer must read.

| Moment | Walkthrough | Launch scene |
| --- | --- | --- |
| Hover dwell | 350 to 420 ms | 60 to 140 ms |
| Settle after a click | 150 to 200 ms | 40 to 120 ms |
| Typing | about 45 ms per character | about 16 ms per character |
| Move | from distance, 260 to 900 ms | 300 to 750 ms |

## Camera

Zoom to make the subject readable, and pull back to show consequence. The camera is a transform on the window; the product underneath is unchanged.

- Interpolate zoom scale logarithmically so the move feels even.
- When zoomed in, let the window bleed off every edge of the canvas. Never show strips of wallpaper beside a zoomed window.
- Anchor the subject where the eye will go next: lower in frame when text will grow above it, off centre when something will enter beside it.
- Typical moves run 600 to 1000 ms. A second, closer push onto a single number can go to 5x.
- Isolate a subject by peeling the rest of the UI away (far elements first, each pushed outward and faded) or by blurring the app back behind a foreground composite.

## Timing

A scene's time limit is a hard maximum. The entrance and the exit sit inside it. When a revision adds a beat, pay for it inside the same limit: fewer rows, a faster flip, a shorter count, shorter holds. Do not deliver an overrun and ask.

- Time beats to the director's split when one is given (for example, 4 seconds per beat).
- Hold the payoff long enough to read: about 2 seconds on a final number or state.
- Wait for product state off the clock. Advance to the next frame only once a sent message has landed, so no frame shows the empty state in between.

## Transitions

The wallpaper is the connective tissue. The final film joins scenes with hard cuts only; each scene carries its own entrance and exit so the cuts don't show.

| Move | Duration | Easing | Motion |
| --- | --- | --- | --- |
| Entrance | first 0.6 s (18 frames) | ease-out, `1 − (1 − t)³` | Window rises from fully below the frame to its rect |
| Exit | last 0.4 s (12 frames) | ease-in, `t³` | Window or its contents leave the frame; the final frame is bare wallpaper |

- **Rise from wallpaper.** The default between scenes. One scene exits to bare wallpaper; the next opens on the same wallpaper and rises in.
- **Match cut.** When two scenes share the window, the next scene opens on the previous scene's exact last frame: the same project, panels, sidebar, cursor point, timestamps and avatars. Pin everything that varies by run (a fixed clock epoch, seeded data) so the frames are identical.
- **Direction continuity.** An upward exit followed by an upward entrance reads as one motion. Choose exit direction with the next scene's entrance in mind.
- **Composite exits** use the same numbers: split columns drop out, foreground cards fall away while the blurred app fades to wallpaper.
- Never open or close on plain white. The film opens with a window rising from the wallpaper and may end on a hold.

## Data honesty

A launch video shows things viewers will take as true. Label every element in one of four categories and report it:

| Category | Meaning | Example |
| --- | --- | --- |
| Real | The running product and real data, unmodified | A published protein structure with its docked ligand pose |
| Staged | Real product, with seeded state or scripted replies | Earlier chat history; an agent's scripted reply; a stand-in card |
| Synthetic | Generated data that looks like science | A volcano plot from a fixed seed |
| Composited | Drawn over or around the product | An underline, a split screen, a foreground avatar |

- Generate synthetic data from a fixed seed and keep it biologically or chemically plausible. A staged chart follows the [visualization guidance](../../data-visualization/skills/fractal-data-visualization/SKILL.md).
- Never put synthetic numbers under a real drug, compound, gene result or customer name. Rename it ("Reference agonist").
- Never give a stand-in record a real person's face or name.
- When recording reveals a gap in the product (a panel that doesn't update live), report it. Fake it only if the director asks, and then label it composited.

## Recording

Record frame by frame, not in real time. Each frame advances every clock by exactly one frame: the app's animation frame time, CSS animations, the backend's scripted timeline, and `performance.now` for viewers that animate from it. Timing then holds however slowly frames capture. Inspect the recorder actually available; a real-time screen capture cannot meet this. The reference implementation is `videos/record.mjs` in the axon-web repository.

- Run against a mock or staged backend, never one that costs money or touches real accounts.
- Check framing with a single still before spending minutes on a take.
- Restart the mock backend before every take when its state lives in memory.
- Write a composite's inputs as notes from the take (rects, frame numbers), and keep the frames for the compositor.
- Record parallel scenes from separate app copies on separate ports, each with its own backend. Restart only your own.
- Inside nested iframes, measure geometry in that document and map it through the iframe's box; outer measurements come back wrong under zoom.

## Review

Make a contact sheet, then inspect full frames around every click and cut.

- The first frame after the entrance is a calm resting state.
- Hovered items show their hover state; clicks show the ripple and the state change on the next frames.
- Nothing sits mid-transition for more than two or three frames. Nothing jumps: no late-loading layout shift, no dialog changing height.
- No carets, scrollbars, private data or development banners.
- The scene ends on bare wallpaper, on the next scene's first frame, or on the film's final hold.
- The duration is at or under the limit.

## Report each scene

Deliver a cut, then describe it in the [scene spec](scene-spec.md) shape:

- the file, its length, resolution and frame rate;
- a beat-by-beat timeline in seconds;
- what is real, staged, synthetic and composited;
- any product gap found while recording;
- the take file and the command to re-render.

Collect the final scenes and the stitched film in one place for download.

## Forbidden outcomes

- A scene over its time limit.
- A cut that jumps: a different wallpaper, window rect, radius or shadow between scenes, or a match cut whose frames differ.
- An undeclared composite, staged record or synthetic dataset.
- Synthetic data under a real name.
- Restyling the product through presentation CSS.
- A cursor action with no visible consequence.
