Content Brain Architecture

Document Type: Architecture
Version: v1.1
Parent Page: Content Brain
Status: Active
Migration Classification: MCR Only
Plugin Or UI Candidate: No
Notes: Defines the complete Content Brain architecture from request and qualification through project definition, asset planning, intelligence assembly, briefing, production, editing, specialist review, human approval, publishing preparation, delivery, measurement and lifecycle management. Separates MCR authority, the Content Brain operational site, Supabase records and future automation. Site Intelligence is one supporting architectural layer and does not define the complete Content Brain system.

Content Brain Architecture

Purpose

The Content Brain Architecture defines how MWMS converts approved business needs, strategic direction and intelligence into complete, usable and governed content assets.

The Architecture supports the full Content Brain mandate established by the Content Brain Canon.

Content Brain is not only a structural messaging layer.

Content Brain is not only a content brief system.

Content Brain is not only a Site Intelligence system.

Content Brain is the governed content production and lifecycle operating system responsible for:

identifying content needs
qualifying content work
assembling approved inputs
planning content projects
creating content briefs
producing complete content assets
editing and improving content
supporting human review and approval
preparing content for publication or delivery
receiving performance signals
refreshing, repurposing, improving, consolidating or retiring content

The Architecture must support both:

controlled production
long-term content improvement

It must prevent governance from becoming so heavy that content is never produced.

It must also prevent content production from becoming uncontrolled, unsupported or disconnected from MWMS authority.

Architectural Objective

The architectural objective is to provide a complete operating path from an approved content need to a finished and reviewable content asset.

The primary architectural flow is:

Request Or Opportunity
→ Qualification
→ Intelligence Assembly
→ Content Project Definition
→ Asset Planning
→ Briefing
→ Content Creation
→ Editing And Quality Control
→ Specialist Review
→ Human Approval
→ Publishing Preparation
→ Delivery Or Publication
→ Measurement
→ Refresh, Repurposing, Improvement Or Retirement

This flow may support:

one content asset
multiple related assets
a content campaign
a website content system
an affiliate content pack
a newsletter and email sequence
a social media content series
a group of video or advertising scripts
a manual or training package
a refresh programme
a repurposing programme

The Architecture must remain broad enough to support current and future MWMS business models.

Core Architectural Principles

The Content Brain Architecture must follow these principles.

Production Must Remain Central

Content Brain must be capable of producing complete content.

Planning, research, records, briefs and governance must support production.

They must not replace production.

Every Asset Must Have A Purpose

Content must originate from a defined:

objective
problem
opportunity
request
audience need
campaign need
site need
product need
offer need
operational need

Content must not be produced merely because a topic is available.

Existing Content Must Be Checked First

Before creating new content, Content Brain must determine whether the correct action is:

create
update
refresh
expand
merge
repurpose
relink
correct
retire
archive
take no action

This protects against duplication, page bloat and unnecessary production.

Approved Intelligence Must Drive Production

Content Brain consumes approved inputs from relevant Brains and human operators.

It must not invent missing:

evidence
research
offer details
product facts
customer experiences
statistics
claims
strategic direction

Where required information is missing, the work must be paused, returned or escalated.

Production Must Remain Traceable

A content asset should remain connected to:

the request that caused it
the objective it supports
the audience it serves
the source intelligence used
the approved evidence
the content project
the destination or channel
the required approval
the final publication or delivery state

Human Control Must Remain Active

The current Content Brain operating model remains human controlled.

Humans retain authority over:

final content acceptance
final publication
major strategic interpretation
unsupported or ambiguous claims
high-risk compliance decisions
cross-Brain escalation
changes to production authority

Future automation may support the workflow but must not bypass these controls unless separately authorised.

Architecture Must Not Be Frozen Too Early

This Architecture defines the required layers, responsibilities and relationships.

It does not permanently lock:

the final plugin interface
the final database schema
the final workflow screen layout
the final automation platform
the final worker structure
the final AI Employee structure
the final publishing integrations

Implementation must follow proven operating needs.

Architecture Overview

