<aside> 💡 Use case: write down how you sound, what you stand for and what you can prove, once. Every agent that writes or replies reads it before it starts.
</aside>
<aside>
👀 Who reads this folder: Content engine, Creative studio, Market radar, Reviews & reputation, and the orchestrator. The Content engine's voice check runs every draft against tone-rules.md.
</aside>
<aside> 🗣️ Controls: how every piece of writing sounds, and how that shifts from channel to channel.
How to fill it: start with three to five words for your voice, then explain each one with a sentence that sounds right and one that sounds wrong. The most useful part is section 7: paste real things you wrote that sound exactly like you.
Save as brand-os/brand-brain/voice-guide.md.
</aside>
# Voice guide
> Read by: content-engine, creative-studio, market-radar, reviews-reputation.
> If this file and owner/brand-voice.md disagree, owner/brand-voice.md wins.
> Fill it in plain words. If you cannot describe a trait, paste a real example instead.
## 1. We sound like
[FILL IN: three to five words that describe how you sound]
Example (Northwind Coffee): warm, plain-spoken, a little nerdy about brewing.
## 2. What each trait means
| Trait | What it means | Sounds like this | Never like this |
|---|---|---|---|
| [FILL IN: trait] | [FILL IN: one line] | [FILL IN: a sentence that shows it] | [FILL IN: a sentence that breaks it] |
| [FILL IN: trait] | [FILL IN: one line] | [FILL IN] | [FILL IN] |
| [FILL IN: trait] | [FILL IN: one line] | [FILL IN] | [FILL IN] |
Example row (Northwind Coffee): | Plain-spoken | Short words, no jargon | "Grind it right before you brew." | "Unlock an elevated extraction experience." |
## 3. Who we are talking to
- Reader: [FILL IN: who reads you, in one sentence]
- What they already know: [FILL IN]
- What they want from you: [FILL IN]
- What makes them stop reading: [FILL IN]
Example (Northwind Coffee): Reader: people who brew coffee at home and want it to taste like the cafe.
## 4. Point of view
- We write as: [FILL IN: "we" for the brand, or "I" for a named founder]
- We speak to the reader as: [FILL IN: "you", by role, or another form]
## 5. Sentence style
- Sentence length: [FILL IN: short, mixed, long]
- Contractions (we're, it's): [FILL IN: yes or no]
- Emojis: [FILL IN: never, or only on the channels named in social/channel-playbooks.md]
- Headings: [FILL IN: sentence case or Title Case]
- Spelling: [FILL IN: US English or UK English]
- Words we always spell one way: [FILL IN: product names, brand name]
## 6. How the voice shifts by channel
| Channel | Shift from the base voice |
|---|---|
| Articles | [FILL IN] |
| LinkedIn | [FILL IN] |
| Instagram | [FILL IN] |
| Facebook | [FILL IN] |
| TikTok | [FILL IN] |
| Newsletter | [FILL IN] |
| Review replies | [FILL IN] |
| Chat replies | [FILL IN] |
Example (Northwind Coffee): Review replies: calmer, no jokes, signed with a first name.
## 7. Samples that sound right
Paste real pieces you wrote that sound exactly like you. Agents copy the rhythm, never the facts.
1. [FILL IN: paste a real post or paragraph]
2. [FILL IN]
3. [FILL IN]
## 8. Samples that sound wrong
1. [FILL IN: paste something that is not you, and say why in one line]
2. [FILL IN]
<aside>
🚫 Controls: the pass or fail voice check. One broken rule sends a draft to queue/held-for-voice-review.md with the rule number named.
How to fill it: write each rule as one line you could check with a yes or a no. Put banned words in "Never say" with the plain word to use instead. Keep the three "Never do" rules that ship in the file: they stop invented numbers, unproven claims and tagging people without permission.
Save as brand-os/brand-brain/tone-rules.md.
</aside>
# Tone rules
> Read by: content-engine (the voice check), creative-studio, market-radar, reviews-reputation.
> The content engine checks every draft against this file. One broken rule sends the draft to
> queue/held-for-voice-review.md with the rule number named, for example "failed N3".
> Write each rule as one line that a reader could check with a yes or a no.
## Always
| # | Rule | How to check it |
|---|---|---|
| A1 | [FILL IN: something every piece must do] | [FILL IN: what a pass looks like] |
| A2 | [FILL IN] | [FILL IN] |
| A3 | [FILL IN] | [FILL IN] |
Example row (Northwind Coffee): | A1 | Say what the reader gets in the first line | The first line names a benefit |
## Never say
Words and phrases that fail the check on sight.
| # | Never say | Say instead |
|---|---|---|
| N1 | [FILL IN: word or phrase] | [FILL IN: your plain version] |
| N2 | [FILL IN] | [FILL IN] |
| N3 | [FILL IN] | [FILL IN] |
| N4 | [FILL IN] | [FILL IN] |
| N5 | [FILL IN] | [FILL IN] |
Example row (Northwind Coffee): | N1 | "elevate your morning ritual" | "better coffee at home" |
## Never do
| # | Rule |
|---|---|
| D1 | Invent a number, a customer name, a quote or a review. |
| D2 | Make a claim that is not in messaging-bank.md. |
| D3 | Tag or name a real person without their permission. |
| D4 | [FILL IN: your own rule] |
| D5 | [FILL IN] |
Example row (Northwind Coffee): | D4 | Name a competitor to make fun of them |
## Topics we do not touch
| Topic | What to do instead |
|---|---|
| [FILL IN: topic] | [FILL IN: leave it out, or hand it to the owner] |
| [FILL IN] | [FILL IN] |
Example row (Northwind Coffee): | Health claims about caffeine | Leave it out |
## Sensitive moments
When news, a complaint or a crisis makes the usual tone wrong:
- What pauses scheduled posts: [FILL IN: the kind of event that pauses everything]
- Who decides when posting starts again: [FILL IN: name]
- Tone in a reply to an upset customer: [FILL IN]
## Pass or fail
A draft passes only when every Always rule holds and no Never say or Never do rule is broken.
The voice check reports `pass`, or `fail` plus the rule numbers it broke. A failed draft is never quietly fixed.
<aside> 🎯 Controls: what you stand for, who you are for, and who you are compared with. Market radar uses the competitor list to sort what it finds.
How to fill it: write the one paragraph first using the sentence shape given. Every difference you list must point at a proof point in messaging-bank.md. The short signed-off version lives in owner/positioning.md, and that file wins if the two disagree.
Save as brand-os/brand-brain/positioning.md.
</aside>
# Positioning
> Read by: content-engine, creative-studio, market-radar, reviews-reputation.
> owner/positioning.md holds the version you signed off. This file is the working detail behind it.
> If the two disagree, owner/positioning.md wins.
## 1. The one paragraph
[FILL IN: For <who>, <brand> is the <category> that <main benefit>, because <reason to believe>. Unlike <main alternative>, we <the difference>.]
Example (Northwind Coffee): For people who brew at home, Northwind Coffee is the small-batch roaster that prints the roast date on every bag, so you always know how fresh it is. Unlike supermarket coffee, we roast to order.
## 2. Who it is for
- Best-fit customer: [FILL IN: one sentence]
- Also buys from us: [FILL IN]
- Not for: [FILL IN: who you do not want to attract]
## 3. The problem we solve
[FILL IN: the problem in the customer's own words]
Example (Northwind Coffee): "The beans I buy taste flat and I can't tell how old they are."
## 4. Category
- We call what we sell: [FILL IN: the category in the words customers search for]
- We never call it: [FILL IN]
## 5. What makes us different
Every difference needs a proof point in messaging-bank.md. No proof, no difference.
| Difference | Proof point ID (messaging-bank.md) | Who cares most |
|---|---|---|
| [FILL IN] | [FILL IN: e.g. P1] | [FILL IN] |
| [FILL IN] | [FILL IN] | [FILL IN] |
| [FILL IN] | [FILL IN] | [FILL IN] |
## 6. What the customer compares us with
| Alternative | Why people choose it | Why they would switch to us |
|---|---|---|
| [FILL IN: a competitor, a habit, or doing nothing] | [FILL IN] | [FILL IN] |
| [FILL IN] | [FILL IN] | [FILL IN] |
Example row (Northwind Coffee): | Supermarket beans | Cheap and on the way home | They want to know how fresh the coffee is |
## 7. Competitors we watch
Market radar and reviews-reputation use this list to sort mentions.
| Competitor | Website | Social handles | What they are known for |
|---|---|---|---|
| [FILL IN] | [FILL IN] | [FILL IN] | [FILL IN] |
| [FILL IN] | [FILL IN] | [FILL IN] | [FILL IN] |
## 8. What we will never position as
- [FILL IN: e.g. the cheapest option]
- [FILL IN]
<aside> 🏦 Controls: every claim an agent is allowed to make. If a claim is not in this file, no agent makes it.
How to fill it: add your proof points first (the review, the photo, the figure, and where it lives), then write each claim and point it at its proof. Only add customer quotes you have permission to use. When a claim stops being true, move it to "Retired claims" so it never comes back.
Save as brand-os/brand-brain/messaging-bank.md.
</aside>
# Messaging bank
> Read by: content-engine, creative-studio, market-radar, reviews-reputation.
> Every claim an agent may make lives in this file. If a claim is not here, no agent makes it.
> A number goes in only if you can name where it came from.
## 1. Core message
[FILL IN: the one sentence you want every customer to remember]
Example (Northwind Coffee): Fresh coffee at home, with the roast date on every bag.
## 2. Message pillars
Three to five themes everything you publish ladders up to. The content calendar tags each item with one.
| Pillar | What we say about it | Proof point IDs |
|---|---|---|
| [FILL IN] | [FILL IN: one or two sentences] | [FILL IN: e.g. P1, P2] |
| [FILL IN] | [FILL IN] | [FILL IN] |
| [FILL IN] | [FILL IN] | [FILL IN] |
Example row (Northwind Coffee): | Freshness | You always know when your coffee was roasted | P1 |
## 3. Approved claims
| ID | Claim (exact wording) | Proof point ID | Use on | Valid until |
|---|---|---|---|---|
| C1 | [FILL IN] | [FILL IN] | [FILL IN: all channels, or a list] | [FILL IN: date, or "no end"] |
| C2 | [FILL IN] | [FILL IN] | [FILL IN] | [FILL IN] |
| C3 | [FILL IN] | [FILL IN] | [FILL IN] | [FILL IN] |
Example row (Northwind Coffee): | C1 | Every bag shows its roast date | P1 | all channels | no end |
## 4. Proof points
| ID | Proof | Type | Where the proof lives | OK to quote publicly |
|---|---|---|---|---|
| P1 | [FILL IN] | [FILL IN: review, figure, award, press, photo, demo] | [FILL IN: file, link or folder] | [FILL IN: yes or no] |
| P2 | [FILL IN] | [FILL IN] | [FILL IN] | [FILL IN] |
| P3 | [FILL IN] | [FILL IN] | [FILL IN] | [FILL IN] |
Example row (Northwind Coffee): | P1 | Photo of the bag label with the roast date | photo | Google Drive: /brand/labels | yes |
## 5. Customer words we may quote
Only quotes you have permission to use. Copy them exactly.
| Quote | Who said it (as they agreed to be named) | Where it came from | Permission given on |
|---|---|---|---|
| [FILL IN] | [FILL IN] | [FILL IN] | [FILL IN: date] |
## 6. Offers and calls to action
| CTA wording | Where it points | Use on | Live from | Live until |
|---|---|---|---|---|
| [FILL IN] | [FILL IN: URL] | [FILL IN] | [FILL IN] | [FILL IN] |
| [FILL IN] | [FILL IN] | [FILL IN] | [FILL IN] | [FILL IN] |
Example row (Northwind Coffee): | Try the sampler | northwind.example/sampler | Instagram, newsletter | [date] | [date] |
## 7. Names we spell one way
| Thing | Exact spelling |
|---|---|
| Brand | [FILL IN] |
| Product | [FILL IN] |
| Product | [FILL IN] |
## 8. Retired claims
Never use these again. Keep them here so no agent brings them back.
| Claim | Retired on | Why |
|---|---|---|
| [FILL IN] | [FILL IN] | [FILL IN] |
<aside> 👉 Next: /signals-seo
</aside>