How is this different from the free content-engine, editorial-calendar, and seo-content-brief playbooks?

The playbooks are the recipe for each move done once — repurpose an asset, plan a quarter, brief a writer. This module assembles those moves into one repeatable pipeline and assesses the system you build: a real quarter's calendar, an executable brief, and a repurpose map, graded against a rubric. The playbook gets you a good draft on a good day; the module gets you output that stays consistent on a bad one — and a credential that says so.

Do I need the M1 Foundation before this module?

Yes — the engine runs on the fuel M1 produces. Every brief here names which messaging pillar it serves and inherits your brand-voice.md, so without a real messaging-framework.md and brand-voice.md the pipeline has nothing keeping it on-brand. If you haven't done M1, start there — it's the free sample of this track.

How does the Arabic content work — is it translated from the English calendar?

No. The Arabic lane is a parallel track on the same calendar with its own briefs. You adapt the angle and the proof for the Gulf reader, not the sentences — a piece can lead on a different pillar in Arabic than it does in English. Translating the finished English calendar at the end is exactly the failure this module is built to prevent.

What does Claude actually do in the pipeline, and where does a person decide?

Claude drafts at every stage — topic into brief, brief into draft, draft into a week of channel-native derivatives in seconds. A person owns the judgment: which pillar a piece serves, whether the angle is right, and the fact-check. Claude states wrong facts with complete confidence, so every claim, price, and named customer is verified by a human before it ships.

The content engine: turn your foundation into a pipeline that ships every week

Your team already has the content-engine, editorial-calendar, and seo-content-brief playbooks — the worked recipes for repurposing an asset, planning a quarter, and briefing a writer. Each is a good move, done once. This module is the layer that turns those separate moves into a single machine: a pipeline that produces briefed, on-brand, scheduled content every week — whether or not anyone felt inspired that morning.

It’s Module 2 of the certifiable Marketing track, and it inherits everything you built in Module 1. Your messaging-framework.md and brand-voice.md are the fuel this engine runs on. M1 mastered what you say and how you say it; M2 builds the machine that turns that into a predictable stream — and assesses the machine, not a single lucky draft.

If the foundation is the fuel, the engine is the machine that burns it on a schedule. A great draft is a spark — it needs a good day, the right person, and an hour nobody had. A pipeline is a system — a brief goes in one end and on-brand, fact-checked, scheduled content comes out the other, every week, at a quality that doesn’t swing with anyone’s mood. The free playbooks teach the sparks. This module is where you stop being heroic and start being repeatable.

The pipeline, not the prompt

Most teams treat Claude as a slot machine — pull the handle with a clever prompt, hope a good draft falls out. It often does, which is the trap. A great draft from a one-off prompt feels like a win, but it isn’t a system: next week needs a fresh flash of inspiration, the quality swings with whoever’s prompting, and nothing compounds.

A pipeline is five named steps that run the same way every time, so the output is consistent instead of heroic:

Brief — turn the calendar slot into an executable brief: the intent, the angle, the pillar it serves, the proof. This is the step that decides quality; the next four are execution.
Draft — feed the brief plus messaging-framework.md and brand-voice.md. Claude drafts to the brief, on-message and on-voice, because the hard decisions were already made upstream.
Edit-to-voice — a focused pass against brand-voice.md: quote every off-voice line and rewrite it. Not make it better — make it ours.
Fact-check — the gate nothing skips. Every stat, price, claim, and named customer gets verified by a person. Claude states wrong facts with total confidence; this step is where a human catches them.
Schedule — place the finished piece on the calendar and queue its derivatives. The calendar is what turns the pipeline into a cadence instead of a pile.

Each step has one job and one input, which buys you two things. First, a different person can own each step — the brief-writer isn’t the fact-checker. Second, when a piece comes out weak you can name the broken step: it’s a brief problem or a voice-doc problem, not a vague “Claude isn’t good at this.” A pipeline you can debug beats a prompt you have to get lucky with.

