Demo brandnot a real client

Demo — not a real clientclaude-opus-5 · 2026-08-14Module 2 · section 10.4 · 994 words

Demo run 04 — Problem–solution

demo runDoc type

demoStatus

Not flaggedFact-check

neverLast verified

DEMO BRAND

See README.md.

What this run demonstrates: a claim made by structure rather than by words — the hardest kind for a vocabulary check to catch, and the reason claim-guard has a semantic pass at all.

Step 1 — Intake read, format checked

Available: there is a specific physical moment of friction on file (scraping), a recorded resolution, and no barred claim standing in the way.

One caution logged before writing. Sable's BV-1 says never sound like a crypto ad, and problem–solution is the format closest to an advert. The register risk is live here in a way it isn't in the other three.

Step 2 — The brief, as filled

Prompt the brief, as filledvia script-from-intake

Write a 20-second problem-solution script in 5 beats.

PRODUCT
  Sable 24cm skillet — a mid-price steel pan sold direct. Hand wash only.
  What it actually fixes: eggs sticking to a worn pan

THE PROBLEM
  Moment of friction: scraping stuck egg off a pan with a spatula edge
  Who has it: a renter in their late twenties who cooks four nights a week in a
    kitchen they can't renovate
  Why they put up with it: the pan still technically works, and replacing a pan
    that isn't broken feels like an indulgence

WHAT I CAN HONESTLY CLAIM
  It fixes: eggs released on the first try, cold pan, a smear of oil, no scraping
  It does not fix: anything about durability, heat-up time, or long-term coating
    performance — none of that was tested

BRAND VOICE
  Never say: game-changer, obsessed, literally, honestly, elevate, foodie,
             girl math
  Barred claims: non-stick forever; dishwasher safe (contract requires hand wash
             only in all creative); clinically proven / lab tested; any
             comparison naming a competitor product
  Never sound like: a wellness cult, a crypto ad, a hotel breakfast menu

CONSTRAINTS
  - Beat 1 has no dialogue — it must read as a picture
  - Beat 4 is the same shot as beat 1, described identically
  - One escalation only in beat 2
  - The product enters in beat 3 without being introduced or held up
  - No claim beyond WHAT I CAN HONESTLY CLAIM > "It fixes"
  - The button in beat 5 is under 7 words and is not a slogan
  - No exclamation marks anywhere

Return as: BEAT n — [dialogue or "no dialogue"] / [what's on screen]. Nothing else.

Step 3 — Output, as generated

Output as generatedclaude-opus-5 · 2026-08-14

BEAT 1 — [no dialogue] / spatula edge under stuck egg, close, unhurried
BEAT 2 — [no dialogue] / same shot, next morning, more scraping
BEAT 3 — "New pan." / pan lowered onto the ring, half in frame
BEAT 4 — [no dialogue] / identical shot to beat 1 — egg slides off in one motion
BEAT 5 — "Hand wash only, though." / hand lifts the pan out of frame

The button is the strongest thing in this run and it wasn't asked for. "Hand wash only, though" satisfies three things at once: it is under seven words, it is dry rather than a slogan, and it converts a contractual obligation — the client bars any suggestion of dishwasher use — into the piece's one honest negative. The constraint produced the joke.

Step 4 — `claim-guard`

BLOCKED — none. Vocabulary scan clean on all seven off-limits strings.

UNSUPPORTED — none, literally. FLAGGED — 3, and the first one is the interesting finding.

1. Beat 4 makes a repeatability claim through structure, not words

Check: barred-claim semantic pass. Weighed against: non-stick forever.

Beat 2 establishes next morning. Beat 4 then mirrors beat 1 and resolves it. Read as a sequence, the piece asserts that this is now how every morning goes — a durability claim, made by editing rather than by language. experience.md records the release behaviour over four weeks of use, which supports has kept happening, and explicitly does not support will keep happening (NOT RECORDED: long-term coating performance).

Not blocked. Four weeks of recorded use is real support for a present-tense pattern, and the piece makes no explicit permanence claim. But the creator should know the structure is doing the asserting, because the vocabulary check will never catch this and the next brand may bar it.

2. Beat 3, "New pan." — reads as bought, not gifted. If the pan was gifted, this is a disclosure problem, not a copy problem. Confirm against how the unit was supplied.
3. Disclosure confirmation date, carried forward.

Step 5 — Final script, as shipped

Shippeddemo brand

Final as shippedclaude-opus-5 · 2026-08-14

DISCLOSURE — "Paid partnership with Sable."  / title card + spoken, 0:00–0:02
BEAT 1 — [no dialogue] / spatula edge under stuck egg, close, unhurried
BEAT 2 — [no dialogue] / same shot, next morning, more scraping
BEAT 3 — "Swapped the pan." / pan lowered onto the ring, half in frame
BEAT 4 — [no dialogue] / identical shot to beat 1 — egg slides off in one motion
BEAT 5 — "Hand wash only, though." / hand lifts the pan out of frame

Two changes:

"New pan." → "Swapped the pan." Removes the purchase implication flagged above without adding a word or breaking the beat.
Disclosure beat added, ahead of beat 1, so beat 1 stays dialogue-free.

Finding 1 was accepted, not fixed — the creator read it, agreed four weeks supports a present-tense pattern, and shipped it knowingly. claim-guard allows that. What it doesn't allow is accepting it without noticing, which is why the finding is recorded here rather than resolved silently.

6Provenance

Provenance standing lineattached to everything shipped

Generated 2026-08-14 · claude-opus-5 · via script-from-intake
From: BV-01/SABLE rev. C + experience.md (both DEMO — invented, see README)
Structural repeatability claim flagged by claim-guard's semantic pass;
reviewed and knowingly accepted, not removed
Human edits: "New pan" → "Swapped the pan"; disclosure beat added
Not evidence of any real client, campaign, or result

Your word for it — nothing is tracked automatically.

Source: content/module-2/skills/demo-runs/04-problem-solution.md