# TrueTraceShorts format-family expansion strategy

Use this reference when planning the next TrueTraceShorts / Everyday Red Flags content wave after the initial red-flag short format.

## Core brand promise stays unchanged

```text
One screen. One red flag. One safer move.
```

The channel remains digital self-defense for normal people. Do not pivot into generic AI tips or scambaiting/vigilante content.

## Format families

Every planned video must declare a `format_type` before scripting/rendering:

- `red_flag_short` — current main format: fast warning, clear red flag, safer move.
- `already_clicked` — recovery/help format for viewers in stress after clicking/paying/entering data.
- `spot_the_trap_quiz` — interaction format: viewer pauses/comments before reveal.
- `true_scam_story` — pattern/story format based on common reports; no fake concrete victim claims.
- `scam_breakdown` — mechanism/psychology format; explain one pattern simply.

Recommended mix for the next 20 videos:

- 50% `red_flag_short`
- 25% `already_clicked`
- 10% `spot_the_trap_quiz`
- 10% `true_scam_story`
- 5% `scam_breakdown`

## Required planning fields

For every candidate, store:

- `format_type`
- `hook_type` (`damage_first`, `identification`, `quiz`, `story`, `counterintuitive`, `recovery`)
- `viewer_state` (`not_clicked`, `already_clicked`, `helping_family`, `learning_pattern`)
- `website_target`
- `cta_type` (`follow`, `save`, `comment`, `checklist`, `share_family`)
- `duration_class` (`35-45`, `45-60`, `50-75`)
- `first_frame_scam_label`
- `evidence_level` (`generic_pattern`, `sourced_case`, `official_guidance`)
- `claim_mode` (`educational_pattern`, `sourced_case_summary`, `official_guidance_summary`)

## Format templates

### red_flag_short

Goal: reach + saves + series recognition.

Structure:

```text
0–2s: scam visible + first-frame red scam label
2–8s: why it feels real
8–18s: red flag
18–32s: safer move
32–45s: memorable rule + follow/site CTA
```

CTA: follow/save/share.
Website target: `/redflags/[slug]`.

### already_clicked

Priority new format. Goal: trust + search + practical help.

Structure:

```text
0–2s: Already clicked / entered / paid?
2–8s: First: stop doing more.
8–30s: 3 immediate steps
30–50s: what not to do
50–70s: when to contact bank/provider/authority
```

Tone: calm, no shame.
Preferred no-shame line family: `You didn’t do anything wrong. This is designed to make you hurry.` Avoid `You are not stupid` unless explicitly requested; it can sound unnecessarily defensive.
CTA: full checklist.
Website target: `/already-clicked` or `/redflags/[slug]#already-clicked`.

### spot_the_trap_quiz

Goal: comments + rewatch + active viewing.

Structure:

```text
0–3s: Can you spot the scam?
3–8s: hold screen / pause prompt
8–15s: reveal
15–30s: why it is dangerous
30–40s: safer move
```

Reveal via cut/zoom/crop/image change, not arrows/circles/explainer overlays.
CTA: `What did you notice first?`

### true_scam_story

Goal: retention + emotion.

Use only `based on common scam reports` / `reported pattern` wording unless a real source is explicitly cited. No fake victim names, exact amounts, or private details.

Structure:

```text
0–3s: outcome/consequence
3–12s: how it started
12–25s: the one moment that flipped it
25–45s: red flag
45–65s: lesson + safer move
```

### scam_breakdown

Goal: authority + pattern learning.

Structure:

```text
0–2s: counterintuitive statement
2–15s: 3 simple parts
15–35s: example screen
35–50s: safer move
```

Avoid cybersecurity jargon. Keep B1/B2 English.

## Visual standard

- Premium prompted AI keyframes as final main visuals.
- No self-built PowerPoint/mockup-looking final visuals.
- Critical scam text/data must be safe and controlled; if AI-generated screen text is used, inspect visually.
- First visible frame only: scam name inside the screen in readable red text, consistent for gallery/swipe. Do not repeat the scam name in every keyframe unless explicitly requested.
- No real logos, QR codes, phone numbers, bank/card/IBAN-like data, real domains, or private details.

## First implementation wave

Do not mass-render immediately. First implement the format spine and website recovery hub, then produce a 5-video test wave:

1. `Already clicked a fake delivery link? Do this now.` — already_clicked
2. `Can you spot the scam in this delivery text?` — spot_the_trap_quiz
3. `It started with a fake support popup.` — true_scam_story
4. `The fake logo is not the trap.` — scam_breakdown
5. `Entered your password on a fake page? Do this first.` — already_clicked

## Review/upload report requirements

For every TrueTraceShorts review or YouTube upload report, include:

- MP4 / media path
- YouTube title
- YouTube description
- duration
- approval command when not yet uploaded
- private upload status / Studio link when uploaded
- TikTok caption/description text

TikTok rule: provide the TikTok caption in review/upload reports, but do not upload to TikTok unless the user explicitly approves a TikTok upload. YouTube remains primary.

## Analytics/audit fields

Upload audits and candidate metadata should preserve:

- format_type
- hook_type
- viewer_state
- cta_type
- duration_class
- first_frame_scam_label
- website_target

This lets later analytics compare formats instead of only individual topics.

## Review/upload report requirements

For every TrueTraceShorts review or upload report, include:

- MP4 path/media attachment
- title
- YouTube description
- TikTok caption/description text, even though TikTok upload remains explicit-only
- approval command when not uploaded yet
- duration
- relevant hashes
- QA status

Do not silently omit TikTok copy just because YouTube is the primary platform. The user wants TikTok caption text in review/upload reports, but TikTok publishing remains manual/explicit.

## Recovery wording preference

For `already_clicked` / recovery formats, prefer the no-shame line:

```text
You didn’t do anything wrong.
```

Avoid:

```text
You are not stupid.
```

The latter can sound defensive even when well-intended.