kai-brandlisted

# /kai-brand — A Position Only This Brand Can Claim ## Objective A brand positioning system the team can write from tomorrow: a positioning statement anchored in white space no competitor owns, three value-prop pillars with proof, voice and tone rules with do/don't examples, a differentiation map against named competitors, and a shortlist of taglines with the reasoning for each. The white-space call is the load-bearing judgment. A position every competitor could also claim is a description, not a position. ## Done when Work type `strategy-plan` — floor **E3/C3/O1** (`harness/eco-floors.yaml`). - **E3** — a named human approved the exact messaging document. - **C3** — `banned_word_check` clean on every deliverable, Four U's ≥ **12/16** on the positioning statement (`python scripts/quality_gates/four_us_score.py <file>`), and someone other than the author read the package end to end. - **O1** — the package names the first asset that will be rewritten against it (site hero, sales deck, ad set) with an owner and a date. Positioning nobody rewrites anything with is not finished. ## Constraints - **Read `MARKETING.md` from the project root first.** It carries product, ICP, value prop, monetization, voice, current channels, and competitive landscape. If it does not exist, build it from the codebase — CLAUDE.md, README.md, PROJECT.md, package.json, landing pages, email/ad/analytics config — using the template from `/kai-email-system`, and confirm the draft. Do not ask the use