# Detailed AI Screen Postpreview Pattern

Use this when producing TrueTrace/AutoShorts proof-short postpreviews after the user approved the B3-style standard: premium AI-generated real UI/screen images with readable concrete text, active-word subtitles, and no renderer-added focus graphics.

## Session-derived standard

The accepted direction is:

```text
Detailed AI-generated screen images + readable concrete UI text
+ voiceover + static active-word subtitles
- no focus lines/arrows/boxes/circles/checklist overlays
```

The user explicitly rejected minimal focus outlines because they added little value and reduced the premium look. Instead, make the AI keyframes themselves semantically rich enough that the problem is visible in the scene.

## Prompting pattern

For each keyframe, specify:

- vertical 9:16, premium cinematic social-video look
- exact UI/screen situation: email, invite, login panel, calendar, work drive, invoice, payment portal, etc.
- exact readable text that should appear on screen
- realistic UI details: sidebars, message rows, attachment cards, buttons, headers, attendee/file/avatar dots
- no real logos/brands unless explicitly permitted
- no people, hands, faces, QR/barcodes, watermarks
- clean lower safe space for subtitles

Good examples:

```text
Exact visible text: “Emma shared a file with you”; “Q3 Strategy Notes.pdf”; “Open document”; “Sign in to view”.
```

```text
Exact visible text: “Calendar”; “Quarterly Review Meeting”; “Today, 10:00 AM”; “Open from calendar”.
```

## Rendering pattern

1. Generate 5–6 keyframes with detailed readable screens.
2. Build a contact sheet and QA before rendering.
3. Render only AI images + voiceover + active-word subtitles.
4. Use subtle push-in/crossfade motion; avoid extra overlay marks.
5. Use EdgeTTS word-boundary cues or equivalent forced alignment.
6. Segment captions by sentence, not one global sentence string, so phrases do not bridge awkwardly (e.g. avoid “trap works The file name”).
7. Export with explicit mobile-safe metadata:
   - `1080x1920`
   - `SAR=1:1`
   - `DAR=9:16`
   - `yuv420p`
   - H.264 High, `+faststart`
8. Probe and extract QA frames before delivery.

## QA checklist

- The first 1–2 seconds show a concrete visible problem without relying only on voiceover.
- The image text is readable enough to carry the mechanism.
- No renderer-added lines, arrows, boxes, circles, labels, or checklist cards.
- Active-word subtitles are readable, not clipped, and do not cover crucial UI.
- Caption phrases do not cross sentence boundaries awkwardly.
- No people/hands/faces/QR/watermark/logos unless explicitly approved.
- `ffprobe` confirms `width=1080 height=1920 SAR=1:1 DAR=9:16`.

## Example approved topics

- Calendar invite login trap: suspicious invite asks for sign-in; safe action is opening calendar/work app directly.
- Shared document login trap: email says a file was shared; safe action is closing the email and opening the work drive directly.

## Approval package

Include:

- candidate id and version
- MP4 `MEDIA:` path
- technical probe summary
- SHA256
- social draft: title variants, caption, hashtags, CTA
- explicit commands:
  - `APPROVED_POSTPREVIEW <candidate> <version>`
  - `REVISE_POSTPREVIEW <candidate> "..."`
  - `REJECT_POSTPREVIEW <candidate>`

No platform posting or platform API calls during preview approval.