You run the whole thing in the chat, no terminal on the main path. Open your marketing folder in Claude Desktop, approve the read of the brief and the two foundation docs in the “Ask permissions” prompt, and work the pieces one step at a time.

The brief is the unit of quality

A pipeline is only as good as what enters it, and what enters it is the brief. Get the brief right and the draft comes back 80% there. Get it vague and no amount of editing saves you — you’re just polishing the wrong piece. The brief is where judgment lives, which is exactly why it’s the thing the free seo-content-brief playbook can build but can’t teach you to judge.

A brief Claude can actually execute names four things — and a brief missing any one of them produces a confident, generic draft:

The intent — search and answer. What does the reader actually want, and what are they asking an engine? Informational, commercial, transactional — and the real questions they ask become the H2s and the FAQ block that AI answers quote. A brief with no intent produces a page that ranks for nothing and gets cited by no one.
The angle. The one point of view only you can take — usually a product truth. A comprehensive piece with no angle is a Wikipedia article, and it loses to anyone with a position. The angle is what makes the piece yours instead of the article every competitor could publish.
Which messaging pillar it serves. This is the line the free playbook doesn’t have. Every piece is a withdrawal from one of the pillars you funded in M1 — so name it. A brief that says this piece serves “Trustworthy, not just fast” inherits that pillar’s proof and angle automatically. A brief that serves no pillar is content for content’s sake: traffic that converts no one.
The source proof. The specific evidence the piece stands on — the metric, the named outcome, the certification, pulled straight from messaging-framework.md. Naming it in the brief is what stops Claude inventing a statistic to fill the gap. You’re not asking it to find proof; you’re handing it the proof you already stand behind.

Write the brief well and you’ve front-loaded every judgment call into one short document, so the draft step is genuinely just execution. That’s the whole reason the brief is its own step: it’s where a person decides, so the draft can be where Claude produces.

Repurpose, don’t reproduce

The cheapest content you’ll ever make is the content you already made. One flagship asset — a launch post, a webinar, a customer interview — holds a week of channel-native pieces inside it. The engine’s job is to extract them, not to invent new ones.

The distinction that matters is repurpose vs. reproduce:

Repurpose is one strong, already-fact-checked claim re-cut for a new channel and a new angle — the LinkedIn version, the X thread, the email, the newsletter blurb — all tracing back to something you already published and already stand behind.
Reproduce is asking Claude for “five new posts about our product,” which quietly invents five new claims you now have to fact-check from scratch. At volume, that’s how a wrong statistic ends up live on three channels before anyone notices.

So the rule is one pillar asset → a week of derivatives, zero new claims. You feed Claude the source plus brand-voice.md and ask for distinct angles off the same material — the problem cut, the proof cut, the how-to cut, the contrarian cut — each channel-native, each on-voice, none making a claim the source didn’t.

And the calendar is the cadence. A pile of fifteen good derivatives is not a plan; a calendar that says which derivative goes where on what day is. The editorial-calendar playbook builds the grid — the engine’s contribution is that every slot on that grid traces back to a briefed pillar asset. A full week of posts becomes one fact-checked source, repurposed, instead of seven separate gambles.

The bilingual cadence — a peer lane, not a translation

Here’s where most teams break the engine: they run the entire English pipeline, then translate the output into Arabic at the very end. The result is a calendar that reads, in Arabic, like a translated brochure — technically correct, emotionally foreign, and a week behind.

The fix is the rule M1 taught for the foundation — adapt, don’t translate — applied now to the cadence. The Arabic lane is a parallel track on the same calendar, with its own briefs:

Its own briefs, not translated ones. An Arabic piece gets an Arabic brief: its own intent (Gulf readers search differently), its own angle, and often a different leading pillar. The proof can differ too — the reference that lands with a GCC owner isn’t always the one that lands in English. You adapt the brief, and the draft follows. You never adapt the finished sentence.
The same calendar, two lanes. One quarter, one grid, an EN column and an AR column, planned together — so the Arabic lane carries the same cadence and the same themes, not a delayed echo. Sometimes the lanes share a theme in the same week; sometimes the Arabic lane leads, because the moment is regional.
Same gate, both languages. Arabic copy clears the same brand, message, and legal review as the English. The failure mode is the reviewer who can’t read it waving it through — so find someone who can, in both languages.

