<aside> 💡 Use case: set the four things only you should decide. Every agent reads them before acting, and no agent can change them.
</aside>
<aside>
🧑💼 The agents can collect, score, brief, draft and schedule. They cannot decide who you are, what you stand for, what you will spend or what you trust them to ship. Those four decisions live in owner/, and CLAUDE.md makes the folder read-only for every agent.
<aside>
✍️ How to fill them: replace every [FILL IN: ...] prompt with your own answer, then delete the Example line under it. Agents stop while any prompt is left, so a half-filled file never turns into a guess. Every example uses Northwind Coffee, a made-up brand, to show the shape of an answer.
</aside>
owner/
├── brand-voice.md how you sound
├── budget-cap.md the most the team may spend
├── approval-bar.md what auto-ships and what waits
└── positioning.md what you stand for
<aside> 🗣️ Fill it with your real words. The strongest answers are the "three lines that sound exactly like us": paste lines you actually wrote and liked. The "words we never use" list is what the voice check tests every draft against.
</aside>
# Brand voice
Owner file. Agents read this before every job and never edit it.
Replace every [FILL IN: ...] prompt. Agents stop while any prompt is left.
Each Example line shows the shape of an answer. Delete it once your own answer is in.
## Who we sound like
[FILL IN: three words that describe how the brand sounds]
Example (Northwind Coffee): warm, plain-spoken, a little nerdy about beans.
## How we talk to people
[FILL IN: "we" or "I", formal or casual, how you address the reader]
Example (Northwind Coffee): "we", casual, we talk to the reader as "you" like a regular at the counter.
## Sentences and format
[FILL IN: sentence length, emoji yes or no, hashtags yes or no, how posts end]
Example (Northwind Coffee): short sentences, one emoji at most, no hashtags in the body.
## Words we use
[FILL IN: words and phrases that sound like you]
Example (Northwind Coffee): "small batch", "roasted this week", "come say hi".
## Words we never use
[FILL IN: words, phrases and topics that are off-limits]
Example (Northwind Coffee): "game-changer", "best coffee in town", anything about rival cafes.
## Three lines that sound exactly like us
[FILL IN: paste three real lines you have written and liked]
Example (Northwind Coffee): "The new Ethiopia roast is in. It tastes like blueberries. We checked twice."
## Three lines that do not sound like us
[FILL IN: three lines you would never post, and why]
Example (Northwind Coffee): "Unlock your morning potential!" (sounds like an ad, not a person).
<aside> 💰 Fill it with the numbers you are sure of. Set a monthly cap and a cap per item, and name where money may and may not go. Every spend waits for you even inside the cap. The cap is the line nobody crosses without you changing this file.
</aside>
# Budget cap
Owner file. Agents read this before any spend and never edit it.
Replace every [FILL IN: ...] prompt. Agents stop while any prompt is left.
Each Example line shows the shape of an answer. Delete it once your own answer is in.
Every spend waits in queue/needs-your-ok.md, even inside the cap. The cap is the line no
approval can cross without you changing this file.
## Monthly cap
[FILL IN: the most the team may spend in a calendar month, with currency]
Example (Northwind Coffee): 200 USD per month across all paid channels.
## Cap per item
[FILL IN: the most a single boost, ad or paid tool action may cost]
Example (Northwind Coffee): 50 USD per boost or ad set.
## Where money may go
[FILL IN: the channels and tools allowed to spend]
Example (Northwind Coffee): Instagram and Facebook boosts only. No LinkedIn ads.
## Where money may never go
[FILL IN: channels, tools or kinds of spend that are always off-limits]
Example (Northwind Coffee): no paid sponsorships, no new paid tool subscriptions.
## When the cap is close
[FILL IN: what the team should do when spend nears the cap]
Example (Northwind Coffee): stop proposing boosts and say how much is left in the week plan.
## Last changed
[FILL IN: date you last changed this file]
Example (Northwind Coffee): 2026-11-01.
<aside> ✅ Fill it by adding to the two lists. "Auto-ships" starts with routine, on-calendar, in-voice work. "Always waits" starts with spend, negative reviews, off-calendar work, prices and offers, real names and unresolved [VERIFY] marks. Add your own lines to either list. If something is not clearly under "Auto-ships", it waits.
</aside>
# Approval bar
Owner file. Agents read this before anything ships and never edit it.
Replace every [FILL IN: ...] prompt. Agents stop while any prompt is left.
Each Example line shows the shape of an answer. Delete it once your own answer is in.
Anything not clearly listed under "Auto-ships" waits in queue/needs-your-ok.md.
## Auto-ships (no need to ask me)
These go out end to end, as long as all of the conditions below are true.
- Routine organic posts that are already on the content calendar
- Drafts that passed the voice check with no [VERIFY] marks left
- Replies to positive reviews that only say thank you
- Chat answers taken word for word from brand-os/conversation/faq-library.md
[FILL IN: anything else you are happy to let ship without seeing it]
Example (Northwind Coffee): the weekly "beans of the week" Instagram post.
## Always waits for me
These go to queue/needs-your-ok.md every time, even if they look routine.
- Any paid spend, boost, ad or budget change
- Any reply to a negative review, or to any review that raises a complaint
- Anything not on the content calendar
- Anything that mentions a price, a discount, an offer or a giveaway
- Anything that names a real person, customer or partner
- Anything with an unresolved [VERIFY] mark
- Anything that responds to a competitor
[FILL IN: anything else you always want to see first]
Example (Northwind Coffee): any post about opening hours or holiday closures.
## Alert me right away
These go to the top of queue/needs-your-ok.md with URGENT in the title.
[FILL IN: the events that should not wait for the next session]
Example (Northwind Coffee): a one-star review, a complaint about health or safety, a press enquiry.
## Channels that never auto-ship
[FILL IN: any channel where every post waits for you]
Example (Northwind Coffee): LinkedIn, because the founder posts there in her own name.
## How fast I review
[FILL IN: when you check the queue, so agents know what "waiting" means]
Example (Northwind Coffee): every weekday morning before opening.
<aside> 🧭 Fill it in plain words. The orchestrator scores every job against your goals and topics, so a vague answer here means vague scoring. Keep "Proof we can use" to facts you can back up, and say where the proof lives.
</aside>
# Positioning
Owner file. Agents read this before scoring, briefing and drafting, and never edit it.
Replace every [FILL IN: ...] prompt. Agents stop while any prompt is left.
Each Example line shows the shape of an answer. Delete it once your own answer is in.
## What we are, in one sentence
[FILL IN: what you sell, to whom, and why it is different]
Example (Northwind Coffee): a neighbourhood roastery selling small-batch coffee to people who care where their beans come from.
## Who we are for
[FILL IN: the people you most want to reach, in plain words]
Example (Northwind Coffee): locals within walking distance, and home brewers who buy beans online.
## Who we are not for
[FILL IN: who you do not chase]
Example (Northwind Coffee): offices looking for the cheapest bulk coffee.
## What we want people to believe
[FILL IN: the one or two beliefs every post should support]
Example (Northwind Coffee): fresh roasting makes a difference you can taste.
## Proof we can use
[FILL IN: real facts you can back up, with where the proof lives]
Example (Northwind Coffee): we roast on site every week (see brand-os/brand-brain/messaging-bank.md).
## Goals this quarter
[FILL IN: what the team should move this quarter, in plain words]
Example (Northwind Coffee): more online bean orders from home brewers.
## Topics we own
[FILL IN: the subjects you want to be known for]
Example (Northwind Coffee): roasting, origins, brewing at home.
<aside> ▶️ Once all four are filled, check that nothing was missed:
</aside>
Read the four files in owner/ and list any [FILL IN: ...] prompt or Example line still left.