The Content Brain Architecture contains the following primary layers:

Request And Intake Layer
Qualification And Action Decision Layer
Intelligence Assembly Layer
Content Project Layer
Asset Planning Layer
Brief And Outline Layer
Content Production Layer
Editing And Quality Control Layer
Specialist Review And Approval Layer
Publishing Preparation Layer
Delivery And Publication Layer
Measurement And Feedback Layer
Content Lifecycle Layer
Site Intelligence Support Layer
Content Knowledge And Reuse Layer
Data And Records Layer
Interface And Operational Layer
Governance And Integrity Layer
Future Automation And Worker Layer

These layers work together but must remain distinguishable.

Temporary implementation work in one layer must not redefine the complete Content Brain architecture.

1. Request And Intake Layer

The Request And Intake Layer receives a defined content need, opportunity or instruction.

A request may originate from:

Martyn
HeadOffice
Strategy Brain
Affiliate Brain
AIBS Brain
PPL Brain
Ads Brain
Research Brain
Customer Brain
Ecommerce Brain
Product Brain
Conversion Brain
Search Intelligence
Site Intelligence
Data Brain
Experimentation Brain
an approved campaign
a website build
an existing content refresh need
a customer or client requirement
a manual human request

A request may ask Content Brain to:

create one asset
create a group of assets
create a content pack
update an existing asset
review a website
plan a content system
create campaign support content
create social content
create scripts
create newsletters or emails
create a manual or guide
refresh existing content
repurpose existing content
prepare content for publication
review content quality
identify missing content

The Request And Intake Layer should eventually capture:

request title
request source
requesting Brain or human
business or project
objective
audience
asset requirement
destination
urgency
known dependencies
available source material
approval owner
current status

A request does not automatically become a production task.

It must first pass qualification.

2. Qualification And Action Decision Layer

The Qualification And Action Decision Layer determines what action is actually required.

Content Brain must decide whether the request should result in:

new content
a refresh
an expansion
a correction
a merge
a repurposing action
an internal-linking action
a format adaptation
a content pack
a retirement recommendation
an archive action
no action
escalation to another Brain
a request for missing information

Qualification should assess:

whether the objective is clear
whether the audience is known
whether the destination is known
whether existing content already solves the need
whether the request belongs to Content Brain
whether Research Brain must act first
whether Strategy Brain direction is required
whether Affiliate Brain or Ads Brain must define campaign needs
whether Compliance Brain review is required
whether source evidence is sufficient
whether the content request is economically or operationally useful
whether producing content would create duplication or unnecessary work

The result of qualification should be a clear action decision.

The system must avoid vague outcomes where a practical decision can be made.

3. Intelligence Assembly Layer

The Intelligence Assembly Layer gathers the approved inputs needed to produce accurate and useful content.

Inputs may include:

strategic positioning
campaign direction
offer intelligence
product information
customer research
customer language
awareness stage
lifecycle stage
search intent
keyword and query context
competitor context
site intelligence
existing content
verified evidence
source material
compliance requirements
voice and tone guidance
brand guidance
creative direction
conversion requirements
platform requirements
previous performance data
experiment learnings
financial constraints
publication destination requirements

The Intelligence Assembly Layer must distinguish between:

confirmed facts
approved strategic direction
validated research
emerging signals
working assumptions
human instructions
content-specific interpretation

Content Brain may perform limited content-specific checks.

It must not duplicate Research Brain’s broad research authority.

Where deep research is required, Content Brain must request or await the appropriate research input.

4. Content Project Layer

The Content Project Layer groups related content work around one objective.

A content project may include:

one asset
several related assets
a complete website
an affiliate content pack
a product launch
a campaign
a social media series
an email or newsletter programme
a video content series
a documentation package
a content refresh programme
a repurposing programme

A content project should eventually identify:

project name
project objective
originating request
business or workstream
target audience
audience stage
project owner
requesting Brain or human
required assets
asset relationships
channels
destinations
dependencies
source intelligence
evidence requirements
compliance requirements
approval requirements
production sequence
current stage
blocked conditions
next action
completed assets
publication state
performance state
lifecycle recommendations