Done this way, Arabic is a peer lane in your engine, not a post-processing step. In this region, that’s the difference between content that earns trust and content that signals you’re translating into the market rather than building in it.

Your assignment

Build the engine for one brand — your own (recommended: the output is a real quarter of content you keep) or the sample brand Mizan, the GCC small-business bookkeeping tool used throughout this track. Everything you produce inherits the two foundation files from M1; if you don’t have them yet, do Module 1 first. Open your marketing folder in Claude Desktop, approve each read in the “Ask permissions” prompt, and work in the chat — no terminal needed.

Module 2 deliverable — the content engine

Inherits from M1: messaging-framework.md + brand-voice.md (+ brand-voice-ar.md)

1. A one-quarter editorial calendar   (one grid, two lanes)
   - 4–6 themes, each mapped to a messaging pillar
   - 12 weeks of pieces: week, theme, working headline, channel, format
   - an EN lane and an AR lane — the Arabic lane planned, not deferred
   - fixed dates respected (launches, events, regional holidays)

2. One executable content brief   (for one flagship piece)
   - search + answer intent: the real questions readers ask, grouped
   - the angle: the one POV only you can take
   - WHICH messaging pillar it serves (named, from M1)
   - the source proof it stands on (a real metric / outcome / cert)
   - outline with per-section intent, FAQ block, title/meta, internal links

3. A repurpose map   (one pillar asset → a week of derivatives)
   - the source asset (a post, webinar, or interview — already published)
   - 8–12 channel-native derivatives, distinct angles, zero new claims
   - each mapped to a calendar slot and channel
   - the one approval gate between the batch and the scheduler

Bilingual teams: the AR lane carries its OWN briefs — adapt the angle
and the proof for the Gulf reader; don't translate the English at the end.

The Foundation toolkit you installed in M1 already holds your CLAUDE.md and the two source-of-truth files. The toolkit additions at the end of this module give you the calendar and brief templates, so you’re filling in structure, not staring at a blank grid.

How it’s graded — the rubric

This is the part the free playbooks don’t have, and the part that makes the credential mean something. Your three deliverables are scored against five criteria. Each criterion is meets / nearly / not yet, and a “nearly” on any one is a revise, not a pass.

Content-engine rubric

1. The pipeline is repeatable   The flow is five named steps anyone could
                                re-run — brief, draft, edit-to-voice,
                                fact-check, schedule — not one clever prompt.

2. The brief is executable      It names all four: search/answer intent, the
                                angle, the messaging pillar it serves, and the
                                source proof. A writer could execute it cold.

3. On-brand and on-message      The calendar and the brief visibly inherit
                                messaging-framework.md and brand-voice.md —
                                every piece serves a named pillar; nothing
                                drifts off-voice. The foundation shows.

4. SEO/AEO is grounded          Built on real reader intent and the questions
                                they ask (H2s + an FAQ block), not a list of
                                keywords stuffed in. Estimates are flagged as
                                estimates, not stated as data.

5. The Arabic lane is a peer    A parallel lane on the same calendar with its
                                OWN briefs — angle and proof adapted for the
                                Gulf, not the English translated at the end.
                                (Bilingual teams.)

The discipline is what a content lead would demand before handing a quarter to a freelancer. A pipeline that depends on one person’s good day, or a calendar that’s really English content wearing Arabic, fails quietly every single week — so it has to be caught here.

The bar, shown — a worked model answer (Mizan)

You don’t have to guess what “meets” looks like. Here are passing excerpts for the sample brand — yours won’t look identical, it just needs to clear the same bar. Mizan’s English brand copy stays in English; the Arabic lane is authored, not translated.

