Brain Name: Content Brain
Document Type: Integration Map
Status: Active Integration Map
Version: v1.0
Authority: HeadOffice
Applies To: Content Brain, HeadOffice Brain, Research Brain, Search Intelligence Brain, Affiliate Brain, Ads Brain, Experimentation Brain, Conversion Brain, Compliance Brain, Data Brain, Finance Brain, Strategy Brain, SIT Brain, and future Content Brain system wiring
Parent: Content Brain
Last Reviewed: 2026-06-02
Purpose
The Content Brain Cross-Brain Integration Map defines how Content Brain connects with the wider MWMS ecosystem.
Content Brain should not operate as an isolated content-production area.
Content Brain should operate as a structured communication layer that receives intelligence from other Brains, turns that intelligence into usable content structures, and sends useful outputs back into the ecosystem.
This page defines:
which Brains send inputs to Content Brain
which Brains receive outputs from Content Brain
what Content Brain is responsible for
what Content Brain is not responsible for
what future wiring M may need to build
which workflows should remain manual until proven
how Content Brain supports the wider MWMS system without taking authority from other Brains
The goal is to make Content Brain integration-ready before technical wiring begins.
Current Status
Content Brain now has a clean first operational layer on mwmscontentbrain.site.
The active first operational layer is:
Content Brain
Content Brain Affiliate Content Packs
Content Brain Affiliate Funnel Support
Content Brain Content Briefs
Content Brain Internal Linking
Content Brain Publishing Readiness
Content Brain Refresh
Content Brain Repurposing
Content Brain SEO Content Briefs
Content Brain Workflow
These pages define the manual operating layer.
This Cross-Brain Integration Map sits above the operational layer as a system-connection page.
It explains how Content Brain should eventually work with the other Brains when M wires the systems together.
Core Principle
Content Brain is not just a content-writing Brain.
Content Brain is the communication-structure Brain.
It turns intelligence, offers, search demand, audience problems, funnel needs, compliance constraints, and performance signals into structured content assets.
Content Brain must help the whole MWMS ecosystem communicate clearly.
Content Brain should improve:
reader understanding
search usefulness
affiliate support
ad-to-content message match
conversion readiness
trust formation
content refresh discipline
content repurposing discipline
internal linking clarity
system learning
cross-brain handoff quality
Content Brain should not replace the authority of other Brains.
It should support them.
Integration Role Inside MWMS
Content Brain sits between intelligence and communication output.
The broad flow is:
HeadOffice sets priority.
Research Brain identifies problems, language, evidence, and market signals.
Search Intelligence Brain identifies search demand, SERP patterns, and intent.
Affiliate Brain identifies offer context, offer status, and affiliate support needs.
Ads Brain identifies ad-to-content message match needs.
Experimentation Brain identifies testable messaging or content variations.
Conversion Brain identifies friction, objections, and decision-support gaps.
Compliance Brain defines claim boundaries and risk review needs.
Data Brain validates performance signals.
Finance Brain evaluates resource and capital implications.
Content Brain turns approved or review-ready inputs into structured content assets, briefs, refresh plans, repurposing plans, internal linking plans, publishing readiness checks, and support content.
HeadOffice reviews visibility, priority, and cross-brain coherence.
What Content Brain Receives
Content Brain may receive inputs from other Brains.
These inputs may include:
research insights
audience language
search intent
offer education needs
affiliate support needs
conversion friction
ad message match needs
content performance signals
trust gaps
compliance constraints
topic gaps
internal linking gaps
repurposing opportunities
refresh triggers
HeadOffice priorities
Content Brain should not act on every input automatically.
Inputs must be classified through Content Brain Workflow before becoming content work.
What Content Brain Produces
Content Brain may produce:
content briefs
SEO content briefs
affiliate product content packs
affiliate funnel support content
publishing readiness checks
internal linking plans
repurposing plans
refresh plans
content optimization notes
topic architecture notes
topic cluster support
trust support content
FAQ content
comparison content
pre-sell support content
YouTube description support
VEO3 pre-video support
email support content
landing page support content
content signal notes
content handoff notes
Content Brain outputs should be structured, reviewable, and useful.
Content Brain should not produce uncontrolled creative output.
What Content Brain Does Not Own
Content Brain does not own:
research verdicts
search validation
offer approval
affiliate opportunity approval
ad campaign approval
conversion architecture
compliance interpretation
data reliability
budget decisions
experiment verdicts
technical wiring
Supabase schema
plugin UI
Brain Room routing
automation execution
Content Brain may support these areas, but it must not take their authority.
HeadOffice Brain Integration
Inputs From HeadOffice
HeadOffice may send Content Brain:
strategic priorities
business direction
content system priorities
cross-brain instructions
major content objectives
priority offers
priority markets
priority pages
workflow improvement needs
risk concerns
system build priorities
HeadOffice tells Content Brain what matters most.
Outputs To HeadOffice
Content Brain may send HeadOffice:
content bottleneck reports
page readiness status
content priority notes
legacy cleanup status
content workflow gaps
cross-brain dependency notes
future build candidate notes
content system risks
content output summaries
Content Brain should help HeadOffice see whether content work is moving the business forward.
Authority Boundary
HeadOffice owns strategic priority.
Content Brain should not decide major business priorities alone.
Future Wiring Candidate
Later, M may wire:
Content Brain status reporting into HeadOffice dashboard
Content Brain readiness signals into HeadOffice task view
Content Brain future build candidates into HeadOffice planning
Content Brain content bottlenecks into HeadOffice alerts
Manual use must prove which reports are actually useful first.
Research Brain Integration
Inputs From Research Brain
Research Brain may send Content Brain:
audience problems
market language
voice-of-customer patterns
problem definitions
evidence summaries
customer objections
knowledge gaps
market trend signals
audience awareness signals
topic opportunities
Research Brain gives Content Brain the raw intelligence needed to create useful content.
Outputs To Research Brain
Content Brain may send Research Brain:
content gaps
reader confusion patterns
questions found during content planning
missing evidence requests
topic clarification needs
objection patterns
content signal notes
audience language found during content use
Content Brain should return useful content-derived signals to Research Brain.
Authority Boundary
Research Brain owns evidence quality and research verdicts.
Content Brain must not invent evidence or treat weak content signals as research proof.
Future Wiring Candidate
Later, M may wire:
Research Brain insight → Content Brain content brief draft
Content Brain content gap → Research Brain research request
Content signal note → Research Brain intake
Research verdict → Content Brain source field
Manual use must prove the exact fields before automation.
Search Intelligence Brain Integration
Inputs From Search Intelligence Brain
Search Intelligence Brain may send Content Brain:
search demand
SERP patterns
query intent
keyword clusters
topic gaps
competitor page patterns
content format expectations
SERP freshness requirements
entity coverage expectations
search opportunity notes
Search Intelligence Brain gives Content Brain the search intelligence needed to produce search-useful content.
Outputs To Search Intelligence Brain
Content Brain may send Search Intelligence Brain:
SEO brief requests
topic validation requests
SERP mismatch notes
keyword cannibalisation concerns
content gap discoveries
refresh triggers
internal linking opportunities
search-intent uncertainty
Content Brain should ask Search Intelligence Brain for validation when search matters.
Authority Boundary
Search Intelligence Brain owns search validation and SERP interpretation.
Content Brain should not treat a topic as search-validated unless Search Intelligence Brain has confirmed it where search matters.
Future Wiring Candidate
Later, M may wire:
Search Intelligence topic opportunity → Content Brain SEO Content Brief
Content Brain Refresh trigger → Search Intelligence review
Content Brain Internal Linking gap → Search Intelligence cluster review
Search intent field → SEO Brief Generator
Manual SEO brief use must prove which fields are needed.
Affiliate Brain Integration
Inputs From Affiliate Brain
Affiliate Brain may send Content Brain:
offer status
offer positioning
affiliate opportunity notes
pre-sell needs
product education needs
objection patterns
trust gaps
comparison needs
VSL support needs
YouTube support needs
affiliate content pack requests
affiliate funnel-stage requirements
Affiliate Brain gives Content Brain the offer context needed to support affiliate revenue paths.
Outputs To Affiliate Brain
Content Brain may send Affiliate Brain:
affiliate content packs
pre-sell content
FAQ content
trust support content
comparison support content
YouTube description support
VEO3 pre-video support
affiliate funnel support plans
offer education gaps
claim-risk flags
content readiness notes
Content Brain helps Affiliate Brain create better support around offers.
Authority Boundary
Affiliate Brain owns offer logic, offer evaluation, affiliate opportunity decisions, and testing readiness.
Content Brain must not approve offers.
Content Brain must not treat unclear offer status as approved.
Future Wiring Candidate
Later, M may wire:
Affiliate Brain approved offer → Content Brain Affiliate Content Pack request
Affiliate Brain funnel need → Content Brain Affiliate Funnel Support task
Content Brain claim-risk flag → Compliance Brain review
Content Brain asset status → Affiliate Brain campaign readiness
Manual use must prove the exact workflow before automation.
Ads Brain Integration
Inputs From Ads Brain
Ads Brain may send Content Brain:
ad angles
campaign message needs
landing page support needs
YouTube description needs
pre-video support needs
message match concerns
retargeting content needs
ad-to-page mismatch notes
creative support requests
Ads Brain gives Content Brain the paid traffic context needed to support continuity.
Outputs To Ads Brain
Content Brain may send Ads Brain:
YouTube descriptions
landing page support sections
pre-sell support content
trust support content
FAQ support
message match notes
VEO3 pre-video support
ad-to-content alignment notes
content readiness status
Content Brain helps Ads Brain keep the message path clear.
Authority Boundary
Ads Brain owns campaign execution, paid testing, targeting, budgets, and ad performance decisions.
Content Brain must not approve campaigns.
Future Wiring Candidate
Later, M may wire:
Ads Brain campaign need → Content Brain support content request
Content Brain Publishing Readiness → Ads Brain launch support status
Ads Brain mismatch signal → Content Brain Refresh or brief task
Manual ad-support workflow must prove which handoffs matter.
Experimentation Brain Integration
Inputs From Experimentation Brain
Experimentation Brain may send Content Brain:
test hypotheses
variant needs
angle tests
message structure tests
content-path tests
CTA tests
funnel-stage assumptions
controlled variation requirements
Experimentation Brain gives Content Brain structured testing needs.
Outputs To Experimentation Brain
Content Brain may send Experimentation Brain:
content variants
angle support copy
brief variants
message sequence variants
pre-sell variants
refresh hypotheses
content test support notes
signal-to-watch definitions
Content Brain can help create the content assets needed for valid tests.
Authority Boundary
Experimentation Brain owns test design, test validity, and experiment verdicts.
Content Brain must not declare winners.
Content Brain must not interpret weak content performance as a valid test outcome.
Future Wiring Candidate
Later, M may wire:
Experimentation Brain approved test → Content Brain variant request
Content Brain variant output → Experimentation Brain test asset
Content Brain signal notes → Experimentation Brain hypothesis review
Manual testing support must prove the structure first.
Conversion Brain Integration
Inputs From Conversion Brain
Conversion Brain may send Content Brain:
conversion friction points
objection patterns
trust gaps
CTA mismatch notes
decision support needs
message match requirements
funnel clarity needs
landing page support needs
Conversion Brain gives Content Brain the decision-readiness context needed to produce conversion-support content.
Outputs To Conversion Brain
Content Brain may send Conversion Brain:
FAQ content
objection-handling content
trust content
decision guides
expectation-setting content
message clarity support
CTA support notes
conversion-support content plans
Content Brain helps improve the environment before and around conversion.
Authority Boundary
Conversion Brain owns conversion architecture and conversion interpretation.
Content Brain supports conversion readiness but does not own conversion logic.
Future Wiring Candidate
Later, M may wire:
Conversion friction signal → Content Brain content request
Content Brain support asset → Conversion Brain readiness review
Content Brain Publishing Readiness → Conversion support status
Manual conversion-support use must prove the useful triggers first.
Compliance Brain Integration
Inputs From Compliance Brain
Compliance Brain may send Content Brain:
claim boundaries
risk warnings
sensitive-topic rules
approved wording constraints
claim-safe phrasing guidance
affiliate disclosure requirements
health claim limits
income claim limits
finance claim limits
legal claim limits
platform policy notes
Compliance Brain gives Content Brain the risk boundaries needed to avoid unsafe content.
Outputs To Compliance Brain
Content Brain may send Compliance Brain:
claim-risk flags
review requests
sensitive content alerts
comparison risk notes
affiliate disclosure questions
health/income/finance/legal claim concerns
before-and-after claim concerns
urgency or scarcity concerns
Content Brain should escalate risk instead of guessing.
Authority Boundary
Compliance Brain owns compliance interpretation.
Content Brain must not approve sensitive claims.
Future Wiring Candidate
Later, M may wire:
Content claim-risk flag → Compliance Brain review task
Compliance Brain approved wording → Content Brain brief field
Publishing Readiness risk status → Content Brain handoff status
Manual claim review must prove required risk fields first.
Data Brain Integration
Inputs From Data Brain
Data Brain may send Content Brain:
traffic signals
engagement signals
scroll depth
internal link behaviour
CTA interaction
affiliate click signals
VSL click signals
refresh triggers
content performance reports
signal confidence levels
measurement reliability notes
Data Brain gives Content Brain validated signal context.
Outputs To Data Brain
Content Brain may send Data Brain:
signal-to-watch definitions
content asset IDs where relevant
content status notes
publishing readiness status
refresh actions
repurposing actions
optimization hypotheses
content learning notes
Content Brain should help Data Brain know what to measure and why.
Authority Boundary
Data Brain owns measurement reliability, signal confidence, tracking quality, and data interpretation.
Content Brain must not over-interpret weak signals.
Future Wiring Candidate
Later, M may wire:
Content asset → signal-to-watch field
Data signal → Content Brain Refresh trigger
Optimization hypothesis → Data Brain review window
Content Operations Dashboard → Data Brain metrics
Manual signal tracking must prove useful metrics first.
Finance Brain Integration
Inputs From Finance Brain
Finance Brain may send Content Brain:
resource limits
budget constraints
content production cost guidance
contractor approval signals
capital allocation rules
expected return thresholds
priority constraints
Finance Brain helps Content Brain avoid wasting resources.
Outputs To Finance Brain
Content Brain may send Finance Brain:
content workload estimates
production volume needs
resource requests
content system build candidates
contractor support needs
content ROI questions
time-cost trade-off notes
Finance Brain can use Content Brain signals to understand whether content work is worth the resource investment.
Authority Boundary
Finance Brain owns capital, budget, tool-spend, and resource decisions.
Content Brain must not approve spending.
Future Wiring Candidate
Later, M may wire:
Content production request → Finance review if resource cost is high
Content system build candidate → Finance priority review
Content workload report → Finance resource planning
Manual resource tracking must prove which costs matter.
Strategy Brain Integration
Inputs From Strategy Brain
Strategy Brain may send Content Brain:
positioning direction
market direction
brand narrative direction
strategic themes
long-term messaging priorities
audience positioning
business model focus
Strategy Brain helps Content Brain stay aligned with long-term direction.
Outputs To Strategy Brain
Content Brain may send Strategy Brain:
narrative gaps
positioning inconsistencies
content theme conflicts
brand clarity concerns
audience-message mismatch notes
topic direction insights
Content Brain can reveal when content direction is drifting.
Authority Boundary
Strategy Brain owns long-term strategic positioning.
Content Brain supports strategy through structured communication.
Future Wiring Candidate
Later, M may wire:
Strategy priority → Content Brain theme brief
Content theme drift → Strategy Brain review
Content narrative map → Strategy Brain visibility
Manual strategy-support use must prove the useful connection points.
SIT Brain Integration
Inputs From SIT Brain
SIT Brain may send Content Brain:
system integrity rules
source-of-truth constraints
drift warnings
governance boundaries
page hierarchy rules
naming rules
system-risk flags
SIT Brain helps protect Content Brain from structure drift.
Outputs To SIT Brain
Content Brain may send SIT Brain:
drift concerns
duplicate page risks
source-of-truth conflicts
naming conflicts
legacy page confusion
active-vs-legacy boundary problems
workflow integrity risks
SIT Brain can help keep Content Brain structurally stable.
Authority Boundary
SIT Brain owns system integrity and structural governance.
Content Brain must not ignore source-of-truth rules.
Future Wiring Candidate
Later, M may wire:
Content Brain page update → SIT drift check
Legacy page status → SIT review
Content Brain integration change → SIT integrity log
Manual integrity checks must prove which checks are worth automating.
Cross-Brain Input Types
Content Brain should classify incoming requests by input type.
Possible input types:
Research Insight
Search Opportunity
Affiliate Support Need
Ad Support Need
Experiment Variant Request
Conversion Support Need
Compliance Review Constraint
Data Signal
Finance Resource Constraint
HeadOffice Priority
Strategy Direction
SIT Governance Rule
Manual Operator Request
Unknown Input
Unknown inputs should be parked until clarified.
Cross-Brain Output Types
Content Brain should classify outputs by output type.
Possible output types:
Content Brief
SEO Content Brief
Affiliate Content Pack
Affiliate Funnel Support Plan
Publishing Readiness Review
Internal Linking Plan
Repurposing Plan
Refresh Plan
Optimization Note
Topic Architecture Note
Topic Cluster Plan
Trust Support Asset
FAQ Asset
Comparison Asset
Pre-Sell Asset
YouTube Support Asset
VEO3 Support Asset
Email Support Asset
Landing Support Asset
Signal-To-Watch Definition
Cross-Brain Handoff Note
Unknown Output
Each output should have a destination Brain or operator use case.
Integration Workflow
The standard cross-brain integration workflow is:
Input received
Source Brain identified
Input type classified
Authority boundary checked
Missing information identified
Content Brain Workflow applied
Correct operational page selected
Content asset or plan created
Publishing readiness checked where relevant
Output destination assigned
Signal to watch defined where possible
Learning returned to the correct Brain
HeadOffice visibility updated where needed
This workflow should remain manual until repeated use proves what should be systemised.
Integration Decision Table
| Situation | Decision |
|---|---|
| Research insight needs content translation | Route to Content Brain Content Briefs |
| Search opportunity needs SEO content | Route to Content Brain SEO Content Briefs |
| Affiliate offer needs support assets | Route to Content Brain Affiliate Content Packs |
| Affiliate funnel stage needs content | Route to Content Brain Affiliate Funnel Support |
| Existing page needs improvement | Route to Content Brain Refresh |
| Approved content can be reused | Route to Content Brain Repurposing |
| Page relationship needs planning | Route to Content Brain Internal Linking |
| Content is ready for use check | Route to Content Brain Publishing Readiness |
| Input is vague | Park in Content Brain Workflow |
| Offer status is unclear | Route to Affiliate Brain |
| Search intent is unclear | Route to Search Intelligence Brain |
| Evidence is missing | Route to Research Brain |
| Claim risk exists | Route to Compliance Brain |
| Data signal is weak | Route to Data Brain |
| Resource cost is material | Route to Finance Brain |
| Priority is unclear | Route to HeadOffice |
| Governance conflict exists | Route to SIT Brain |
Manual-First Integration Rule
Content Brain should be integrated manually before technical wiring.
Manual-first means:
the pages are used by the operator
repeatable handoffs are observed
common input types become clear
common output types become clear
bottlenecks are identified
only useful workflows become build candidates
Manual-first does not mean the system will remain manual forever.
Manual-first protects MWMS from building the wrong system too early.
Future System Wiring Candidates
Once manual workflow proves the need, Content Brain may later support:
Content Opportunity Queue
Content Production Queue
Content Refresh Queue
Content Repurposing Queue
Content Operations Dashboard
Content Brief Generator
SEO Brief Generator
Affiliate Content Pack Generator
Affiliate Funnel Support Planner
Internal Linking Planner
Publishing Readiness Checklist UI
Content Signal Feedback Dashboard
Cross-Brain Handoff Router
Content Brain AI Employee Router
Content Brain Task Status Dashboard
Content Brain Integration Log
These are future candidates only.
They should be built only after repeated manual use proves the exact fields, rules, and handoff paths.
Future Content Brain AI Employee Candidates
Possible future AI Employees include:
Content Strategy Employee
Content Briefing Employee
SEO Brief Employee
Affiliate Content Pack Employee
Affiliate Funnel Support Employee
Publishing Readiness Employee
Internal Linking Employee
Repurposing Employee
Refresh Employee
Content Optimization Employee
Content Trust Review Employee
Content Signal Feedback Employee
Content Governance Employee
Cross-Brain Handoff Employee
These are not approved builds yet.
They are candidate roles only.
Manual workflow must prove which employees are genuinely needed.
Build-Readiness Criteria
A Content Brain workflow becomes build-ready only when:
the manual workflow is repeated
the source Brain is clear
the output type is clear
the status path is clear
required fields are clear
approval owner is clear
risk rules are clear
handoff destination is clear
signal-to-watch is useful
operator value is proven
HeadOffice agrees it should be systemised
M has a clean spec to build from
Until then, the workflow remains manual.
Integration Guardrails
Content Brain integration must prevent:
Content Brain taking authority from other Brains
outputs being created without source Brain context
content work starting from vague inputs
affiliate content being created before offer status is clear
SEO content being created before search intent is clear
claim-sensitive content bypassing Compliance Brain
weak data being over-interpreted
resource-heavy work bypassing Finance Brain
campaign support being mistaken for campaign approval
experiment support being mistaken for experiment verdict
legacy pages overriding active operational pages
manual workflow being skipped before system build
M being asked to build vague systems without proven workflow logic
M Build Handoff Rule
When Content Brain is eventually ready for technical wiring, M should receive build-ready specifications only.
A build-ready specification must include:
page or workflow name
purpose
input fields
output fields
status values
source Brain
destination Brain
approval rules
risk rules
handoff rules
error/parking rules
dashboard needs
data needs
user role needs
manual workflow evidence
priority level
M should not be expected to invent Content Brain logic.
Content Brain should hand M clean system instructions when the time comes.
Operator Role
Martyn’s current role in Content Brain is to:
clean the page structure
confirm active vs legacy pages
prove the manual workflow
identify repeated work
decide what is useful
stop drift
protect the vision
shape the integration logic
prepare future build-ready specs
This work does not replace M’s development role.
It prepares the logic M will eventually wire.
Architectural Intent
Content Brain Cross-Brain Integration Map exists to make Content Brain ecosystem-ready.
The intent is not only to have clean Content Brain pages.
The intent is to create a Content Brain that can connect cleanly with the whole MWMS ecosystem.
A finished Content Brain should be able to:
receive inputs from other Brains
produce structured outputs
respect authority boundaries
support revenue paths
improve content quality
improve search usefulness
support affiliate systems
support ad message match
support conversion readiness
support compliance safety
return learning signals
help HeadOffice see what is happening
give M a clean build path later
Content Brain should become a bridge between intelligence and useful communication.
Final Rule
Content Brain must work with the wider MWMS ecosystem.
It should not be an isolated content site.
It should not become a random article factory.
It should not replace other Brains.
It should translate intelligence into structured, useful, trustworthy, build-ready content systems.
Manual workflow comes first.
System wiring comes later.
M should wire proven logic, not vague ideas.
Change Log
Version: v1.0
Date: 2026-06-02
Author: HeadOffice
Change: Created Content Brain Cross-Brain Integration Map to define how Content Brain connects with HeadOffice Brain, Research Brain, Search Intelligence Brain, Affiliate Brain, Ads Brain, Experimentation Brain, Conversion Brain, Compliance Brain, Data Brain, Finance Brain, Strategy Brain, and SIT Brain. Added input/output relationships, authority boundaries, integration workflow, future wiring candidates, future AI Employee candidates, build-readiness criteria, M build handoff rule, operator role, and guardrails for manual-first integration.
Change Impact Declaration
Pages Created:
Content Brain Cross-Brain Integration Map
Pages Updated:
None
Pages Renamed:
None
Pages Deprecated:
None
Registries Requiring Update:
Content Brain Page Registry should be updated later to include this page after creation.
Canon Version Update Required:
No immediate canon update required unless HeadOffice decides this integration map becomes canonical.
Change Log Entry Required:
Recommended later in Content Brain Page Registry or Content Brain Architecture if this becomes an active integration reference.
END CONTENT BRAIN CROSS-BRAIN INTEGRATION MAP v1.0