Brain Name: Content Brain
Document Type: Framework
Status: Active
Version: v1.1
Authority: Content Brain under HeadOffice governance
Applies To: Content Brain topic planning, SEO topic structures, authority-building content, affiliate support content, product education content, and mwmscontentbrain.site operational use
Parent: Content Brain
Last Reviewed: 2026-05-08
Content Brain Topic Architecture Framework
Operational Copy Notice
This page is an operational copy used on mwmscontentbrain.site.
MCR remains the source of truth.
If this page conflicts with the MCR version, the MCR version overrides it.
This protects source-of-truth discipline.
Purpose
The Content Brain Topic Architecture Framework defines how content topics are structured across the MWMS ecosystem.
Its purpose is to ensure that content creation is:
strategically aligned
scalable
non-duplicative
discoverable
connected to customer understanding
connected to offer logic
connected to product education needs
connected to search intent
connected to authority development
connected to internal linking structure
Topic architecture prevents random content creation and ensures each content asset strengthens the MWMS authority system.
This framework converts content planning into a governed structural activity.
Scope
This framework applies to:
blog topic planning
educational content topic structures
authority-building content systems
SEO-informed topic clusters
pillar page planning
supporting article planning
content mapping to customer problems
content mapping to customer journey stages
content mapping to product understanding
content mapping to offer understanding
content mapping to buyer barriers
content mapping to trust gaps
content system expansion planning
This framework governs how content topics are organised and expanded over time.
It does not govern:
persuasion structure by itself
conversion page structure by itself
offer construction logic by itself
product feature definition by itself
raw research generation by itself
campaign testing
paid traffic decisions
plugin implementation
Supabase implementation
Those remain governed by Creative Brain, Conversion Brain, Offer Brain, Product Brain, Research Brain, Ads Brain, Experimentation Brain, and the relevant implementation layers.
Core Principle
Content topics must be structured into intentional architecture.
Content must not be created as isolated assets.
Each content asset must connect to:
customer understanding
problem awareness
solution education
trust development
authority building
offer understanding
product understanding
search intent
buyer journey stage
decision clarity
Unstructured topic creation creates duplication, weak authority signals, and fragmented learning loops.
Structured topic architecture creates compounding authority.
Topic Architecture Layers
Content topics typically fall into structured layers.
Layer 1: Problem Understanding Topics
Focus:
problem awareness
problem definition
problem impact
problem urgency
problem symptoms
problem misconceptions
Examples:
symptom explanation
mistake education
problem identification
myth clarification
why the problem matters
common hidden causes
Purpose:
Increase awareness of problem relevance.
This layer helps the reader understand that the problem is real, relevant, and worth solving.
Layer 2: Solution Understanding Topics
Focus:
solution mechanisms
solution categories
solution comparisons
solution misconceptions
solution trade-offs
solution selection criteria
Examples:
how solution types work
differences between approaches
limitations of alternative methods
what to look for in a solution
common solution myths
Purpose:
Prepare understanding before offer exposure.
This layer helps the reader compare paths without forcing a premature buying decision.
Layer 3: Product Understanding Topics
Focus:
how the product works
how product components function
how product delivers outcome
product usage education
product fit
product limitations
Examples:
feature explanation
use-case explanation
implementation explanation
how it fits into a routine
what results depend on
who it is best suited for
Purpose:
Reduce uncertainty around product adoption.
This layer helps the reader understand the product or offer without hype.
Layer 4: Trust Building Topics
Focus:
credibility development
risk reduction
expectation alignment
realism reinforcement
proof interpretation
transparency
Examples:
case explanation logic
expectations education
realistic outcome framing
responsible claims structure
risk questions
what the product does not do
Purpose:
Increase decision confidence.
This layer helps the reader feel safer, clearer, and less pressured.
Layer 5: Authority Expansion Topics
Focus:
expertise demonstration
depth of understanding
structured explanation systems
interpretation models
market education
expert-level clarity
Examples:
frameworks
models
structured thinking tools
interpretation methods
advanced guides
decision support systems
Purpose:
Increase perceived expertise and intellectual leadership.
This layer helps MWMS build authority that compounds over time.
Layer 6: Conversion Support Topics
Focus:
objection handling
decision support
comparison clarity
FAQ clarity
risk reduction
next-step confidence
Examples:
comparison pages
pre-sell explainers
objection articles
FAQ pages
trust reinforcement pages
decision guides
Purpose:
Support conversion without taking over Conversion Brain authority.
This layer helps the reader move forward with clarity.
Layer 7: Refresh And Maintenance Topics
Focus:
outdated content
declining traffic
search intent shifts
new competitor content
missing proof
weak internal linking
Examples:
updated guides
expanded sections
new FAQ blocks
new comparison points
refreshed topic pages
merged content plans
Purpose:
Keep the topic architecture current, useful, and search-relevant.
Topic Relationship Mapping Rule
Each topic should map to at least one of the following:
customer problem signals
customer questions
customer uncertainty
customer decision friction
product understanding needs
offer understanding needs
search intent
buyer journey stage
trust gap
authority gap
internal linking need
Topics must support decision clarity.
Topics must not exist without structural role.
Topic Expansion Discipline
New topics should only be created when:
a structural gap exists
a repeated question appears
customer understanding requires reinforcement
product education requires clarification
offer education requires support
trust requires strengthening
authority requires expansion
search intent is validated
internal linking architecture needs support
content refresh analysis identifies a gap
Topic creation must remain intentional.
Topic expansion must strengthen the ecosystem.
Topic Approval Questions
Before creating a new topic, ask:
What problem does this topic clarify?
What reader intent does it serve?
What buyer journey stage does it support?
What Brain does it support?
What content cluster does it belong to?
What existing page does it strengthen?
What internal links will it support?
What authority gap does it fill?
What trust gap does it reduce?
What decision friction does it resolve?
What signal will show whether it worked?
If these questions cannot be answered, the topic should remain in review.
Topic Cluster Structure
A strong topic cluster should include:
pillar topic
supporting subtopics
problem-awareness pages
solution-awareness pages
trust-building pages
comparison pages where relevant
FAQ pages where relevant
internal links between related pages
clear content hierarchy
defined reader journey
Each cluster should make it easier for readers and search engines to understand the relationship between pages.
Topic Duplication Prevention
Before creating a new topic, Content Brain should check:
Does a similar page already exist?
Could an existing page be refreshed instead?
Could this become a section inside an existing page?
Does this overlap another Brain’s authority?
Does the title create naming conflict?
Does the topic add new information gain?
If the answer suggests overlap, the topic should be merged, refreshed, or held for review.
Relationship To Research Brain
Research Brain identifies:
customer language
problem signals
emerging questions
behavioural patterns
voice-of-customer signals
buyer objections
decision criteria
market demand signals
Content Brain translates validated signals into structured topic architecture.
Research identifies signal.
Content structures signal into usable content assets.
Content Brain must not invent research authority where evidence is weak.
Relationship To Offer Brain
Offer Brain defines:
value proposition
commercial structure
pricing logic
risk reversal logic
offer promise boundaries
Content Brain may create topics supporting offer understanding.
Offer Brain defines the commercial logic.
Content Brain defines educational structure supporting comprehension.
Content Brain must not change the offer.
Relationship To Product Brain
Product Brain defines:
product structure
product components
feature prioritisation
product evolution logic
delivery capability
Content Brain structures educational content supporting product clarity.
Product Brain defines the product.
Content Brain structures understanding of the product.
Relationship To Affiliate Brain
Affiliate Brain defines:
offer evaluation
affiliate opportunity viability
testing readiness
offer status
pre-sell support needs
Content Brain may create content that supports approved or reviewable affiliate opportunities.
Content Brain must not decide whether an offer should be tested.
Affiliate Brain remains responsible for opportunity evaluation.
Relationship To Conversion Brain
Conversion Brain defines:
conversion logic
message match
friction reduction
trust compression
decision support
Content Brain may create topic structures that support conversion clarity.
Content Brain must not replace Conversion Brain’s authority over conversion architecture.
Relationship To Data Brain
Data Brain validates:
traffic signals
content performance signals
measurement quality
signal reliability
Content Brain may use content performance signals for topic improvement.
Content Brain must not over-interpret weak data.
Relationship To Content Brain Workflow Map
The Workflow Map defines how content work moves through Content Brain.
This framework defines how topics are structured before content production begins.
Workflow Map equals movement.
Topic Architecture Framework equals topic structure.
Relationship To Content Brain SEO Content Brief Standard
The SEO Content Brief Standard defines the structure of SEO briefs.
This framework helps decide what topics deserve briefs.
Topic Architecture Framework equals topic planning.
SEO Content Brief Standard equals brief planning.
Relationship To Content Brain Copy Map
The Content Brain Copy Map classifies this page as:
Destination: Copy To Content Brain
Reason: Topic planning
Source Of Truth: MCR
Future Destination: mwmscontentbrain.site
Future Use: Topic planning and authority architecture
Plugin Or UI Later: Possible topic planner
This operational copy follows that classification.
Future Plugin Or UI Candidate
This framework may later support:
Topic Cluster Planner
Internal Linking Planner
Content Brief Generator
Content Production Queue
Content Refresh Queue
Authority Asset Planner
Content Operations Dashboard
These should not be built yet.
Manual topic planning must prove operational need before plugin or UI development begins.
Structural Rule
Each topic must:
have defined purpose
support decision clarity
strengthen authority
connect to system knowledge
avoid duplication
support reader understanding
fit a topic cluster where relevant
connect to internal linking where relevant
If a topic does not strengthen system clarity, it should not be created.
Drift Protection
The system must prevent:
duplicate topic creation
content production without structural role
topic creation based purely on inspiration
topic structures disconnected from customer understanding
topic structures disconnected from offer understanding
topic structures disconnected from product understanding
topic structures disconnected from search intent
topic structures disconnected from buyer journey stage
random content expansion without architectural logic
topic pages being copied to mwmscontentbrain.site without Copy Map classification
plugin or UI topic planners being built before manual use proves the structure
mwmscontentbrain.site replacing MCR source-of-truth authority
Content architecture must remain structured and compounding.
Architectural Intent
The Content Brain Topic Architecture Framework ensures that content operates as a structured authority-building system rather than a collection of disconnected articles or assets.
By structuring topic relationships deliberately, MWMS strengthens:
trust
clarity
learning speed
expertise perception
decision confidence
search visibility
internal linking strength
funnel support
Topic architecture transforms content into a long-term strategic asset.
The long-term intent is for topic planning to support the operational Content Brain site first manually, then later through a planner, brief generator, or dashboard only after need is proven.
Final Rule
Do not create content topics randomly.
A topic should only enter the Content Brain workflow when it has:
a clear purpose
a defined audience
a structural role
a topic cluster relationship
a reader intent
a system use case
a feedback path where relevant
If a topic does not strengthen clarity, trust, authority, or decision support, it should remain in review.
Change Log
Version: v1.1
Date: 2026-05-08
Author: HeadOffice
Change: Created operational copy for mwmscontentbrain.site. Added Operational Copy Notice, Source Of Truth protection, Parent update for live site, expanded topic layers, added topic approval questions, topic cluster structure, duplication prevention, cross-brain relationships, future plugin or UI boundaries, and drift protection against mwmscontentbrain.site replacing MCR authority.
Version: v1.0
Date: 2026-04-16
Author: HeadOffice
Change: Initial creation of Content Brain Topic Architecture Framework.
Change Impact Declaration
Pages Created:
Content Brain Topic Architecture Framework
Pages Updated:
None
Pages Deprecated:
None
Registries Requiring Update:
None
Canon Version Update Required:
No
Change Log Entry Required:
No
END CONTENT BRAIN TOPIC ARCHITECTURE FRAMEWORK v1.1