editorial-calendar.md — Mizan (Q3, weeks 1–2 excerpt)

Pillars → themes
  Trustworthy → "books you can hand over"            (lead pillar)
  Speed       → "close your month in an afternoon"
  Simple      → "built for the owner, not the accountant"

— EN lane —
  Wk1  Speed (pillar)   "Close your month in an afternoon, not a weekend"
                        Blog → LinkedIn + email cuts
  Wk2  Simple           "You don't need to know accounting to trust your books"
                        Blog → newsletter cut

— AR lane (own briefs, adapted — not translated) —
  Wk1  Trustworthy (pillar)   "أرقام تقدر تسلّمها للبنك بدون مراجعة"
                              Blog → LinkedIn cut
                              (numbers you can hand the bank, no redo)
  Wk2  Speed                  "أقفل شهرك بعد الظهر"
                              Blog → email cut
                              (close your month this afternoon)

Why the lanes differ: in wk1 the EN lane leads on Speed, the AR lane leads
on Trustworthy — for a GCC owner the FTA-accepted VAT export is the proof
that earns trust, so the Arabic flagship leads there. Same grid, same
cadence, two briefs — not one piece translated.

content-brief.md — Mizan: "Close your month in an afternoon" (excerpt)

Pillar it serves:  Speed — "close your month in an afternoon"
                   (supporting: Trustworthy — the close is also correct)
Lane:              EN

Search + answer intent
  Informational → commercial. Owner asking: how do I close my books fast
  at month-end without an accountant?
  Real questions (→ H2s + FAQ):
    - what does "closing the month" actually mean?
    - what takes the longest, and why?
    - can I close the month myself, accurately?
    - how long should it really take?

Angle (only we can say it)
  Closing the month is an afternoon, not a weekend — because the books were
  kept right all month, not reconstructed at the end.

Source proof (no invented stats — from messaging-framework.md)
  9,000+ GCC businesses; VAT-return-ready exports accepted by the FTA
  without amendment in the 2025 cohort.

Outline (each H2 answers a question; answer-first)
  H2  "An afternoon, not a weekend" — the claim, up top
  H2  Why month-end usually eats a weekend
  H2  The afternoon close, step by step
  H2  How Mizan keeps it correct, not just fast   (→ Trustworthy)
  FAQ from the question map · title ≤60 · meta ≤155 · 3 internal links

Voice check (brand-voice.md)
  Plain over clever; no exclamation marks; you/your.
  Avoid: GL, reconciliation, ledger, leverage, solution.

repurpose-map.md — Mizan: one blog post → one week

Source (already published, already fact-checked):
  Blog "Close your month in an afternoon, not a weekend"
  Allowed to reuse: the afternoon-close steps; the 9,000+ / FTA-accepted
  proof. No NEW claims.

  Mon  LinkedIn    Problem cut — "Month-end shouldn't cost you a weekend."
                   (the pain, no stat)
  Mon  X thread    How-to cut — the afternoon-close steps, one per post
  Tue  Email       Proof cut — FTA-accepted exports, one owner's close
                   → CTA to the post
  Wed  LinkedIn    Contrarian cut — "Fast books only count if they're also
                   right."  (→ Trustworthy)
  Wed  X           One-line pull-quote from the post
  Thu  Newsletter  60-word blurb + link
  Fri  LinkedIn    Owner cut — "you don't need to be an accountant"
                   (→ Simple)

Approval gate: the brand owner reviews the batch; anything with the FTA
claim or a number goes to legal before it's queued. The scheduler runs
AFTER the gate, never instead of it.

What you keep — toolkit additions

These extend the Foundation toolkit you already installed — same folder, same CLAUDE.md, two more templates and a few more saved prompts. Drop them next to your foundation files, and every piece in the pipeline starts from structure instead of a blank page.

# editorial-calendar.md — [Brand], [quarter]

## Pillars → themes   (from messaging-framework.md)
[pillar 1] → [theme]    [pillar 2] → [theme]    [pillar 3] → [theme]

