# TrueTraceShorts hook-retention test cycle

Use this for the next 10 TrueTraceShorts / Everyday Red Flags shorts after the 2026-06 YouTube Analytics CSV review showed most viewers swipe away in the first seconds and average view duration is only about 3–4 seconds.

## Objective

Optimize for viewed-vs-swiped, not for cinematic beauty.

Targets:
- Viewed rate: at least 25–35%.
- Average view duration: at least 8–12 seconds.
- Runtime for this test cycle: 22–35 seconds, usually 25–30 seconds.

## Priority order

1. First-frame clarity.
2. Immediate danger.
3. One red flag.
4. One safer move.
5. Shorter runtime.

## Hard format rules for the next 10 shorts

- No 60s story video as default.
- No slow setup.
- No logo/brand intro.
- No generic cinematic opening.
- The first frame must show the scam immediately.
- A silent viewer must understand the scam category within 1 second.
- Use one normal screen, one red flag, one safer move.

## Timing structure

```text
0.0–0.7s  Scam-screen large and readable
0.7–2.0s  Hook with concrete danger
2.0–6.0s  Why it feels real
6.0–14.0s One red flag
14.0–24.0s Safer move
24.0–30.0s Memory rule / Follow / Website guide
```

## Visual rules

Premium AI keyframes remain mandatory, but the screen must carry the threat.

Allowed and encouraged:
- High-quality AI image base with phone, laptop, chat, popup, banking/app screen, marketplace/chat screen, etc.
- Renderer-owned scam-screen text filled into the screen area.
- Large readable fake scam text on the screen.
- Generic safe fake data.
- Static active-word captions without box.

Forbidden:
- PowerPoint graphics.
- Diagrams.
- Arrows, circles, explainer boxes, focus lines.
- `example.com` as final visible look.
- Generic cyber clouds.
- Abstract metaphors.
- Slow buildup without visible danger.
- Real brands, domains, phone numbers, bank data, card data, QR codes, or personal data.

## Hook rule

Hooks must state the concrete danger.

Use:
- `This small fee can expose your card.`
- `If you call this number, the scam starts.`
- `A real bank will not ask you to read this code.`
- `If this is your child, call the old number.`
- `The buyer is not buying. They want you off-platform.`

Avoid:
- `This delivery text is designed to make you panic.`
- `It started with a fake support popup.`
- `This login page looks right.`

## GO_NEXT_SHORT rule during this cycle

When the user says `GO_NEXT_SHORT`, suggest only one of these short hook-test candidates plus two alternatives:

1. Small delivery fee — hook: `This small fee can expose your card.`
2. Fake support number — hook: `If you call this number, the scam starts.`
3. Bank code — hook: `A real bank will not ask you to read this code.`
4. Hi Mom — hook: `If this is your child, call the old number.`
5. Marketplace — hook: `The buyer is not buying. They want you off-platform.`

Do not suggest topics outside Scam / Online Safety.

## OK_PRODUCE requirements during this cycle

Produce:
- 25–30s video unless the concept absolutely needs 31–35s.
- Premium KI image basis.
- Renderer-owned scam-screen text.
- Gianna voice.
- Static active-word captions without box.
- YouTube title + description.
- TikTok caption text only, no TikTok API.
- Website guide link.
- After a private YouTube upload succeeds, immediately update the website companion page and set the visible `videoUrl` to the real Shorts link; the user manually switches the video public right away.
- Hash-bound private YouTube approval command.

## Channel hygiene

Mark old off-topic / non-scam / non-online-safety videos as `recommend_unlist_or_private` in local registries or audit notes when possible. Do not use YouTube read/write scopes for this; upload-only policy still applies. The user will handle public/private changes manually in Studio.