# TrueTraceShorts Strategic Neuausrichtung — Digital Red Flags

This reference is authoritative for TrueTraceShorts / AutoShortsBot content strategy after the fake-invoice proof short. It supersedes AI-workflow-first positioning.

## Official position

**TrueTraceShorts — Digital Red Flags**

**Scam Self-Defense for Normal People**

Core line:

> One screen. One red flag. One safer move.

German internal line:

> Ein normaler Screen. Ein gefährlicher Hinweis. Eine sichere Handlung.

Channel promise:

> I show you the one red flag before you click, pay, scan, or log in.

## Deprioritized as main formats

Do not lead with these as the primary channel identity:

- AI workflow tips
- prompt engineering
- AI tool reviews / top 5 tools
- abstract productivity mechanisms
- beautiful AI explainers without visible viewer pain
- generic cybersecurity news
- hacker tactics / OSINT / dark-web explainers
- VPN comparisons
- technical attack instructions

AI/workflow content may remain a later specialist/legacy format, not the core promise.

## Audience stance

Externally: **Digital self-defense for normal people.**

Do not brand it as “cybersecurity for boomers”. Internally, content should be boomer-safe: simple wording, large text, concrete examples, no jargon, one action.

Target viewers:

- normal smartphone and internet users
- parents and teenagers
- workers and teams
- small business owners
- families
- people who want to protect parents, partners, colleagues, or friends

Psychological target:

> “That could have happened to me or my family.”

## Language style

Use simple English for final social videos. Aim for B1/B2. Short, everyday sentences.

Good:

- “This message wants you to hurry.”
- “Don’t tap the link.”
- “Open the app yourself.”
- “If the payment route changed, verify it another way.”
- “If it makes you hurry, slow down.”

Bad:

- “This phishing attempt leverages urgency-based social engineering to exploit cognitive load.”
- “Validate the authenticity of the communication channel before initiating a transactional flow.”

Plain replacements:

- “validate communication channel” → “check it another way”
- “credential harvesting” → “stealing your login”
- “MFA prompt fatigue” → “a login prompt you did not start”

## Default video formula

Every video should default to:

1. **0–2s:** Visible trap + hook.
2. **2–7s:** Why it feels normal.
3. **7–15s:** The one red flag.
4. **15–24s:** The safer move.
5. **24–30s:** Screenshot checklist.
6. **30–34s:** Memorable rule + soft CTA.

Before rendering, candidate must answer:

- What normal screen does the viewer see?
- What concrete red flag is visible?
- Is the problem visible in second 1 without audio?
- What could happen to the viewer?
- What is the one safer move?
- Can someone send it to parents, partner, colleagues, or team?
- Is there a save/screenshot reason?
- Is the language simple enough for average users?
- Is it useful without tech knowledge?

If unclear: do not render.

## Primary content pillars

1. **Text & Delivery Scams** — package SMS, customs/toll fee, short links, fake tracking.
2. **Login & Account Traps** — fake bank/Microsoft/Google/Apple login, reset, account closure, login prompt not started.
3. **Payment & Invoice Red Flags** — fake invoice, changed payment route, vendor bank change, CEO request, QR payment trap.
4. **Marketplace & Buyer Scams** — off-platform buyer, fake shipping link, escrow, overpayment, courier pickup.
5. **Family & Emotion Scams** — “Hi mom new number”, emergency money, grandparent scam, wrong-number scam, simple AI voice warning.
6. **Fake Support / Popup Scams** — infected-device popup, call support, fake antivirus, browser lock, remote access.
7. **Password / Account Safety Basics** — password reuse, password managers, MFA basics, recovery email risk.
8. **Job / Side-Hustle Scams** — fake recruiter, task scam, pay to get paid, remote job deposit, crypto onboarding trap.

## Official series

1. **One Screen. One Red Flag.** — normal screen, dangerous detail, safe action.
2. **Send This To Your Parents** — simple family-safe clips without condescension.
3. **Before You Click** — links, SMS, QR, login, popups.
4. **Money Move Red Flags** — payments, invoices, bank routes, QR, marketplaces.
5. **Account Trap** — login, password, MFA, fake reset, account closure.

