Brain Name: Content Brain
Document Type: Operational Template
Status: Active
Version: v1.0
Authority: HeadOffice
Applies To: Content Brain operational content briefs, SEO briefs, affiliate support briefs, affiliate product content pack briefs, affiliate funnel support briefs, authority content briefs, refresh briefs, repurposing briefs, YouTube support briefs, VEO3 pre video briefs, email content briefs, social content briefs, internal linking briefs, AIBS education briefs, and first operational Content Brain layer use
Parent: Content Brain
Last Reviewed: 2026-05-24
Operational Copy Notice
This page is the live operator content brief page for Content Brain on mwmscontentbrain.site.
MCR remains the source of truth.
If this page conflicts with MCR, MCR wins.
This page is designed for practical operator use.
It is not a full MCR governance page.
Purpose
Content Brain Content Briefs defines the standard structure for planning content before production begins.
This page exists to prevent Content Brain from producing content without a clear:
purpose
audience
intent
source
structure
quality bar
review path
handoff path
approval owner
feedback signal
A content brief is the control document between idea and output.
It ensures content is not created randomly, vaguely, or only because a topic sounds useful.
Every meaningful Content Brain output should begin with a brief unless the task is small, low risk, and clearly defined.
Source Of Truth
MCR defines the governing version of Content Brain.
mwmscontentbrain.site operates the working version.
This page is the working operator version of the Content Brain content brief system.
Do not treat this page as a replacement for:
Content Brain Canon
Content Brain Architecture
Content Brain Page Registry
Content Brain Copy Map
Content Brain Migration Execution Checklist
mwmscontentbrain.site First Operational Layer Build Checklist
Those remain MCR control pages.
What This Page Is For
Use this page when creating a brief for:
SEO articles
authority articles
affiliate support content
affiliate product content pack assets
affiliate funnel support content
pre-sell articles
comparison articles
review support content
FAQ content
objection-handling content
trust support content
YouTube descriptions
YouTube script support
VEO3 pre video support
email drafts
newsletter content
social repurposing assets
content refresh work
topic cluster content
pillar pages
internal linking support content
sales support content
conversion support content
AIBS education content
case-study support content
What This Page Does Not Control
This page does not control:
offer approval
campaign approval
capital approval
final compliance approval
statistical validation
search validation
affiliate opportunity approval
paid ad decisions
plugin implementation
Supabase implementation
Brain Room routing
HeadOffice reporting build work
M’s active development areas
Those remain governed by the relevant Brain, protocol, standard, or implementation layer.
Core Principle
A content brief must define the job of the content before the content is written.
The brief should answer:
who the content is for
why the content exists
what the content must achieve
where the content fits in the system
what the reader needs
what the content must include
what risk must be controlled
where the content will be used
who must approve it
how success will be reviewed
If the brief cannot answer these questions, the content should not move into production yet.
When To Use A Brief
Use a brief when the content is:
important
public-facing
SEO-focused
affiliate-related
compliance-sensitive
campaign-supporting
conversion-supporting
authority-building
intended for repurposing
intended for refresh
connected to a wider Brain workflow
Small internal notes may not need a full brief, but they still need a clear purpose and destination.
Brief Selection Guide
Use the correct brief type for the job.
Use General Content Brief for standard articles, guides, support pages, and educational content.
Use SEO Content Brief for search-focused content.
Use Affiliate Support Brief for content supporting an approved or review-ready affiliate offer.
Use Affiliate Product Content Pack Brief when planning multiple assets around one offer.
Use Affiliate Funnel Support Brief when mapping content to funnel stages.
Use Refresh Brief when improving existing content.
Use Repurposing Brief when adapting approved content into another format.
Use YouTube Or VEO3 Support Brief when preparing video support assets.
Use Email Or Social Brief when turning approved ideas into outbound or repurposed content.
Master Brief Template
Use this master structure when a full content brief is needed.
1. Brief Name
Field:
Brief Name:
Operator instruction:
Write a clear internal name for the brief.
Use the content purpose, topic, offer, or asset type.
Example:
Rural Family Summer Storm Water Trust Article
2. Date Created
Field:
Date Created:
Operator instruction:
Record the date the brief was created.
3. Source Brain
Field:
Source Brain:
Options:
HeadOffice
Affiliate Brain
Research Brain
Search Intelligence Brain
Ads Brain
Experimentation Brain
AIBS Brain
Compliance Brain
Finance Brain
Data Brain
Conversion Brain
Sales Brain
SIT Brain
Manual Operator Observation
Operator instruction:
Record where the request or signal came from.
If the source Brain is unclear, park the brief until clarified.
4. Request Type
Field:
Request Type:
Options:
New content
SEO content
Affiliate support content
Affiliate product content pack asset
Affiliate funnel support
YouTube support
VEO3 pre video support
Email content
Social content
Repurposing
Refresh
Internal linking support
Trust or authority content
AIBS education content
Campaign support content
Other
Operator instruction:
Choose the closest request type.
5. Content Asset Type
Field:
Content Asset Type:
Options:
SEO article
Blog post
Product support page
Pre-sell article
Comparison article
Review support article
FAQ page
Objection-handling page
Trust page
Authority page
YouTube script
VEO3 pre video support script
YouTube description
Email sequence
Single email
Social post set
Short-form video script
Internal linking update
Refresh update
Repurposed content asset
AIBS education article
Case-study support asset
Other
Operator instruction:
Be specific about the asset being created.
6. Working Title
Field:
Working Title:
Operator instruction:
Write a working title that can be improved later.
The title should reflect the reader’s problem, intent, or desired outcome.
7. Target Audience
Field:
Target Audience:
Operator instruction:
Describe who the asset is for.
Include:
audience type
awareness level
pain point
desired outcome
knowledge level
market or location if relevant
Example:
USA rural family concerned about summer storms and reliable water access.
8. Audience Awareness Stage
Field:
Audience Awareness Stage:
Options:
Unaware
Problem aware
Solution aware
Product aware
Most aware
Existing lead
Existing buyer
Internal operator
Business owner
Operator instruction:
Choose the awareness stage that matches the content job.
9. Reader Intent
Field:
Reader Intent:
Options:
Learn
Compare
Decide
Understand risk
Solve a problem
Validate trust
Prepare for purchase
Watch VSL
Click affiliate link
Book call
Reply
Share
Save
Other
Operator instruction:
State what the reader is trying to do.
10. Content Goal
Field:
Content Goal:
Operator instruction:
Define what the content asset must achieve.
Examples:
Educate reader before they watch the VSL.
Answer common objections before affiliate click.
Support SEO topic cluster.
Build trust around a problem.
Repurpose approved article into social posts.
Refresh outdated content for better search intent match.
11. Funnel Role
Field:
Funnel Role:
Options:
Awareness
Education
Trust building
Pre-sell
Comparison
Objection handling
Decision support
Follow-up
Retention
Internal support
Operator instruction:
Choose where the content fits in the journey.
12. Related Offer Or Product
Field:
Related Offer Or Product:
Operator instruction:
Name the offer, product, service, campaign, or Brain initiative this content supports.
If not applicable, write:
Not applicable
If offer status is unclear, write:
Offer status unclear — requires Affiliate Brain or Research Brain review.
13. Offer Status
Field:
Offer Status:
Options:
Approved
Review-ready
Research needed
Testing candidate
Rejected
Not applicable
Unknown
Operator instruction:
Do not write affiliate support content as if the offer is approved unless the offer status is clear.
14. Research Basis
Field:
Research Basis:
Operator instruction:
List the research, signals, source pages, intelligence, or evidence used for the brief.
Include:
Research Brain signals
Search Intelligence Brain signals
Affiliate Brain offer notes
customer language
competitor observations
SERP notes
Data Brain signals
HeadOffice priority notes
If no research exists, write:
Research basis missing.
15. Key Reader Questions
Field:
Key Reader Questions:
Operator instruction:
List the main questions the content should answer.
These should reflect real audience intent, not generic filler.
16. Key Objections
Field:
Key Objections:
Operator instruction:
List objections, doubts, fears, or blockers the content should address.
Examples:
Will this actually work?
Is this safe?
Is this affordable?
Can I trust this?
Is this right for my situation?
What happens if it fails?
17. Main Message
Field:
Main Message:
Operator instruction:
Write the core message the content should communicate.
The message should be clear, useful, and aligned with the reader’s stage.
18. Supporting Points
Field:
Supporting Points:
Operator instruction:
List the main points the content should include.
Keep them relevant to the content goal.
19. Proof Or Support Needed
Field:
Proof Or Support Needed:
Operator instruction:
List proof, examples, trust signals, logic, source material, or demonstrations needed.
If proof is missing, flag it before production.
20. Claims To Avoid
Field:
Claims To Avoid:
Operator instruction:
List claims that should not be made.
Include:
unverified product claims
income claims
health claims
legal claims
guarantees
scarcity claims
urgency claims
exaggerated comparisons
unsupported performance claims
21. Compliance Sensitivity
Field:
Compliance Sensitivity:
Options:
Low
Medium
High
Unknown
Operator instruction:
Choose the risk level.
If medium, high, or unknown, identify who must review the content before use.
22. Required CTA
Field:
Required CTA:
Options:
Read next page
Watch video
Watch VSL
Click affiliate link
Join list
Book call
Reply
Save
Share
No CTA
Other
Operator instruction:
Choose the CTA that matches the content role.
Do not force a CTA where it does not fit.
23. Internal Links Needed
Field:
Internal Links Needed:
Operator instruction:
List internal pages that should be linked from or to this content.
Use the Internal Linking page if the linking plan is meaningful.
24. External References Needed
Field:
External References Needed:
Operator instruction:
List any external sources, references, examples, or evidence required.
Use only reliable sources where factual support is needed.
25. Content Structure
Field:
Content Structure:
Operator instruction:
Outline the recommended structure.
Include:
introduction
main sections
subsections
FAQ section if needed
CTA section
trust section if needed
comparison section if needed
objection-handling section if needed
26. Tone And Style
Field:
Tone And Style:
Operator instruction:
Define the tone.
Examples:
clear
direct
helpful
plain-English
calm
authority-building
practical
trust-focused
compliance-aware
conversion-supportive
Do not use hype unless explicitly approved.
27. Handoff Destination
Field:
Handoff Destination:
Options:
WordPress page
Blog post
YouTube description
YouTube script
VEO3 pre video
Newsletter
Social post
Affiliate funnel
Sales support
Internal knowledge
Refresh queue
Repurposing queue
Other
Operator instruction:
State where the content will go after preparation.
28. Approval Owner
Field:
Approval Owner:
Operator instruction:
Name the Brain, person, or role that must approve the content before use.
Examples:
HeadOffice
Affiliate Brain
Research Brain
Compliance Brain
Finance Brain
Ads Brain
Experimentation Brain
Manual operator
If approval owner is missing, do not treat the content as ready.
29. Signal To Watch
Field:
Signal To Watch:
Operator instruction:
Define what should be watched after the content is used.
Examples:
ranking movement
click-through rate
VSL click rate
affiliate click rate
time on page
email reply rate
objection reduction
engagement
conversion assist
lead quality
manual feedback
30. Brief Status
Field:
Brief Status:
Options:
Draft
Needs research
Needs approval
Ready for drafting
In drafting
In review
Ready for handoff
Handed off
Published
Parked
Closed
Operator instruction:
Keep the status current.
Fast Brief Template
Use this for small or low-risk tasks.
Brief Name:
Date:
Source Brain:
Request Type:
Content Asset Type:
Target Audience:
Reader Intent:
Content Goal:
Main Message:
Key Points:
Claims To Avoid:
Approval Owner:
Handoff Destination:
Signal To Watch:
Status:
SEO Content Brief Template
Use this when the content is search-focused.
Brief Name:
Primary Search Intent:
Target Query Or Topic:
Supporting Topics:
Reader Problem:
Audience Awareness Stage:
Search Intelligence Source:
Research Basis:
Information Gain Angle:
E E A T Requirements:
Content Structure:
Internal Links Needed:
External References Needed:
Claims To Avoid:
Compliance Sensitivity:
CTA:
Approval Owner:
Signal To Watch:
Status:
SEO content must be useful to the reader first.
Do not create thin content only to target a keyword.
Affiliate Support Brief Template
Use this when the content supports an affiliate offer.
Brief Name:
Related Offer:
Offer Status:
Source Brain:
Research Basis:
Target Audience:
Audience Awareness Stage:
Funnel Role:
Content Asset Type:
Reader Intent:
Key Objections:
Main Message:
Trust Signals Needed:
Claims To Avoid:
Compliance Sensitivity:
CTA:
Approval Owner:
Handoff Destination:
Signal To Watch:
Status:
Affiliate support content does not approve the offer.
It only structures content around an approved or review-ready affiliate opportunity.
Affiliate Product Content Pack Brief Template
Use this when planning multiple assets for one affiliate product or offer.
Pack Name:
Related Offer:
Offer Status:
Source Brain:
Research Basis:
Audience:
Funnel Role:
Pack Size:
Required Assets:
Pre-sell Content Needed:
FAQ Content Needed:
Objection Content Needed:
Comparison Content Needed:
YouTube Support Needed:
Email Support Needed:
Social Support Needed:
Internal Linking Needed:
Repurposing Plan:
Claims To Avoid:
Compliance Sensitivity:
Approval Owner:
Handoff Destination:
Signal To Watch:
Status:
Use the Affiliate Content Packs page for fuller pack planning.
Affiliate Funnel Support Brief Template
Use this when mapping content to funnel stages.
Funnel Name:
Related Offer:
Offer Status:
Source Brain:
Target Audience:
Awareness Stage:
Funnel Stage:
Reader Intent:
Content Asset Needed:
Main Message:
Objections To Address:
Trust Signals Needed:
CTA:
Claims To Avoid:
Compliance Sensitivity:
Approval Owner:
Handoff Destination:
Signal To Watch:
Status:
Use the Affiliate Funnel Support page for fuller funnel mapping.
Refresh Brief Template
Use this when improving existing content.
Page Or Asset Name:
Current URL Or Location:
Refresh Trigger:
Source Signal:
Current Problem:
Search Intent Change:
Research Update Needed:
Offer Change:
Compliance Risk:
Internal Linking Issue:
Content Quality Issue:
Action Needed:
Update
Expand
Rewrite
Merge
Redirect
Retire
Park
Approval Owner:
Signal To Watch:
Status:
Use the Refresh page for fuller refresh decisions.
Repurposing Brief Template
Use this when adapting approved content into another format.
Source Asset:
Source Asset Status:
Approved Message To Preserve:
New Format:
Target Audience:
Funnel Role:
Main Message:
Sections To Reuse:
Claims To Avoid:
Compliance Sensitivity:
CTA:
Approval Owner:
Handoff Destination:
Signal To Watch:
Status:
Use the Repurposing page for fuller repurposing planning.
YouTube Or VEO3 Support Brief Template
Use this when preparing video support content.
Brief Name:
Video Type:
YouTube Description
YouTube Script Support
VEO3 Pre Video
Short-Form Script Seed
Source Brain:
Related Offer Or Topic:
Audience:
Hook Direction:
Main Message:
Key Points:
Claims To Avoid:
Compliance Sensitivity:
CTA:
Approval Owner:
Handoff Destination:
Signal To Watch:
Status:
Do not introduce unapproved claims in video support material.
Email Or Social Brief Template
Use this when preparing email or social content.
Brief Name:
Format:
Newsletter
Social Post Set
Short Post
Thread
Caption
Source Brain:
Source Asset:
Audience:
Content Goal:
Main Message:
CTA:
Claims To Avoid:
Compliance Sensitivity:
Approval Owner:
Handoff Destination:
Signal To Watch:
Status:
Brief Quality Check
Before moving from brief to draft, confirm:
source Brain is clear
content purpose is clear
audience is clear
reader intent is clear
content type is clear
research basis is noted
offer status is clear where relevant
claims to avoid are listed
approval owner is identified
handoff destination is clear
signal to watch is defined
If any item is missing, the brief is not ready.
When To Park A Brief
Park a brief when:
purpose is unclear
audience is unclear
source Brain is unclear
approval owner is missing
research basis is weak
offer status is unclear
compliance risk is unclear
budget or resource issue exists
destination is unknown
the request belongs to another Brain
Parked does not mean rejected.
It means missing information must be resolved before production.
Relationship To Other Operational Pages
Use this page with:
Content Brain for the homepage and operator starting point
Content Brain Workflow for the full workflow
Content Brain Publishing Readiness for final checks
Content Brain Affiliate Content Packs for affiliate content pack planning
Content Brain Affiliate Funnel Support for funnel-stage mapping
Content Brain SEO Content Briefs for search-focused content planning
Content Brain Internal Linking for page connection planning
Content Brain Repurposing for adapting approved content
Content Brain Refresh for improving existing content
Future Plugin Or UI Candidates
This page may later support:
Content Brief Generator
SEO Brief Generator
Affiliate Content Pack Generator
Publishing Readiness Checklist UI
Content Production Queue
Content Opportunity Queue
Content Operations Dashboard
Do not build these yet.
Manual use must prove the need first.
No Build Rule
Do not start any of the following from this page:
plugin work
custom UI work
Supabase work
Brain Room routing
automation
queue build
dashboard build
generator build
cross-brain task routing
This page is part of the first manual operational layer only.
Old Page Handling
This page replaces the operator role of the older page:
Content Brain Content Brief Template
After Content Brain Content Briefs is created and checked, the older Content Brain Content Brief Template page should be handled as follows:
If it is only a duplicate operational brief page, delete it.
If it is needed for historical reference, move it to a legacy/reference area and mark it clearly as legacy.
Do not keep both as active operator content brief pages.
The active operator content brief page should be:
Content Brain Content Briefs
Drift Protection
The system must prevent:
content being produced without a brief
briefs being created without purpose
briefs being created without source Brain context
briefs being created without approval owner
affiliate support briefs being created before offer status is clear
SEO briefs being created without reader intent
repurposing briefs changing approved meaning
refresh briefs being created without a trigger
briefs bypassing Research Brain, Affiliate Brain, Search Intelligence Brain, Compliance Brain, Finance Brain, Experimentation Brain, Ads Brain, Data Brain, or HeadOffice authority
old template pages being treated as the current operator brief page after this clean page is created
future UI being built before manual brief use proves need
Architectural Intent
Content Brain Content Briefs exists to make content planning visible, structured, and controlled.
Its role is to ensure Content Brain can produce useful content assets without drifting into random content creation.
A brief should become the bridge between:
signal
research
offer need
SEO opportunity
funnel requirement
content production
review
handoff
learning feedback
The long-term intent is:
MCR defines Content Brain.
mwmscontentbrain.site operates Content Brain.
Future plugin or UI systems automate repeated workflows only after manual use proves the need.
Final Rule
No meaningful content should move into production without a clear brief.
No affiliate support content should move forward without known offer status.
No SEO content should move forward without reader intent.
No repurposed content should change approved meaning.
No refresh work should happen without a trigger.
No brief should override the authority of another Brain.
When in doubt, park the brief and route the missing decision back to the correct Brain.
Change Log
Version: v1.0
Date: 2026-05-24
Author: HeadOffice
Change: Created clean operator content brief page for mwmscontentbrain.site based on MCR Content Brain Content Brief Template Operational Copy and the existing Content Brain Content Brief Template page. Defines the live Content Brain Content Briefs page for the first operational Content Brain layer, including master brief structure, fast brief, SEO brief, affiliate support brief, affiliate product content pack brief, affiliate funnel support brief, refresh brief, repurposing brief, YouTube or VEO3 support brief, email or social brief, brief quality checks, parking rules, relationship to other operational pages, no build rule, old page handling, drift protection, and manual-first future plugin/UI boundaries.
Change Impact Declaration
Pages Created:
Content Brain Content Briefs
Pages Updated:
None
Pages To Delete Or Move To Legacy After Validation:
Content Brain Content Brief Template
Pages Deprecated:
Content Brain Content Brief Template as active operator content brief page
Registries Requiring Update:
None
Canon Version Update Required:
No
Change Log Entry Required:
No
END CONTENT BRAIN CONTENT BRIEFS v1.0