The Content Project Layer prevents multiple related assets from being treated as disconnected records.

It allows one approved objective to produce a coordinated set of content outputs.

5. Asset Planning Layer

The Asset Planning Layer determines what content assets are required.

Asset planning may define:

asset type
asset purpose
audience
awareness stage
channel
destination
format
length
message
angle
call to action
evidence requirement
source requirements
relationship to other assets
production order
approval point
publication requirement

Asset planning should support:

website pages
articles
affiliate pages
landing pages
bridge pages
advertorials
comparison pages
social posts
social series
video scripts
podcast scripts
webinar scripts
ad copy
ad scripts
newsletters
email sequences
manuals
guides
reports
lead magnets
ebooks
training content
knowledge-base content
checklists
workbooks
standard operating procedures
content packs

The Asset Planning Layer must prevent content production from starting without sufficient clarity.

It must also avoid unnecessary planning overhead for simple and fully defined requests.

6. Brief And Outline Layer

The Brief And Outline Layer converts the approved asset plan into production guidance.

A content brief may include:

content objective
target audience
audience state
intent
content type
destination
required message
supporting evidence
source material
structure
headings
questions to answer
objections to address
trust requirements
conversion role
call to action
voice and tone
compliance limits
internal-linking requirements
metadata requirements
approval requirements
completion criteria

A brief may support:

human writers
Martyn
M
future Content Brain tools
future AI Employees
future controlled generators

Not every request requires a large formal brief.

The architecture must support proportional briefing.

Simple content may proceed from a smaller instruction set where the objective and requirements are already clear.

7. Content Production Layer

The Content Production Layer creates the actual content.

This is a central architectural layer.

It must not be reduced to recommendations, structural notes or brief generation.

The Content Production Layer may create:

Website Content

home pages
about pages
service pages
product pages
category pages
collection pages
landing pages
lead-generation pages
bridge pages
pre-sell pages
advertorials
affiliate review pages
comparison pages
local pages
FAQ pages
authority pages
pillar pages
supporting pages
onboarding pages
knowledge-base pages
calls to action
metadata
internal-linking copy

Article Content

educational articles
informational articles
commercial articles
affiliate reviews
comparisons
buyer guides
how-to articles
list articles
case studies
authority articles
thought-leadership articles
research-led articles
search-led articles
evergreen articles
refreshed articles
supporting cluster articles

Social Content

Facebook posts
Instagram captions
Instagram carousel copy
LinkedIn posts
X posts
X threads
YouTube community posts
TikTok concepts
short-form social scripts
social hooks
engagement posts
comment-response material
social series
platform-specific content plans

Scripted Content

YouTube scripts
YouTube Shorts scripts
TikTok scripts
Instagram Reel scripts
webinar scripts
VSL scripts
sales video scripts
explainer scripts
educational video scripts
product demonstration scripts
podcast scripts
podcast outlines
voiceover scripts
presentation scripts
training scripts
ad scripts
scene guidance
shot guidance
on-screen text

Advertising Content

headlines
descriptions
primary ad copy
hooks
opening lines
search ad copy
display ad copy
native ad copy
YouTube ad scripts
Meta ad copy
TikTok ad scripts
advertorial copy
pre-sell copy
creative briefs
landing-page message-match copy
call-to-action variations

Email And Newsletter Content

newsletters
newsletter series
promotional emails
educational emails
welcome sequences
nurture sequences
launch sequences
affiliate promotional sequences
re-engagement sequences
post-purchase emails
abandoned-cart emails
subject lines
preview text
email calls to action
email variants

Manuals And Long-Form Assets

instruction manuals
user guides
implementation guides
playbooks
standard operating procedures
reports
white papers
ebooks
workbooks
checklists
lead magnets
onboarding packs
client documents
course lessons
training materials
internal operating documents
knowledge-base content

Content Packs

The Production Layer may create coordinated content packs containing multiple assets.

A content pack may include:

a main website page
supporting articles
newsletter content
email sequences
social posts
short-form scripts
ad scripts
lead magnets
checklists
internal-linking recommendations
publishing notes

The Production Layer must be capable of creating complete, usable drafts and final review versions.

8. Editing And Quality Control Layer

The Editing And Quality Control Layer improves content after initial creation.

It may perform:

structural editing
developmental editing
factual review
evidence alignment
clarity editing
readability improvement
repetition reduction
voice and tone alignment
message consistency review
audience alignment
intent alignment
channel adaptation
heading improvement
flow improvement
call-to-action improvement
trust review
compliance-risk review
duplication review
internal-linking review
formatting preparation
completeness checking

Content must not be treated as ready merely because a first draft exists.

Quality control should evaluate:

objective fit
audience fit
intent fit
channel fit
source support
factual accuracy
evidence quality
information gain
clarity
structure
readability
voice
persuasion strength
trust stability
compliance safety
completeness
next-action clarity
relationship to other assets
publishing readiness

The Editing And Quality Control Layer may return content to production for correction.

9. Specialist Review And Approval Layer

The Specialist Review And Approval Layer manages required review before publication or delivery.

Review may include:

human content review
compliance review
factual review
technical review
legal review
offer review
product review
strategy review
campaign review
brand review
stakeholder approval
client approval

The review requirement depends on:

content type
business risk
claim risk
destination
audience
subject matter
campaign role
legal exposure
financial implications
publication authority

Review outcomes may include:

approved
approved with changes
changes required
specialist review required
evidence required
blocked
rejected
held for later

Humans retain final approval authority under the current manual operating model.

10. Publishing Preparation Layer

The Publishing Preparation Layer converts approved content into a destination-ready package.

It may include:

final title
heading structure
metadata
URL guidance
call-to-action placement
internal-link placement
external-link requirements
image requirements
creative requirements
alt-text guidance
formatting guidance
publication notes
platform-specific formatting
channel-specific versions
disclosure requirements
compliance notes
publishing checklist
asset naming
destination confirmation

Publishing preparation does not automatically mean publication.

It means the content is prepared for the authorised publishing or delivery process.

11. Delivery And Publication Layer

The Delivery And Publication Layer handles the controlled movement of approved content to its destination.

Current operating status:

publishing remains human controlled
delivery remains human controlled
no autonomous publishing
no autonomous cross-site posting
no autonomous social posting
no autonomous newsletter sending
no autonomous ad deployment
no autonomous document delivery

Future authorised integrations may support:

WordPress publishing
social platform scheduling
email platform delivery
newsletter systems
documentation systems
client delivery portals
advertising platform asset delivery
content management systems
ecommerce platforms

Any future publishing integration must include:

permission controls
approval gates
destination checks
version checks
rollback or correction procedures
audit visibility
failure handling
human override

12. Measurement And Feedback Layer

The Measurement And Feedback Layer receives post-publication or post-delivery signals.

Signals may come from:

Data Brain
Search Intelligence
Ads Brain
Experimentation Brain
Affiliate Brain
Customer Brain
Ecommerce Brain
platform analytics
email analytics
website analytics
human review
customer feedback
campaign outcomes
publication performance

Signals may include:

traffic
impressions
rankings
engagement
click-through rate
conversion support
email opens
email clicks
social engagement
video retention
lead generation
sales contribution
audience response
internal-link performance
content decay
content gaps
compliance issues
factual corrections
stakeholder feedback

The Measurement And Feedback Layer must distinguish between:

useful signal
weak signal
temporary fluctuation
confirmed pattern
channel-specific behaviour
asset-specific behaviour

Content Brain uses approved signals to guide future work.

It does not independently redefine statistical confidence or experimentation rules.

13. Content Lifecycle Layer

The Content Lifecycle Layer governs what happens after content is published or delivered.

Lifecycle actions may include:

monitor
refresh
improve
expand
repurpose
update evidence
update claims
update metadata
strengthen internal linking
consolidate overlapping content
reformat
redistribute
reissue
correct
retire
archive

A lifecycle decision should consider:

current relevance
performance
strategic value
accuracy
evidence age
search visibility
audience usefulness
duplication
compliance risk
business value
maintenance cost
relationship to other assets

Content should not remain active indefinitely merely because it was once published.

The Architecture must support long-term content maintenance.

14. Site Intelligence Support Layer

The Site Intelligence Support Layer reviews websites and existing content estates.

Its role may include:

identifying missing pages
identifying weak content
identifying thin content
identifying duplicated content
identifying outdated content
identifying refresh needs
identifying internal-linking opportunities
identifying content gaps
identifying publishing-readiness issues
identifying compliance concerns
identifying site structure issues
identifying opportunities for content packs
identifying content that should not be recreated

Site Intelligence must produce content action decisions.

Possible decisions include:

create
refresh
merge
repurpose
relink
correct
retire
no action
specialist review
content project required

Site Intelligence is a supporting layer.

It must not become the main Content Brain operating model.

The current Site Intelligence Records screen is a temporary diagnostic and records proof.

It is not the complete Content Brain interface.

15. Content Knowledge And Reuse Layer

The Content Knowledge And Reuse Layer preserves useful content intelligence and reusable production assets.

It may eventually include:

approved templates
content structures
successful hooks
message patterns
article structures
script structures
email frameworks
newsletter formats
social post formats
content pack patterns
voice guidance
style guidance
audience language
approved claims
prohibited claims
internal-linking patterns
reusable research references
reusable evidence
high-performing content examples
failed content patterns
editing rules
publishing standards

This layer must support reuse without encouraging generic duplication.

Reusable structures must still be adapted to:

objective
audience
channel
offer
business
evidence
destination
current context

16. Data And Records Layer

The Data And Records Layer stores repeatable operational information.

Supabase is the expected structured data environment for repeatable Content Brain records.

Future records may include:

content requests
content projects
asset records
content brief records
source references
evidence references
content versions
approval records
production status
publishing status
destination records
performance signals
refresh recommendations
repurposing recommendations
internal-link actions
compliance flags
archive state
migration state

The final data model must follow the validated operating workflow.

Temporary Site Intelligence test fields must not define the complete Content Brain schema.

Structured records should not be converted into large numbers of WordPress pages.

17. Interface And Operational Layer

The Interface And Operational Layer provides the human-controlled operating environment.

The Content Brain site is the operational implementation environment.

Future interfaces may include:

Content Brain home
request intake
active content projects
asset planning
briefs
production workspace
content editor
review queue
approval screen
publishing preparation
content pack view
content lifecycle view
refresh view
repurposing view
Site Intelligence
source and evidence view
operational signals
completed content assets
archive view

The main interface must reflect Content Brain’s full production role.

It must not be centred only on:

Site Intelligence tests
research-style records
compliance flags
migration state
diagnostic signals

Those may remain as supporting functions.

18. Governance And Integrity Layer

The Governance And Integrity Layer ensures Content Brain remains within authority.

Governance controls may include:

MCR source-truth checks
Canon alignment
Brain authority checks
evidence requirements
compliance requirements
human approval
version control
change logging
source traceability
publication authority
audit visibility
archive controls
drift detection
safe editing
no uncontrolled deletion
no uncontrolled automation

The Governance And Integrity Layer must prevent:

unsupported claims
invented evidence
uncontrolled publishing
duplicate content creation
research authority drift
Site Intelligence scope drift
page bloat
temporary test screens defining permanent architecture
records being treated as Canon
Content Brain site pages being treated as MCR source truth
premature automation
premature worker activation
premature AI Employee activation
premature Brain Room routing
premature M handoff

SIT Brain may monitor architectural integrity and authority boundaries.

19. Future Automation And Worker Layer

The Architecture allows future automation but does not activate it.

Future capabilities may include:

automated request intake
approved routing
structured project creation
controlled brief generation
controlled drafting
controlled editing
compliance pre-checks
publishing-readiness checks
version comparison
refresh recommendations
repurposing recommendations
content queues
worker processes
AI Employees
publishing integrations
performance feedback
automated status updates
cross-Brain requests
Brain Room routing
M handoff