## Visual rules

Default: screen/mockup-led.

Prefer:

- phone screen
- SMS
- email
- invoice
- chat
- popup
- login
- QR situation
- marketplace chat
- fictional deterministic mockups

Avoid:

- abstract glass clouds
- pretty but empty AI images
- generic laptop B-roll
- funnel/ring metaphors
- PowerPoint-like explainers
- unnecessary Wan/I2V/T2V

## Scam-screen safety

Scam screens should be deterministic/renderer-owned whenever the text or UI matters.

Never use real:

- brands/logos
- phone numbers
- bank data / IBANs
- domains except safe placeholders like `example.com`
- QR codes / barcodes
- invoice IDs / company details
- real persons or companies

Do not provide operational scam instructions. Use cautious language:

- “A common red flag is...”
- “Before you pay, check...”
- “Verify through another channel.”
- “This does not catch everything, but it gives you a safer next step.”

## AI-image policy for this channel

Use this safe pattern:

```text
AI image layer = text-free atmosphere/background/keyframes
Deterministic renderer = SMS/email/invoice/login/chat UI, labels, facts, captions, claims
```

AI images may be used for premium atmosphere when they contain no meaningful text/data. Do not let AI freely invent scam documents, bank pages, fake invoices, or fake login screens.

QA AI backgrounds and reject if they contain pseudo-text, logo-like marks, QR/barcodes, people/hands when not desired, bank/payment/account-like details, or busy composition.

## Screenshot checklist

End-card should usually be included:

- max 3 points
- large text
- 1.5–3 seconds visible
- mobile-safe
- no paragraphs
- title like “SAVE THIS” or “Quick check”

Example:

```text
SAVE THIS

Delivery text?
Check:

Small fee?
Short deadline?
Suspicious link?

Open the app yourself.
```

## Scoring priorities

- viewer pain in first second
- screen clarity without audio
- red flag clarity
- safe move clarity
- family/share potential
- screenshot checklist value
- beginner language
- mockup safety
- no fearmongering
- pretty-empty-visual blocker

Block if beautiful but problem-free, too jargon-heavy, red flag unclear, no safer next step, or visually generic.

## Next candidate order

After the fake-invoice proof short:

1. `delivery-sms-trap-35s`
   - Hook: “This delivery text is designed to make you panic.”
   - Takeaway: “If it makes you hurry, slow down.”

2. `fake-support-popup-call-now-30s`
   - Hook: “If a website tells you to call support, stop.”
   - Takeaway: “Real support does not hijack your screen.”

3. `marketplace-buyer-off-platform-30s`
   - Hook: “The buyer is not buying. They are moving you off-platform.”
   - Takeaway: “Keep the chat and payment inside the platform.”

4. `fake-qr-bank-login-page-35s`
   - Hook: “The QR code was not the problem. The page after it was.”
   - Takeaway: “If money or login is involved, open the app yourself.”

5. `password-reuse-domino-30s`
   - Hook: “One leaked password does not stay on one website.”
   - Takeaway: “One account, one password.”

## Session-specific render lesson: Delivery SMS Trap

The user approved the Delivery SMS concept, then requested the defined high-quality AI image standard.

Correct workflow:

1. Build deterministic proof preview first to validate concept and readability.
2. Generate a small AI background batch only for atmosphere.
3. QA contact sheet before rendering.
4. Discard unsafe/generated background artifacts.
5. Keep SMS/app/checklist/captions deterministic.
6. Re-render full 1080x1920 with `setsar=1,setdar=9/16` and extract QA frames.

In this session:

- 3 AI backgrounds were generated with `gpt-image-2-high`.
- 2 were used.
- 1 was discarded due to barcode-like package-label marks.
- Deterministic SMS used fictional `example.com`.
- Final MP4 was probed as `1080x1920`, `SAR 1:1`, `DAR 9:16`.

If TTS word-boundary events are absent, manually derive phrase/word timing from sentence timings and create active-word ASS subtitles rather than dropping captions.