<aside> 💡 Use case: give the Content engine its plan, its brief shapes, its opening lines and its search checks, so every draft starts from the same place.

</aside>

<aside> 👀 Who reads this folder: the Content engine (together with brand-brain/), and the orchestrator. The playbook "Content calendar looks thin" reads content-calendar.md.

</aside>

content-calendar.md

<aside> 🗓️ Controls: what gets written, for which channel, and when. The Content engine takes the next row marked ready.

How to fill it: add one row with the status ready to get your first draft. The status table at the top says who may move a row from one status to the next. If you keep the calendar in Airtable, use the same column names there and export it into this file each week.

Save as brand-os/content/content-calendar.md.

</aside>

# Content calendar

> Read by: content-engine (takes the next row marked `ready`), the orchestrator, and the playbook content-calendar-looks-thin.
> If your calendar lives in Airtable, keep these exact column names there and export it to this file each week,
> or connect it later. The agents read the same columns either way.
> Agents may add rows, always with the status `idea`.

## Status values
| Status | Means | Set by |
|---|---|---|
| idea | Worth doing, nothing written yet | you or any agent |
| briefed | The orchestrator wrote the brief | orchestrator |
| ready | Approved to draft. The content engine takes the next one | you, or the orchestrator when owner/approval-bar.md allows |
| drafted | A draft is saved in drafts/ | content-engine |
| held | Failed the voice check, waiting in queue/held-for-voice-review.md | content-engine |
| approved | Passed your review | you, or the orchestrator when owner/approval-bar.md allows |
| scheduled | In Metricool with a date and time | publishing-social |
| published | Live | publishing-social |
| dropped | Not doing it, kept for the record | you |

## The calendar
| ID | Publish date | Channel | Topic | Pillar | Goal | Keyword | Status | Brief | Draft file | Notes |
|---|---|---|---|---|---|---|---|---|---|---|
| 001 | [FILL IN: YYYY-MM-DD] | [FILL IN: article, linkedin, instagram, facebook, tiktok, newsletter, gbp] | [FILL IN] | [FILL IN: from messaging-bank.md] | [FILL IN: reach, clicks, leads, sales] | [FILL IN: articles only] | ready | [FILL IN: one line, or a link to the brief] | | |
| 002 | [FILL IN] | [FILL IN] | [FILL IN] | [FILL IN] | [FILL IN] | | idea | | | |

Example row (Northwind Coffee): | 003 | [date] | linkedin | Why we print the roast date | Freshness | reach | | ready | Three things the roast date tells you | | |

## When the calendar counts as thin
- Thin means fewer than [FILL IN: how many ready or scheduled items a week before it counts as thin] items in the next [FILL IN: how far ahead you look]
- What happens: the orchestrator runs /content-calendar-looks-thin. New rows arrive as `idea`. They become `ready` only when you, or owner/approval-bar.md, say so.

## How often each channel posts
See social/posting-schedule.md. The calendar fills those slots; it does not set them.

brief-templates.md

<aside> 📝 Controls: the shape of every brief, one template per channel: audience, one promise, three proof points, keyword for search pieces, call to action. The Content engine only writes for channels that have a template here.

How to fill it: set the length for each channel you use. Delete the channels you do not use. To add one, copy a block and change it.

Save as brand-os/content/brief-templates.md.

</aside>

# Brief templates

> Read by: content-engine. The orchestrator fills one of these for every job.
> One template per channel. The content engine only writes for channels that have a template here:
> to add a channel, copy a block and change it.
> Lengths are yours to set. Until a length is filled in, the content engine asks before drafting.

## Every brief has these fields
- Audience: who this piece is for (from brand-brain/voice-guide.md)
- One promise: what the reader gets, in one sentence
- Three proof points: IDs from brand-brain/messaging-bank.md
- Keyword: article only, from signals-seo/keyword-map.md
- Call to action: from the offers table in messaging-bank.md
- Visual: what creative-studio needs to make, or "none"

## Article (WordPress)
- Calendar ID:
- Audience:
- One promise:
- Proof points: P_, P_, P_
- Primary keyword:
- Other keywords:
- Search intent: [learn, compare, buy or find us]
- Length: [FILL IN: your usual article length in words]
- Format: title, intro, H2 sections, short close with the call to action
- Must answer: [the questions the reader arrives with]
- Internal links to: [pages from keyword-map.md]
- Call to action:
- Visual: [header image, diagrams]
- Then: run content/seo-checklist.md

## LinkedIn post
- Calendar ID:
- Audience:
- One promise:
- Proof points: P_, P_, P_
- Length: [FILL IN: your usual LinkedIn post length]
- Format: hook line, short paragraphs, one idea per paragraph
- Hook pattern: [an ID from hook-bank.md]
- Link: [FILL IN: in the post, in the first comment, or none]
- Call to action:
- Visual: [image, document, none]

## Instagram caption
- Calendar ID:
- Audience:
- One promise:
- Proof points: P_, P_, P_
- Length: [FILL IN: your usual caption length]
- Format: first line that works without "more", then the detail
- Hook pattern:
- Hashtags: [a set from social/hashtag-rules.md]
- Call to action: [FILL IN: where you send people, e.g. the link in your bio]
- Visual: [single image, carousel, short video: brief creative-studio]

## Facebook post
- Calendar ID:
- Audience:
- One promise:
- Proof points: P_, P_, P_
- Length: [FILL IN]
- Format:
- Hook pattern:
- Link:
- Call to action:
- Visual:

## Newsletter
- Calendar ID:
- Audience: [which list]
- One promise:
- Proof points: P_, P_, P_
- Subject line: three options
- Preview text:
- Length: [FILL IN]
- Format: [FILL IN: one story, or several short sections]
- Call to action: one main link
- Visual:

