<aside> 💡 Use case: give every agent the same knowledge of your brand, kept in plain files you can read and change. Edit a file and the whole team works differently on its next run.

</aside>

What Brand OS is

<aside> 🧠 Brand OS is one folder in your project, brand-os/, with 27 Markdown templates in 8 folders. It holds what a new hire would need on day one:

Why the agents read files instead of one long prompt

<aside> 📄 Three reasons:

The folder

brand-os/
├── README.md              how the folder works
├── brand-brain/           voice-guide.md, positioning.md, messaging-bank.md, tone-rules.md
├── signals-seo/           keyword-map.md, serp-rules.md, ranking-targets.md, tracking-setup.md
├── content/               content-calendar.md, brief-templates.md, hook-bank.md, seo-checklist.md
├── creative/              visual-specs.md, asset-library.md, video-scripts.md
├── social/                channel-playbooks.md, posting-schedule.md, hashtag-rules.md
├── reputation/            gbp-response.md, review-flow.md, mentions-rules.md
├── conversation/          faq-library.md, routing-rules.md, auto-reply-scripts.md
└── reporting/             kpi-model.md, margin-rules.md, attribution.md

Which department reads which folder

Department Agent file Reads
The brain orchestrator.md every folder
Search visibility search-visibility.md signals-seo/
Market radar market-radar.md signals-seo/, brand-brain/
Content engine content-engine.md content/, brand-brain/
Creative studio creative-studio.md creative/, brand-brain/
Publishing & social publishing-social.md social/
Reviews & reputation reviews-reputation.md reputation/, brand-brain/
Leads & conversations leads-conversations.md conversation/
Results & ROI results-roi.md reporting/

How Brand OS and owner/ fit together

<aside> 🧑‍💼 The owner/ folder holds the four things only you set: brand voice, budget cap, approval bar and positioning. Agents can read those files but never change them. Brand OS is the working detail underneath. If the two ever disagree, owner/ wins and the agent that noticed writes the conflict to queue/needs-your-ok.md.

</aside>

Fill these five first

<aside> ✅ You do not need all 27 templates to get a first run. Fill these five and the Content engine can draft:

  1. brand-brain/voice-guide.md: how you sound
  2. brand-brain/tone-rules.md: what you never say
  3. brand-brain/positioning.md: what you stand for
  4. brand-brain/messaging-bank.md: the claims you can prove
  5. content/content-calendar.md: one row with the status ready

Then fill the length line in content/brief-templates.md for the one channel you start with. Fill the other folders as you switch on each department.

</aside>

How to fill a template

<aside> ✏️ Every template uses the same three marks:

Any [FILL IN] left in place tells the agents "unknown". They stop and ask in queue/needs-your-ok.md instead of guessing. Every number in these templates is yours to set: the files never ship with a threshold chosen for you.

</aside>

How to keep it current

<aside> 🔁 - Every week: drop the new exports into brand-os/signals-seo/, then approve or delete the idea and proposed rows the agents added.

The README

<aside> 📋 Copy this into brand-os/README.md. It is the first file the orchestrator reads, and it tells every agent the rules of the folder.

</aside>

# Brand OS

Brand OS is the folder every agent reads before it works. It holds what the team needs to know about your brand:
how you sound, what you may claim, what to watch, how to reply and what counts as a result.
Change a file here and every agent works differently on its next run. You never edit a prompt.

## The rules of this folder
1. **Agents read, you write.** Agents never change a rule in this folder. The only edits an agent may make are new rows
   in tables marked "Agents may add rows", and every such row starts with the status `idea` or `proposed` until you approve it.
2. **owner/ wins.** If anything here disagrees with owner/brand-voice.md, owner/budget-cap.md, owner/approval-bar.md
   or owner/positioning.md, the owner file wins. The agent that spots the conflict writes it to queue/needs-your-ok.md.
3. **[FILL IN] means unknown.** An agent that needs a value still marked [FILL IN] does not guess. It stops and asks
   in queue/needs-your-ok.md.
4. **Exports land in the folder that reads them.** Weekly exports from your tools go in brand-os/signals-seo/ unless
   tracking-setup.md says otherwise, named <tool>-<what>-YYYY-MM-DD.csv.
5. **No keys, no passwords.** Nothing secret goes in this folder.

## The folders
brand-os/
├── README.md              this file
├── brand-brain/           voice-guide.md, positioning.md, messaging-bank.md, tone-rules.md
├── signals-seo/           keyword-map.md, serp-rules.md, ranking-targets.md, tracking-setup.md
├── content/               content-calendar.md, brief-templates.md, hook-bank.md, seo-checklist.md
├── creative/              visual-specs.md, asset-library.md, video-scripts.md
├── social/                channel-playbooks.md, posting-schedule.md, hashtag-rules.md
├── reputation/            gbp-response.md, review-flow.md, mentions-rules.md
├── conversation/          faq-library.md, routing-rules.md, auto-reply-scripts.md
└── reporting/             kpi-model.md, margin-rules.md, attribution.md

## Who reads what
| Agent | Reads |
|---|---|
| orchestrator | every folder |
| search-visibility | signals-seo/ |
| market-radar | signals-seo/, brand-brain/ |
| content-engine | content/, brand-brain/ |
| creative-studio | creative/, brand-brain/ |
| publishing-social | social/ |
| reviews-reputation | reputation/, brand-brain/ |
| leads-conversations | conversation/ |
| results-roi | reporting/ |

## Fill these five first
1. brand-brain/voice-guide.md
2. brand-brain/tone-rules.md
3. brand-brain/positioning.md
4. brand-brain/messaging-bank.md
5. content/content-calendar.md (one row with the status `ready`)
In content/brief-templates.md, fill the length line for the one channel you start with.
That is enough for a first draft. Fill the other folders as you switch on each department.

## Keeping it current
- Once a week: drop the new exports in, read queue/needs-your-ok.md, approve or delete rows marked `idea` or `proposed`.
- Once a month: re-read tone-rules.md and messaging-bank.md. Retire any claim that is no longer true.
- Whenever you change your mind: edit the file. The next run uses it.
- Last reviewed: [FILL IN: date you last read this whole folder]