Future automation must be introduced only after:

the manual workflow is proven
authority is clear
the data model is stable
failure handling is defined
permissions are defined
approval gates are active
audit visibility exists
rollback or correction is possible
human override remains available
SIT integrity checks are satisfied

The presence of a future capability in this Architecture does not authorise its current implementation.

Cross-Brain Architecture

Content Brain operates as a production and lifecycle Brain that consumes approved inputs from other Brains.

HeadOffice

HeadOffice provides:

authority
strategic direction
governance
conflict resolution
future autonomy approval

Content Brain reports material architectural drift to HeadOffice and Martyn.

Strategy Brain

Strategy Brain provides:

positioning
strategic narrative
market direction
launch priorities
growth priorities

Content Brain converts approved strategy into content assets.

Research Brain

Research Brain provides:

validated research
emerging insights
market intelligence
competitor intelligence
customer intelligence
source material
evidence

Content Brain uses approved research.

It does not replace Research Brain’s deep research function.

Customer Brain

Customer Brain provides:

audience states
motivations
concerns
language
journey context
segmentation
retention intelligence

Content Brain uses this information to create audience-relevant content.

Affiliate Brain

Affiliate Brain provides:

offer requirements
funnel role
campaign context
testing needs
affiliate objectives

Content Brain creates:

review pages
comparison pages
bridge pages
advertorials
supporting articles
emails
social content
scripts
affiliate content packs

Ads Brain

Ads Brain governs:

campaign strategy
platform selection
testing structure
optimisation
scaling
advertising performance

Content Brain creates:

ad copy
headlines
scripts
advertorials
pre-sell content
message-match content
creative briefs
content variations

Creative Brain

Creative Brain provides:

creative concepts
emotional angles
narratives
stories
message ideas
creative direction

Content Brain converts approved creative direction into complete assets.

Conversion Brain

Conversion Brain provides:

friction analysis
trust requirements
persuasion principles
page structure guidance
behavioural guidance
conversion-support guidance

Content Brain applies these requirements during production and editing.

Compliance Brain

Compliance Brain provides:

claim boundaries
policy interpretation
regulatory requirements
escalation decisions
prohibited content rules

Content Brain must comply with these requirements.

Experimentation Brain

Experimentation Brain provides:

testing rules
variant requirements
experiment structure
interpretation standards

Content Brain creates controlled variants for approved tests.

Data Brain

Data Brain provides:

measurement integrity
performance signals
attribution context
reporting inputs

Content Brain uses approved signals for lifecycle decisions.

Search Intelligence

Search Intelligence provides:

demand
intent
query opportunity
search visibility
SERP context
performance signals

Content Brain creates and improves search-focused content from those inputs.

Ecommerce Brain

Ecommerce Brain provides:

product context
merchandising needs
customer journey requirements
retention needs
ecommerce lifecycle requirements

Content Brain creates product, category, education, email and support content.

Product Brain

Product Brain provides:

product capabilities
use cases
user needs
positioning context
documentation requirements

Content Brain creates product communication, onboarding, training and documentation assets.

Finance Brain

Finance Brain provides:

financial constraints
economic claim boundaries
budget context
commercial viability inputs

Content Brain must not produce unrealistic financial claims.

Operations Brain

Operations Brain may support:

workload coordination
delivery sequencing
handoffs
operational continuity
production capacity

Content Brain retains authority over content-specific quality and production requirements.

SIT Brain

SIT Brain monitors:

system integrity
authority boundaries
workflow compliance
drift
controlled change

Content Brain must remain within approved operating status.

Current Operating Architecture

The current Content Brain operating position is:

MCR remains the source of truth
the Content Brain site remains the operational working environment
Supabase remains the structured records layer
manual workflow remains human controlled
Site Intelligence has been manually tested
Site Intelligence Tests 1 to 5 exist as active structured records
the records interface has proven add, view, edit and archive behaviour
the records interface is not the full Content Brain product
the full production interface has not started
content generation has not started
automated content creation has not started
publishing automation has not started
workers have not started
queues have not started
Brain Room routing has not started
AI Employee work has not started
M handoff has not started

