skills/juicylucy-setup/references/brand-template/compliance-overlay.md

# <Brand> — compliance overlay

Brand-specific prohibitions, **over and above** whatever the platform forbids.

The distinction matters and is easy to get wrong. "Scarcity that isn't tied to a
real time-bound promotion is deceptive-practice territory" is true for every
advertiser — that is platform policy and belongs with the engine's policy
reference (the `ad-platform` skill's rejection taxonomy). "Never use a
free-trial CTA" reads like compliance but would change under a different
brand, so it is a **brand** rule and lives here.

Everything below would change if the brand changed. Nothing below is a
restatement of what the product is — that is
[`product-truth.md`](./product-truth.md), and it is the only place scope is
asserted.

## Hard rules

These rules govern copy the engine authors. Copy the user supplies verbatim is
built as given, and every conflict with a rule here is named in the reply with
a compliant alternative — the engine's copy gate owns that precedence
(`video-ad-production` `references/ad-copy.md` § When this gate blocks, and
when it only reports).

**<Never … >.** <The rule, the phrasings it covers in any language, and the
neutral alternative to use instead.>

**<Never claim … >.** <A capability the product does not have; point at
product-truth § What it is not.>

**No absolutes or guaranteed outcomes.** Avoid "never", "always",
"guaranteed", "100%", and any guaranteed result claim. <Keep this one; it is
brand policy for almost every product and the platform's too.>

**No fabricated numbers.** Statistics, counts and testimonials must be real,
sourced, and approved. Concrete real numbers are encouraged; invented ones are
the fastest route to a rejection.

**No fake urgency.** No fake scarcity, no evergreen countdowns, no "this week
only" unless a genuine time-bound promotion is actually running.

## Rejection classes this brand has met

<Once an ad has been rejected: the platform's stated reason, the phrasings
that triggered it, and the rule that follows. Date each entry and point at the
log in `history/`. Until then, delete this section — an empty heading reads as
a rule.>

## Why this file exists

<When the first rejection happens, record it here in two sentences: what was
rejected, what the emotional core was that survived, and what separated the
two. That is the sentence a future author needs.>