Brain Name: Content Brain
Document Type: Operational Copy
Status: Draft
Version: v1.0
Authority: Content Brain under HeadOffice governance
Applies To: mwmscontentbrain.site future content brief page, Content Brain first operational copy batch, Content Brain operator templates, SEO content briefs, affiliate content briefs, YouTube content briefs, VEO3 pre-video support briefs, email content briefs, social content briefs, refresh briefs, repurposing briefs, and Content Brain source-of-truth protection
Parent: Content Brain
Last Reviewed: 2026-05-24
Content Brain Content Brief Template Operational Copy
Purpose
The Content Brain Content Brief Template Operational Copy defines the simplified future content brief template for mwmscontentbrain.site.
This page is not the live template page yet.
This page is the MCR-prepared operational copy that will later be used to create the first practical Content Brain content brief page.
Its purpose is to give the operator one reusable brief structure for planning content assets before drafting begins.
This page helps prevent random content creation by requiring every meaningful content asset to have:
a clear source Brain
a clear purpose
a clear content type
a clear audience
a clear intent
a clear research basis
a clear approval owner
a clear handoff destination
a clear signal to watch
The content brief is the bridge between a content request and a usable content asset.
Scope
This operational copy applies to:
future mwmscontentbrain.site content brief page content
manual Content Brain briefing workflow
SEO article briefs
affiliate product content briefs
affiliate funnel support briefs
pre-sell content briefs
comparison content briefs
FAQ and objection content briefs
YouTube script briefs
VEO3 pre-video support briefs
email content briefs
social content briefs
repurposing briefs
refresh briefs
AIBS education content briefs
campaign support content briefs
first migration batch preparation
operator guidance for structured content creation
This operational copy does not apply to:
Content Brain Canon authority
Content Brain Architecture authority
Content Brain Page Registry
Content Brain Copy Map
Content Brain plugin or UI build
Supabase implementation
Brain Room routing
cross-brain automation
M’s active build work
live mwmsbrain.site plugin work
mwmscontentbrain.site migration execution
This page prepares future operational template content only.
It does not start migration.
Core Rule
Do not start drafting important content without a brief.
A content brief must confirm:
why the content is needed
who requested it
which Brain owns the decision
what research supports it
what the content must achieve
what risk exists
what approval is required
where the asset will be used
what signal will be watched after use
Content Brain uses briefs to keep content structured, useful, and aligned with the MWMS system.
Future Template Page Title
Recommended future template page title:
Content Briefs
Recommended future page subtitle:
Create structured briefs before drafting content assets.
Recommended operator description:
Use this template whenever Content Brain needs to plan an SEO article, affiliate support asset, content pack asset, YouTube script, VEO3 pre-video support asset, email, social post set, refresh task, repurposing task, or AIBS education asset.
When To Use This Template
Use this template when:
a new content asset is needed
a content request comes from another Brain
an affiliate offer needs support content
an SEO opportunity needs content planning
a YouTube or VEO3 asset is required
a page needs refreshing
an approved asset needs repurposing
an internal linking plan needs content support
a campaign needs supporting content
an AIBS education page is needed
a trust or authority asset is needed
Do not use this template for:
offer approval
claim approval
budget approval
ad campaign setup
experiment validation
research verdicts
finance decisions
conversion strategy decisions
sales strategy decisions
Those decisions belong to the relevant Brain.
Content Brief Template
1. Brief Name
Field:
Content Brief Name:
Operator instruction:
Use a clear name that describes the asset.
Examples:
GeniusWave Review Support Article Brief
Aqua Tower FAQ Support Page Brief
AIBS Business Owner Education Article Brief
Affiliate Product Pre-Sell Article Brief
VEO3 Pre-Video Hook Support Brief
2. Date Created
Field:
Date Created:
Operator instruction:
Record the date the brief was created.
3. Source Brain
Field:
Source Brain:
Options may include:
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 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
Problem education
Solution education
Pre-sell
Trust building
Objection handling
Comparison
FAQ support
Decision support
VSL support
Email nurture
Retargeting support
Sales support
Post-click support
Internal education
Operator instruction:
Record the role this asset plays in the funnel or content system.
12. Related Offer, Product, Or Topic
Field:
Related Offer, Product, Or Topic:
Operator instruction:
Name the related offer, product, topic, campaign, or system.
If there is no offer, record the core topic.
13. Offer Status
Field:
Offer Status:
Options:
Approved
Review-ready
Research required
Testing candidate
Parked
Not offer-related
Unknown
Operator instruction:
If this content supports an affiliate product or campaign, confirm the offer status.
If offer status is unknown, do not proceed to draft affiliate claims.
14. Research Basis
Field:
Research Basis:
Operator instruction:
List the research, evidence, or source material supporting this content.
Include:
Research Brain notes
Search Intelligence Brain notes
affiliate product evidence
audience language
SERP observation
newsletter signal
competitor insight
customer question
campaign learning
manual observation
If research is missing, mark:
Research required before drafting.
15. Search Intelligence Notes
Field:
Search Intelligence Notes:
Operator instruction:
Use when the content has SEO intent.
Record:
target query or topic
search intent
SERP pattern
content gap
related questions
comparison demand
topic cluster relationship
If not SEO-related, mark:
Not applicable.
16. Compliance Risk
Field:
Compliance Risk Level:
Options:
Low
Medium
High
Unknown
Not applicable
Operator instruction:
Flag risk early.
Risk may involve:
health claims
financial claims
earnings claims
energy claims
scarcity claims
privacy claims
product performance claims
legal claims
political claims
sensitive audience claims
If risk is medium, high, or unknown, route to Compliance Brain or approval owner before publishing.
17. Claims To Avoid
Field:
Claims To Avoid:
Operator instruction:
List claims that must not be made.
Examples:
guaranteed results
medical cure
income promise
risk-free claim
unverified product performance
unsupported comparison
false scarcity
Do not strengthen claims during drafting.
18. Required Proof Or Support
Field:
Required Proof Or Support:
Operator instruction:
List proof elements needed.
Examples:
source link
research note
customer language
approved product feature
case study
testimonial status
data point
expert note
internal system note
If proof is not available, avoid making the claim.
19. Key Message
Field:
Key Message:
Operator instruction:
Write the main message in one clear sentence.
Example:
This article helps rural families understand why water backup planning matters before summer storm season.
20. Supporting Points
Field:
Supporting Points:
Operator instruction:
List the main points the content should cover.
Use short bullets.
21. Objections To Address
Field:
Objections To Address:
Operator instruction:
List likely reader objections.
Examples:
Is this product legitimate?
Does this solve my problem?
Is it too expensive?
Is this too technical?
Why should I act now?
Can I trust this source?
What are the risks?
22. Trust Elements Needed
Field:
Trust Elements Needed:
Operator instruction:
List trust elements to include.
Examples:
clear explanation
balanced wording
source citation
FAQ
risk note
comparison
transparent limitation
approved testimonial
authority reference
brand consistency
23. Internal Linking Notes
Field:
Internal Linking Notes:
Operator instruction:
List:
pillar page
supporting page
affiliate page
FAQ page
trust page
comparison page
related article
anchor text idea
reader journey
If none exist yet, record:
Internal linking opportunity to create later.
24. CTA Or Next Step
Field:
CTA Or Next Step:
Options:
Read next article
Watch VSL
Click affiliate link
Download guide
Book call
Reply to email
Visit product page
Open checklist
Share internally
No CTA
Other
Operator instruction:
Use a CTA that matches the content role and approval status.
25. Format Requirements
Field:
Format Requirements:
Operator instruction:
Include format guidance.
Examples:
short article
long-form SEO article
YouTube script
VEO3 time-coded pre-video support
email sequence
bullet-heavy checklist
FAQ format
comparison table
social post set
refresh notes
26. Tone And Style
Field:
Tone And Style:
Operator instruction:
Define the tone.
Examples:
clear
helpful
practical
calm
authority-building
direct
American-friendly
compliance-safe
non-hype
science-curious
business-owner friendly
For VEO3 pre-video support, follow the current MWMS VEO3 pre-video style rules.
27. Required Sections
Field:
Required Sections:
Operator instruction:
List sections the asset should include.
Examples:
introduction
problem explanation
why it matters
solution education
FAQ
comparison
trust note
CTA
internal links
claim risk note
summary
28. Assets Needed
Field:
Assets Needed:
Operator instruction:
List supporting assets.
Examples:
image prompt
YouTube thumbnail
VEO3 visual direction
source material
product notes
internal screenshots
comparison table
FAQ list
email subject lines
social captions
29. Approval Owner
Field:
Approval Owner:
Options may include:
Martyn
HeadOffice
Affiliate Brain
Research Brain
Search Intelligence Brain
Ads Brain
Experimentation Brain
Compliance Brain
Finance Brain
Conversion Brain
Sales Brain
AIBS Brain
Other
Operator instruction:
Record who must approve the asset before use.
If unknown, do not publish.
30. Handoff Destination
Field:
Handoff Destination:
Options:
mwmscontentbrain.site
MWMS site
affiliate page
YouTube
VEO3 workflow
email platform
social scheduler
Ads Brain
Affiliate Brain
AIBS Brain
Sales Brain
HeadOffice
MCR only
Other
Operator instruction:
Record where the finished asset should go.
31. Signal To Watch
Field:
Signal To Watch:
Options:
search impressions
search clicks
ranking movement
affiliate clicks
VSL clicks
YouTube views
YouTube retention
email opens
email clicks
social engagement
time on page
scroll depth
conversion support
sales usefulness
objection reduction
manual feedback
Other
Operator instruction:
Choose the signal that will show whether the content was useful.
Do not over-interpret weak signals.
Data Brain owns data quality.
32. Repurposing Potential
Field:
Repurposing Potential:
Options:
None
Social posts
YouTube description
Short video script
VEO3 pre-video support
FAQ
Comparison snippet
Retargeting support
Sales support
Internal training
Other
Operator instruction:
Record possible future reuse.
Do not repurpose without preserving meaning and claim safety.
33. Refresh Trigger
Field:
Refresh Trigger:
Options:
Not applicable
Date-based review
Performance drop
Search intent change
New research
Compliance update
Offer change
Product change
Internal linking update
Campaign learning
Other
Operator instruction:
Record when this asset should be reviewed again.
34. Drafting Status
Field:
Drafting Status:
Options:
Not started
Brief ready
Research required
Drafting
Review required
Approval required
Ready for handoff
Published
Parked
Retired
Operator instruction:
Keep the status current.
35. Notes
Field:
Notes:
Operator instruction:
Add any extra context that will help the operator or reviewer.
Blank Copyable Brief Template
Use this copyable template when creating a new brief.
Content Brief Name:
Date Created:
Source Brain:
Request Type:
Content Asset Type:
Working Title:
Target Audience:
Audience Awareness Stage:
Reader Intent:
Content Goal:
Funnel Role:
Related Offer, Product, Or Topic:
Offer Status:
Research Basis:
Search Intelligence Notes:
Compliance Risk Level:
Claims To Avoid:
Required Proof Or Support:
Key Message:
Supporting Points:
Objections To Address:
Trust Elements Needed:
Internal Linking Notes:
CTA Or Next Step:
Format Requirements:
Tone And Style:
Required Sections:
Assets Needed:
Approval Owner:
Handoff Destination:
Signal To Watch:
Repurposing Potential:
Refresh Trigger:
Drafting Status:
Notes:
Fast Brief Version
Use this when a lightweight brief is enough.
Content Brief Name:
Source Brain:
Content Asset Type:
Audience:
Goal:
Research Basis:
Compliance Risk:
Approval Owner:
Handoff Destination:
Signal To Watch:
Notes:
Affiliate Product Content Pack Brief Version
Use this when creating an asset inside an affiliate product content pack.
Content Brief Name:
Affiliate Product Or Offer:
Offer Status:
Source Brain:
Pack Role:
Asset Type:
Funnel Stage:
Target Audience:
Audience Awareness Stage:
Reader Intent:
Research Basis:
Compliance Risk:
Claims To Avoid:
Required Proof Or Support:
Key Message:
Objections To Address:
CTA Or Next Step:
Internal Linking Notes:
Approval Owner:
Handoff Destination:
Signal To Watch:
Repurposing Potential:
Notes:
SEO Content Brief Version
Use this when planning SEO content.
Content Brief Name:
Target Topic Or Query:
Search Intent:
Source Brain:
Search Intelligence Notes:
Audience:
Audience Awareness Stage:
Content Goal:
Information Gain Angle:
Required Sections:
Internal Linking Notes:
Trust Elements Needed:
Compliance Risk:
Approval Owner:
Handoff Destination:
Signal To Watch:
Refresh Trigger:
Notes:
VEO3 Pre-Video Support Brief Version
Use this when planning support for a VEO3 pre-video.
Content Brief Name:
Related Offer Or Campaign:
Source Brain:
Pre-Video Role:
Hook Angle:
Target Audience:
Audience Awareness Stage:
Key Message:
Narration Direction:
Visual Direction:
On-Screen Text Direction:
Claim Risk:
Claims To Avoid:
Approval Owner:
Handoff Destination:
Signal To Watch:
Notes:
Repurposing Brief Version
Use this when turning approved content into another format.
Content Brief Name:
Source Asset:
Approved Message To Preserve:
New Format:
Target Platform:
Audience:
CTA Or Next Step:
Claims To Avoid:
Approval Owner:
Handoff Destination:
Signal To Watch:
Notes:
Refresh Brief Version
Use this when updating existing content.
Content Brief Name:
Existing Asset:
Refresh Trigger:
Source Signal:
What Needs Updating:
Research Update Needed:
Search Intent Change:
Claims To Review:
Internal Links To Update:
Recommended Action:
Republish
Merge
Redirect
Retire
Park
Approval Owner:
Signal To Watch After Refresh:
Notes:
Operator Warnings
Do Not Use A Brief As Approval
A brief is a planning tool.
It does not approve:
offers
claims
budgets
campaigns
experiments
research verdicts
publishing
Do Not Draft From Missing Research
If the brief requires research and the research basis is missing, mark:
Research required.
Do not invent proof.
Do Not Strengthen Claims
During drafting, do not turn cautious wording into strong claims.
Do not convert signals into guarantees.
Do not convert examples into promises.
Do Not Skip Approval Owner
Every meaningful content asset needs an approval owner.
If approval owner is unknown, do not publish.
Do Not Automate Yet
This template is manual first.
Do not build:
Content Brief Generator
SEO Brief Generator
affiliate pack generator
workflow automation
Supabase tasks
Brain Room routing
until repeated manual use proves the need.
Source Of Truth Note
MCR remains the source of truth for Content Brain.
mwmscontentbrain.site will become the future operational environment.
If a conflict exists between MCR and mwmscontentbrain.site, MCR wins.
Any brief template copy must remain traceable to the original MCR page.
Approval Boundaries
Content Brain must preserve these boundaries:
Affiliate Brain approves affiliate offer direction.
Research Brain provides evidence and research truth.
Search Intelligence Brain supports search demand and SERP opportunity validation.
Ads Brain owns campaign execution and ad testing.
Experimentation Brain owns test validity and learning quality.
Compliance Brain owns compliance interpretation where risk exists.
Finance Brain owns spend, budget, and capital discipline.
Conversion Brain owns conversion strategy.
Sales Brain owns sales progression strategy.
Data Brain owns data quality and signal interpretation.
HeadOffice owns governance oversight.
Content Brain supports these Brains with content assets.
It does not replace them.
First Operational Copy Status
This page is part of the first operational copy preparation batch.
Current status:
Prepared in MCR
Not migrated
Not live on mwmscontentbrain.site
Not connected to plugin/UI
Not automated
Previous operational copies prepared:
Content Brain Home Operational Copy
Content Brain Workflow Operational Copy
Next operational copy to prepare:
Content Brain Publishing Readiness Checklist Operational Copy
Relationship To Content Brain Workflow Operational Copy
The Content Brain Workflow Operational Copy explains when a brief should be created.
This page provides the actual operator template for creating that brief.
Workflow = when to brief.
Content Brief Template = how to brief.
Relationship To Content Brain First Migration Batch Review
The Content Brain First Migration Batch Review identified the Content Brain Content Brief Template as the third page in the operational copy order.
This page prepares the simplified operational copy for that template.
First Migration Batch Review = decision record.
Content Brain Content Brief Template Operational Copy = prepared future operator template page.
Relationship To Content Brain Operational Migration Plan
The Content Brain Operational Migration Plan defines the first practical operating version of mwmscontentbrain.site.
This page implements the content brief template copy from that plan.
The plan remains in MCR.
This page remains in MCR until migration is approved.
Relationship To Content Brain Copy Map
The Content Brain Copy Map classifies the Content Brain Content Brief Template as:
Copy To Content Brain
This page is a prepared simplified operational copy of that future content brief page.
It should remain in MCR until migration is approved.
Relationship To Content Brain Page Registry
This page should be added to the Content Brain Page Registry as:
Page Title: Content Brain Content Brief Template Operational Copy
Document Type: Operational Copy
Parent Page: Content Brain
Status: Draft
Migration Classification: MCR Only First
Plugin Or UI Candidate: Possible Content Brief Generator Later
Notes: Prepared simplified future content brief template copy for mwmscontentbrain.site. Provides reusable operator brief structures for SEO content, affiliate product content packs, affiliate funnel support, YouTube, VEO3 pre-video support, email, social, repurposing, refresh, and AIBS education content while preserving approval boundaries and MCR source-of-truth rules.
Relationship To mwmscontentbrain.site
This page is future content brief template copy for mwmscontentbrain.site.
It should not be copied yet.
It should be used only after:
Content Brain stability is confirmed
first migration batch review is accepted
operational copy batch is prepared
migration timing is approved
MCR source-of-truth links are preserved
Drift Protection
The system must prevent:
this page being treated as live migration
this page being treated as plugin/UI instruction
this page replacing Content Brain Content Brief Template as MCR source
this page replacing Content Brain Canon
this page replacing Content Brain Architecture
this page overriding Content Brain Copy Map
this page bypassing the migration readiness checklist
this page weakening approval boundaries
this page starting automation work too early
this page causing work on M’s active build areas
this page being used to draft unsupported claims
this page being used to skip research
this page being used to skip approval
Architectural Intent
The Content Brain Content Brief Template Operational Copy exists to make the future Content Brain briefing process simple, repeatable, and operator-friendly.
Its architectural role is to translate the MCR-level Content Brief Template into a practical template page for mwmscontentbrain.site.
The goal is to ensure content work starts with structure rather than guesswork.
The future template page should help an operator move from:
request
to brief
to draft
to review
to handoff
without losing source Brain context, approval boundaries, research basis, or signal tracking.
Final Rule
Do not migrate this page until migration is approved.
Do not build a Content Brief Generator from this page yet.
Do not treat this page as source of truth over MCR control pages.
Do not use this page to override Brain authority boundaries.
Do not draft meaningful content without source Brain, research basis, approval owner, and handoff destination.
Content Brain Content Brief Template Operational Copy is a prepared future operator template draft only.
MCR remains source of truth.
Change Log
Version: v1.0
Date: 2026-05-24
Author: HeadOffice
Change: Initial creation of Content Brain Content Brief Template Operational Copy. Defines the prepared simplified future content brief template for mwmscontentbrain.site, including full brief fields, fast brief version, affiliate product content pack brief version, SEO content brief version, VEO3 pre-video support brief version, repurposing brief version, refresh brief version, operator warnings, approval boundaries, source-of-truth note, first operational copy status, and relationships to Content Brain Workflow Operational Copy, Content Brain First Migration Batch Review, Content Brain Operational Migration Plan, Content Brain Copy Map, Content Brain Page Registry, and mwmscontentbrain.site.
Change Impact Declaration
Pages Created:
Content Brain Content Brief Template Operational Copy
Pages Updated:
None
Pages Deprecated:
None
Registries Requiring Update:
Content Brain Page Registry
Content Brain Copy Map
Canon Version Update Required:
No
Change Log Entry Required:
No
END CONTENT BRAIN CONTENT BRIEF TEMPLATE OPERATIONAL COPY v1.0