## The grid   (one row per piece; two lanes)
Wk | Lane | Theme/pillar | Working headline | Channel | Format | Briefed?
1  | EN   | ...          | ...              | ...     | ...    | y/n
1  | AR   | ...          | ...              | ...     | ...    | y/n
...
(AR lane = its OWN briefs — adapt angle + proof, don't translate)

## Fixed dates   (sync with demand-gen, PR, events BEFORE you lock it)
[launch wk X]  ·  [event wk Y]  ·  [regional holiday wk Z]

## Cadence rules
[N pieces/week]  ·  [no theme twice in a row]  ·  [front-load the strongest]

# content-brief.md — [Brand]: [working title]

Pillar it serves:  [the ONE pillar from messaging-framework.md]
Lane:              EN / AR   (AR = its own intent + proof, adapted)

## Search + answer intent
Intent: informational / commercial / transactional
Reader: [who's asking]
Real questions (→ H2s + FAQ block): [8–10, grouped]

## Angle   (the one POV only you can take — a product truth)
[one sentence]

## Source proof   (real evidence from messaging-framework.md — no invented stats)
[the metric / outcome / cert this piece stands on]

## Outline   (each H2 answers a question; front-load the answer)
H2 ... (intent: ...)   ·   FAQ from the question map
Title ≤60  ·  meta ≤155  ·  internal links: [...]

## Voice   (from brand-voice.md)
Words we use: [...]   ·   Words we avoid: [...]

The saved-prompt library (Engine) — add to the Foundation set

Turn a calendar slot into a brief
  "Read messaging-framework.md and brand-voice.md. For the calendar slot
   '[working headline]', write a content brief: the search and answer
   intent with the 8–10 real questions readers ask, the one angle only we
   can take, WHICH pillar it serves, and the exact source proof from the
   framework it stands on. Outline the H2s so each answers a question.
   Don't write the draft yet — and don't invent any statistic."

QA a draft against voice AND message
  "Read brand-voice.md and messaging-framework.md, then review this draft.
   Quote every line that's off-voice or off-message and rewrite it. Name
   the pillar this piece is meant to serve and tell me where it drifts off
   it. List every claim, number, price, and named customer that needs a
   human fact-check before it ships. Don't soften."

Repurpose one asset into a week
  "Read brand-voice.md. Here's one published piece: [paste]. Cut it into
   8–12 channel-native derivatives — LinkedIn, X, email, newsletter — each
   a DIFFERENT angle (problem / proof / how-to / contrarian / owner).
   Reuse only claims already in the source; invent no new stats. Match the
   voice exactly. Then lay them on a one-week calendar, one per slot."

Build the Arabic lane (adapt, don't translate)
  "Read brand-voice-ar.md and messaging-framework.md. For this calendar
   theme, write the ARABIC brief from scratch for a Gulf reader: its own
   intent, its own angle, and the proof that actually earns trust here —
   which may lead on a different pillar than the English. This is an
   adaptation with its own brief, not a translation of the English piece."

What you’ve proven — and what’s next

Clear the rubric and you’ve proven something a pile of good drafts never can: that your team produces on-brand, on-message, bilingual content predictably — a pipeline, not a streak of good days. That’s the Engine stage of “Certified Marketing with Claude.”

From here the track turns a working engine into campaigns and a measured loop, each module assessed the same way:

Module 3 — lifecycle & stories: sequencing that earns the next step, and approval-safe customer stories — the long-form pieces the engine feeds.
Module 4 — the launch, Module 5 — measure & iterate, then the capstone — a complete campaign for one brand, end to end, graded into the certificate.

First, make the engine reusable. The toolkit additions above — the calendar and brief templates plus the saved prompts — turn the quarter you just planned into files your whole team runs from, extending the Foundation toolkit you already installed. And if you’re rolling this across a team, the operating guide is the data, sign-off, and rollout layer that belongs underneath the whole pipeline.