## Google Business Profile post
- Calendar ID:
- Audience: people searching for you nearby
- One promise:
- Proof points: P_
- Length: [FILL IN]
- Post type: [update, offer, event]
- Button: [FILL IN: the button and where it points]
- Visual: [photo]

## Example (Northwind Coffee), LinkedIn post
- Audience: people who brew at home
- One promise: you will know if your beans are still fresh
- Proof points: P1
- Hook pattern: H5
- Call to action: Try the sampler
- Visual: photo of the bag label

hook-bank.md

<aside> 🪝 Controls: the opening-line patterns the Content engine draws on. It writes three hooks per piece, picks the strongest and keeps the other two in the draft.

How to fill it: keep the patterns that suit you and delete the rest. Over time, the two tables at the bottom fill with hooks that worked and hooks that flopped, backed by your own results.

Save as brand-os/content/hook-bank.md.

</aside>

# Hook bank

> Read by: content-engine. It writes three opening lines per piece using these patterns, picks the strongest
> and keeps the other two in the draft.
> Agents may add rows to "Hooks that worked" and "Hooks that flopped", with the status `proposed`, when the
> numbers from results-roi back it up. You approve them by changing the status to `kept`.

## Patterns
| ID | Pattern | Shape | Example (Northwind Coffee) | Best on |
|---|---|---|---|---|
| H1 | Plain promise | "You can <result> without <pain>." | "You can brew cafe coffee at home without new gear." | [FILL IN] |
| H2 | The question they already ask | "<The question, in their words>?" | "Why does my coffee taste flat by Friday?" | [FILL IN] |
| H3 | The common mistake | "Most people <mistake>. Here is why it costs them." | "Most people store beans in the fridge. Here is why that hurts the taste." | [FILL IN] |
| H4 | Before and after | "<Before>. Then <one change>." | "Same beans, same kettle. Then we changed the grind." | [FILL IN] |
| H5 | One specific detail | "<A small, concrete detail> tells you <something useful>." | "The date on the bag tells you more than the price does." | [FILL IN] |
| H6 | A view you disagree with | "<A common belief> is wrong for <who>." | "Dark roast is not stronger coffee." | [FILL IN] |
| H7 | Start of a story | "<A moment, a place, a person doing something>." | "At 6am the roaster is already warm." | [FILL IN] |
| H8 | What is inside | "<What the reader will get> in <the format>." | "Three ways to tell if your beans are fresh." | [FILL IN] |
| H9 | [FILL IN: your own pattern] | [FILL IN] | [FILL IN] | [FILL IN] |

## Rules for every hook
- The body must deliver what the hook promises.
- It passes brand-brain/tone-rules.md like everything else.
- It fits the first line on a phone screen: [FILL IN: your limit in characters, or "no limit"]
- Never: [FILL IN: hook styles you refuse to use]

## Hooks that worked
| Date | Channel | Hook (exact) | Pattern ID | Post file or link | Why it worked (from the results report) | Status |
|---|---|---|---|---|---|---|
| [FILL IN] | [FILL IN] | [FILL IN] | [FILL IN] | [FILL IN] | [FILL IN] | kept |

## Hooks that flopped
| Date | Channel | Hook (exact) | Pattern ID | What happened | Status |
|---|---|---|---|---|---|
| [FILL IN] | [FILL IN] | [FILL IN] | [FILL IN] | [FILL IN] | kept |

seo-checklist.md

<aside> 🔍 Controls: the search pass every article goes through before it leaves drafts/. The first four checks are the ones the Content engine agent file names: keyword in the title, keyword in the first 100 words, keyword in an H2, meta description of 155 characters or fewer.

How to fill it: keep the required checks. Add your own at the bottom, such as the content score you accept from Surfer.

Save as brand-os/content/seo-checklist.md.

</aside>

# SEO checklist

> Read by: content-engine. Run on every article before it leaves drafts/. Not used for social posts.
> The content engine reports each check as pass or fail in the draft's front matter.
> The first four checks are the ones the content engine agent file names. Keep them. Add your own below.

## Required checks
| # | Check | Pass when |
|---|---|---|
| S1 | Keyword in the title | The primary keyword from the brief appears in the title |
| S2 | Keyword early | The primary keyword appears in the first 100 words |
| S3 | Keyword in a heading | The primary keyword, or a close form of it, appears in at least one H2 |
| S4 | Meta description | Written, 155 characters or fewer, and it says what the reader gets |
| S5 | One owner | No other page in signals-seo/keyword-map.md owns this keyword |
| S6 | One H1 | The page has exactly one H1 |
| S7 | Internal links | Links to [FILL IN: how many] related pages listed in keyword-map.md |
| S8 | Image alt text | Every image has alt text that describes it |
| S9 | Slug | Short, lower case, words joined with hyphens, contains the keyword |
| S10 | Facts | Every number has a source in the brief or messaging-bank.md, or is marked [VERIFY] |

## Your own checks
| # | Check | Pass when |
|---|---|---|
| S11 | [FILL IN: e.g. Surfer content score] | [FILL IN: the score you accept] |
| S12 | [FILL IN] | [FILL IN] |

## How a fail is handled
- S1 to S9: the content engine fixes it and runs the check again.
- S10: it never invents a source. It leaves [VERIFY] in place and lists it for you.

## Example report (Northwind Coffee)
seo_check: S1 pass, S2 pass, S3 pass, S4 pass, S5 pass, S6 pass, S7 pass, S8 fail (one image without alt text, fixed), S9 pass, S10 pass

<aside> 👉 Next: /creative

</aside>