Brain Name: Content Brain
Document Type: Operational Repurposing Framework
Status: Active
Version: v1.0
Authority: HeadOffice
Applies To: Content Brain repurposing, approved content reuse, SEO content repurposing, affiliate content repurposing, YouTube support repurposing, VEO3 pre-video support, email repurposing, social content repurposing, FAQ repurposing, comparison content repurposing, refresh support, internal linking support, content asset reuse, handoff readiness, signal feedback, and first operational Content Brain layer use
Parent: Content Brain
Last Reviewed: 2026-05-24
Operational Copy Notice
This page is the live operator repurposing 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 Repurposing defines how approved content assets are adapted into additional useful formats without changing the approved meaning, claims, risk level, or strategic purpose.
Its purpose is to help MWMS get more value from content that already exists.
Repurposing should turn one approved asset into useful support assets for:
SEO
affiliate funnels
YouTube
VEO3 pre-video support
newsletter content
social content
FAQ content
comparison content
trust content
sales support
internal linking
refresh support
Repurposing is not rewriting for the sake of volume.
It is structured reuse of approved content.
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 repurposing 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 adapting approved content into another format.
Use it for:
turning articles into social posts
turning articles into emails
turning articles into newsletter sections
turning articles into YouTube descriptions
turning YouTube scripts into article outlines
turning approved affiliate content into email support
turning SEO content into social snippets
turning trust content into FAQ support
turning comparison content into short-form support
turning objection-handling content into email or YouTube support
turning approved content into VEO3 pre-video support ideas
turning long-form content into short supporting assets
turning refresh work into updated repurposing assets
This page helps the operator repurpose content safely and consistently.
What This Page Does Not Control
This page does not control:
new content approval
affiliate offer approval
affiliate claim approval
campaign approval
budget approval
test validation
final compliance approval
search validation
research verdicts
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 Rule
Only repurpose content that is approved, reviewed, or clearly safe for reuse.
Do not repurpose unapproved, unclear, risky, outdated, or claim-sensitive content without review.
Repurposing must preserve:
meaning
message
claim boundaries
risk level
audience fit
approval status
source context
handoff destination
If repurposing changes the meaning, strengthens a claim, adds a new claim, changes compliance risk, or changes offer positioning, it is no longer simple repurposing.
It becomes new content or revision work and must be reviewed.
Repurposing Principles
Repurposed content should be:
useful
accurate
clear
faithful to the source
format-appropriate
audience-aware
claim-safe
compliance-aware
easy to review
connected to the original asset
Repurposed content should not be:
random
misleading
claim-heavy
out of context
overhyped
stronger than the source
weaker in meaning
detached from the approved message
created only to fill channels
Repurposing Starts With Source Status
Before repurposing, confirm the source asset status.
Approved source assets may be repurposed more freely.
Review-ready assets may be repurposed with care.
Draft assets should not be repurposed unless approved for internal support.
Outdated assets should be refreshed before repurposing.
Compliance-sensitive assets should be reviewed before repurposing.
Affiliate assets should only be repurposed if offer status and claims are clear.
Repurposing Checklist
Use this checklist before repurposing content.
1. Source Asset
Field:
Source Asset:
Operator instruction:
Record the original asset being repurposed.
Examples:
article
SEO brief
YouTube script
affiliate support page
FAQ content
social post
comparison page
trust page
refresh update
2. Source Asset Status
Field:
Source Asset Status:
Options:
Approved
Review-ready
Draft
Published
Needs refresh
Outdated
Compliance-sensitive
Unknown
Operator instruction:
Do not repurpose assets with unclear status.
If the source is outdated, risky, or unknown, park the repurposing request until reviewed.
3. Source Brain
Field:
Source Brain:
Options:
Content Brain
Affiliate Brain
Research Brain
Search Intelligence Brain
Ads Brain
Experimentation Brain
Conversion Brain
Sales Brain
AIBS Brain
HeadOffice
Manual Operator Observation
Other
Operator instruction:
Record where the source asset or repurposing request came from.
If source Brain is unclear, park the request.
4. Supporting Brains
Field:
Supporting Brains:
Operator instruction:
Record any Brains supplying support.
Examples:
Research Brain for evidence
Affiliate Brain for offer status
Search Intelligence Brain for search demand
Compliance Brain for claim risk
Ads Brain for campaign support
Conversion Brain for funnel logic
Sales Brain for sales use
Data Brain for performance signal
HeadOffice for priority
If none, write:
Not applicable
5. Repurposing Purpose
Field:
Repurposing Purpose:
Operator instruction:
Explain why the content is being repurposed.
Examples:
Turn article into email support.
Create social posts from approved FAQ content.
Turn trust content into YouTube description support.
Convert approved affiliate content into VEO3 pre-video support.
Support an existing funnel with shorter assets.
If the purpose is vague, do not proceed.
6. Approved Message To Preserve
Field:
Approved Message To Preserve:
Operator instruction:
Write the core message that must remain unchanged.
This is the message that the repurposed asset must preserve.
If the approved message is unclear, park the request.
7. New Format
Field:
New Format:
Options:
Newsletter section
Social post
Social post set
Short-form script seed
YouTube description
YouTube script support
VEO3 pre-video support
FAQ section
Comparison snippet
Objection-handling snippet
Trust block
Internal support note
Sales support note
Refresh support note
Other
Operator instruction:
Choose the repurposed format.
The format should match the audience, channel, and purpose.
8. Target Audience
Field:
Target Audience:
Operator instruction:
Define who the repurposed asset is for.
Include:
audience type
awareness stage
problem
desired outcome
market or location if relevant
knowledge level
Do not assume the audience is the same as the original source asset.
9. 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 for the repurposed format.
10. Funnel Role
Field:
Funnel Role:
Options:
Awareness
Education
Trust building
Pre-sell
Comparison
Objection handling
Decision support
Follow-up
Retention
Internal support
Not applicable
Operator instruction:
Choose where the repurposed asset fits in the journey.
11. Main Message
Field:
Main Message:
Operator instruction:
Write the repurposed asset’s main message.
It must stay faithful to the approved source message.
12. Sections Or Ideas To Reuse
Field:
Sections Or Ideas To Reuse:
Operator instruction:
List which source sections, points, examples, FAQs, objections, or proof elements should be reused.
Do not reuse unsupported, outdated, or risky sections without review.
13. Sections Or Ideas To Avoid
Field:
Sections Or Ideas To Avoid:
Operator instruction:
List source sections that should not be reused.
Examples:
outdated information
unsupported claims
old offer details
unapproved testimonials
high-risk wording
weak examples
irrelevant sections
14. Claims To Avoid
Field:
Claims To Avoid:
Operator instruction:
List claims that must not be introduced or strengthened.
Include:
unverified product claims
income claims
health claims
legal claims
guarantees
scarcity claims
urgency claims
exaggerated comparisons
unsupported performance claims
unsupported testimonials
unverified “works for everyone” language
Do not leave this blank for affiliate, health, finance, legal, income, product, or compliance-sensitive content.
15. Compliance Sensitivity
Field:
Compliance Sensitivity:
Options:
Low
Medium
High
Unknown
Operator instruction:
Record the risk level.
If risk is medium, high, or unknown, identify the review owner.
16. Required Compliance Review
Field:
Required Compliance Review:
Options:
Not required
Compliance Brain
HeadOffice
Affiliate Brain
Ads Brain
Legal review
Other
Unknown
Operator instruction:
If the repurposed content involves sensitive claims, product claims, affiliate content, health, finance, income, legal, urgency, scarcity, testimonials, or comparisons, identify the review owner.
Do not mark ready if review ownership is unclear.
17. CTA
Field:
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 new format and funnel role.
Do not force a CTA where it does not fit.
18. 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:
Record where the repurposed asset goes next.
If the destination is unclear, park the request.
19. Approval Owner
Field:
Approval Owner:
Operator instruction:
Record who must approve the repurposed asset before use.
Examples:
HeadOffice
Content Brain
Affiliate Brain
Research Brain
Search Intelligence Brain
Ads Brain
Experimentation Brain
Compliance Brain
Conversion Brain
Sales Brain
Finance Brain
Martyn
Other
If approval owner is missing, do not mark ready.
20. Link Back To Source Asset
Field:
Link Back To Source Asset:
Options:
Yes
No
Maybe
Not applicable
Operator instruction:
Decide whether the repurposed asset should link back to the original source asset.
Use Content Brain Internal Linking where meaningful.
21. Internal Links Needed
Field:
Internal Links Needed:
Operator instruction:
List any pages the repurposed asset should link to or from.
If not applicable, write:
Not applicable
22. Signal To Watch
Field:
Signal To Watch:
Options:
email opens
email clicks
social engagement
YouTube views
YouTube retention
VSL clicks
affiliate clicks
internal link clicks
page views
time on page
scroll depth
conversion assist
manual feedback
Other
Operator instruction:
Record what signal should be watched after use.
Do not over-interpret weak signals.
Data Brain owns data quality.
23. Repurposing Status
Field:
Repurposing Status:
Options:
Draft
Needs source review
Needs approval owner
Needs compliance review
Ready for drafting
In drafting
In review
Ready for handoff
Handed off
Published
Parked
Closed
Rejected
Operator instruction:
Keep status current.
Do not mark ready if source status, message, claim risk, approval owner, or handoff destination is unclear.
Repurposing Format Guide
Use the guides below to choose the right repurposed format.
Article To Email
Use when the source article contains a clear educational or persuasive message that can be turned into a shorter direct message.
Watch for:
over-shortening
claim strengthening
missing context
wrong CTA
email hype
Article To Social Post
Use when a single idea, question, objection, or helpful explanation can stand alone.
Watch for:
loss of context
overpromising
unsupported claims
clickbait
too much compression
Article To YouTube Description
Use when the source content supports a video, VSL, or YouTube traffic path.
Watch for:
CTA mismatch
unsupported product claims
too much detail
missing expectation setting
Article To VEO3 Pre Video Support
Use when approved source content can support a short intro, hook, or pre-video concept.
Watch for:
overhyped hooks
unapproved claims
visual exaggeration
wrong tone
CTA creep
FAQ To Social Or Email
Use when repeated questions can be turned into short education content.
Watch for:
removing important limitations
oversimplifying
making claims stronger than the approved answer
Objection Content To Email
Use when an approved objection answer can become follow-up content.
Watch for:
pressure tactics
defensive tone
unsupported reassurance
compliance risk
Trust Content To Funnel Support
Use when a reader may need confidence before moving to the next step.
Watch for:
fake proof
unsupported credibility
overstated authority
missing transparency
Comparison Content To Short Asset
Use when a comparison can be simplified safely.
Watch for:
unfair comparisons
unsupported superiority claims
missing caveats
changing meaning
Repurposing Decision Table
Use this table to decide what happens next.
| Situation | Decision |
|---|---|
| Source approved, message clear, risk low, destination clear | Ready for drafting |
| Source approved but format changes meaning | Needs review |
| Source status unknown | Park |
| Source outdated | Refresh source first |
| Claims risk unclear | Needs compliance review |
| Affiliate offer status unclear | Needs Affiliate Brain review |
| Approved message unclear | Needs source review |
| Audience changes significantly | Needs brief review |
| CTA changes from education to sale | Needs approval |
| Destination unclear | Park |
| Repurposed asset belongs to another Brain | Route back to correct Brain |
When To Mark Ready For Drafting
Mark the repurposing task ready for drafting only when:
source asset is approved or review-ready
source Brain is clear
approved message is clear
new format is clear
target audience is clear
funnel role is clear where relevant
claims to avoid are listed
compliance sensitivity is known
handoff destination is clear
approval owner is known
signal to watch is defined
If any major item is missing, do not mark ready.
When To Park Repurposing
Park the request when:
source asset status is unknown
source asset is outdated
approved message is unclear
new format is unclear
audience is unclear
claim risk is unclear
compliance sensitivity is unknown
approval owner is missing
handoff destination is unclear
the request belongs to another Brain
Parked does not mean rejected.
It means missing information must be resolved before work moves forward.
Meaning Preservation Check
Before repurposed content is used, confirm:
the meaning is preserved
claims are not stronger
risk is not increased
context is not lost
CTA still fits
audience still matches
source message is still clear
approval owner is known
If any answer is no, review before use.
Repurposing Quality Guardrails
Good repurposing should:
preserve the approved message
fit the new format
help the target audience
stay clear and useful
respect claim boundaries
support the reader journey
connect to the right page or asset
create a useful signal to watch
Bad repurposing:
changes the message
adds claims
removes necessary context
uses hype
forces CTAs
creates thin content
duplicates without value
misleads the reader
creates compliance risk
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 Content Briefs for creating briefs
Content Brain Publishing Readiness for final checks
Content Brain Affiliate Content Packs for affiliate product 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 Refresh for improving existing content
Future Plugin Or UI Candidates
This page may later support:
Repurposing Planner
Content Repurposing Queue
Content Brief Generator
Publishing Readiness Checklist UI
Internal Linking Planner
Content Operations Dashboard
Content Signal Feedback 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 Repurposing Framework
After Content Brain Repurposing is created and checked, the older Content Brain Content Repurposing Framework page should be handled as follows:
If it is only a duplicate operational repurposing 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 repurposing pages.
The active operator repurposing page should be:
Content Brain Repurposing
Drift Protection
The system must prevent:
repurposing unapproved content
repurposing outdated content without refresh
repurposed content changing the approved meaning
repurposed content strengthening claims
repurposed content adding unsupported claims
repurposed content changing compliance risk
affiliate repurposing happening before offer status is clear
repurposed content losing source context
repurposed content being created only for volume
old repurposing framework pages being treated as the current operator repurposing page after this clean page is created
future UI being built before manual repurposing use proves need
Content Brain taking authority from Affiliate Brain, Research Brain, Search Intelligence Brain, Ads Brain, Experimentation Brain, Conversion Brain, Compliance Brain, Finance Brain, Data Brain, SIT Brain, or HeadOffice
Architectural Intent
Content Brain Repurposing exists to make approved content work harder without creating uncontrolled content drift.
Its role is to turn strong content assets into useful additional formats while preserving meaning, claims, risk level, and system alignment.
Repurposing should help MWMS create:
more reusable content assets
stronger multi-format support
better affiliate funnel support
better email and social support
better YouTube support
safer VEO3 pre-video support
better refresh value
stronger internal linking opportunities
more learning signals
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
Repurposing must preserve the approved meaning.
No repurposed content should be used if it changes the message, strengthens claims, adds risk, removes context, or lacks an approval owner.
When in doubt, park the task 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 repurposing page for mwmscontentbrain.site based on MCR Content Brain Repurposing Operational Copy and the existing Content Brain Content Repurposing Framework. Defines the live Content Brain Repurposing page for the first operational Content Brain layer, including source asset status, approved message preservation, format selection, repurposing checklist, format guide, decision table, ready rules, parking rules, meaning preservation check, quality guardrails, 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 Repurposing
Pages Updated:
None
Pages To Delete Or Move To Legacy After Validation:
Content Brain Content Repurposing Framework
Pages Deprecated:
Content Brain Content Repurposing Framework as active operator repurposing page
Registries Requiring Update:
None
Canon Version Update Required:
No
Change Log Entry Required:
No
END CONTENT BRAIN REPURPOSING v1.0