The next build decisions must be based on the full production architecture defined in this page.

Operating Layer Boundaries

MCR

MCR contains:

Canon
architecture
governance
authority
master frameworks
master templates
master specifications
approved operating rules

Content Brain Site

The Content Brain site contains:

operational working pages
manual workflows
plugin screens
implementation pages
working copies
approved operating tools

A Content Brain site-only page is operational only unless deliberately promoted or copied into MCR.

Supabase

Supabase contains:

repeatable operational records
structured status
source relationships
evidence relationships
approval state
asset state
publishing state
lifecycle state
archive state

Supabase does not replace Canon or architecture.

WordPress Pages

WordPress pages are appropriate for:

Canon
frameworks
protocols
templates
specifications
operating pages
short summary logs
approved working copies

Repeatable records should not become individual WordPress pages where structured data is more appropriate.

Architectural Drift Protection

The Architecture must prevent Content Brain from being reduced to:

a research system
a Site Intelligence system
a brief generator
a records table
a compliance register
a page library
a message hierarchy framework
a content recommendation engine
a publishing checklist

These may all exist as parts of Content Brain.

None of them represents the complete Content Brain architecture.

The Architecture must preserve the full path from request to complete content and lifecycle management.

Architectural Success Standard

The Content Brain Architecture is successful when it can support a request such as:

Create a new business website.

And produce:

site structure
page plan
homepage
service pages
about page
FAQs
lead-generation content
supporting articles
email follow-up
social launch content
publishing-ready assets

It must also support a request such as:

Launch this affiliate offer.

And produce:

review page
comparison page
bridge page
advertorial
supporting articles
ad scripts
social posts
newsletter
email sequence
content pack
publishing package

It must also support a request such as:

Turn this source asset into a campaign.

And produce:

article
newsletter
email sequence
social posts
carousel copy
video script
short-form scripts
ad copy
lead magnet
internal-linking actions

It must also support a request such as:

Improve this existing website.

And determine:

what should be created
what should be refreshed
what should be merged
what should be repurposed
what should be linked
what should be retired
what should remain unchanged

Architectural Intent

Content Brain must become the governed production system through which MWMS plans, creates, reviews, prepares, delivers and improves content across every major format and channel.

The Architecture must combine:

intelligence
planning
production
editing
review
publishing support
measurement
lifecycle management

The Architecture must remain capable of supporting:

affiliate projects
PPL projects
AIBS projects
ecommerce
product businesses
client work
websites
social channels
advertising
newsletters
video
documentation
training
future MWMS business models

The Architecture must support both present manual operation and future controlled automation.

Future tools, interfaces, schemas, workers and AI Employees may evolve beneath this Architecture.

They must not narrow or replace the full Content Brain mandate.

Change Log

v1.1 — 2026-06-15

Replaced the previous structural messaging architecture with the full Content Brain production and lifecycle architecture.

Added:

Request And Intake Layer
Qualification And Action Decision Layer
Intelligence Assembly Layer
Content Project Layer
Asset Planning Layer
Brief And Outline Layer
Content Production Layer
Editing And Quality Control Layer
Specialist Review And Approval Layer
Publishing Preparation Layer
Delivery And Publication Layer
Measurement And Feedback Layer
Content Lifecycle Layer
Site Intelligence Support Layer
Content Knowledge And Reuse Layer
Data And Records Layer
Interface And Operational Layer
Governance And Integrity Layer
Future Automation And Worker Layer

Expanded Content Brain Architecture to support:

website production
article production
social media content
script creation
advertising content
newsletters
email sequences
manuals
guides
documentation
training content
content packs
publishing preparation
measurement
refresh
repurposing
retirement

Clarified that Site Intelligence and its current records interface are supporting capabilities and technical proofs, not the full Content Brain architecture.

v1.0 — 2026-03-29

Initial creation of Content Brain Architecture as a structural intelligence and messaging framework connected to research, persuasion, lifecycle alignment and measurable outcomes.