# Shared show profile

Use this as the structure for `SHOW-PROFILE.md`. Keep the file short enough to read at the start of each task. Link to large source files and logs in the user's workspace. Do not copy every transcript into it.

Fill known fields from existing material. Mark a guess as proposed. Mark a missing fact as unknown. The profile should help work start; it should not block it.

```markdown
# Show profile

Updated: [date]
Show: [name]
Working folder: [path, if known]
Channels: [main show and any clip accounts]

## Audience and promise
Viewer: [person and situation]
Need: [what brings them to this show]
Promise: [what they can expect each episode]
Proof: [what in the show supports the promise]
Topics in scope: [core topics and useful wider frames]
Topics outside scope: [boundaries]
Goal: [full-episode viewing, listener growth, or another chosen goal]
Status: [confirmed choices and proposed choices]

## Format and voice
Format: [interview, solo, panel, narrative, or mix]
Usual length and release pace: [known values]
Tone: [plain description with an example]
Host role: [what the host adds]
Audience language: [words viewers use]
Claims to avoid: [unsupported promises or unwanted phrasing]

## Title and image rules
Title patterns: [useful patterns with examples]
Guest names and proof: [placement and checks]
Images: [source and acceptable edits]
Faces and framing: [values]
Color treatment: [values]
Type and text: [font, weight, word range, position]
Base layout: [description or asset path]
Exceptions: [when and why]
Clip format cues: [how each format stays recognizable]
Status: [observed, confirmed, or proposed for each rule]

## Reference episodes
| Episode and date | Title | Image or asset path | Why keep it | Result and age measured |
| --- | --- | --- | --- | --- |

Keep 5 to 10 useful examples. Include a weak result if it teaches a lesson.

## Clip plan defaults
Platforms and accounts: [where the team posts]
Job for each format: [discovery, depth, or existing fans]
Edit budget: [time or number of finished clips]
Release pace: [current habit or proposed trial]
Route to full episode: [link feature or path]
Limits: [assets, guest terms, or topics that need care]

## What the team has learned
| Date | Lesson | Evidence or log | Status | Recheck when |
| --- | --- | --- | --- | --- |

Use status: guess, one episode, or repeated pattern.

## Open questions
[Only choices that affect the next task]

## Change notes
[Date, what changed, and why]
```

When another skill finds a new result, add a dated lesson. Keep the current rules until the evidence or the user supports a change. A test winner for one guest does not rewrite the whole show.

Do not guess private numbers from public views. For each result, keep its time window and source. If a number is no longer comparable because the format or view definition changed, mark that limit.