Content Brain Employee Registry

Brain Name: Content Brain
Document Type: Legacy Registry
Status: Legacy Role Reference
Version: v1.1
Authority: HeadOffice
Applies To: Historical Content Brain employee-role logic, Content Brain function definitions, future AI Employee planning, future Content Brain role mapping, future workflow-to-employee assignment, and legacy Content Brain reference material
Parent: Content Brain
Last Reviewed: 2026-05-24

Legacy Status Notice

This page is an early Content Brain employee and role registry from the April 2026 Content Brain structure.

It has not been retired.

It should be kept temporarily as a legacy role reference because it contains useful Content Brain function definitions, including:

strategy roles

research roles

production roles

optimisation roles

signal roles

governance roles

cross-brain interaction responsibilities

role integrity rules

registry maintenance rules

However, this page should not be treated as the current final Content Brain employee structure.

The active first operational layer on mwmscontentbrain.site should be used before this registry for current workflow decisions.

Recommended future action:

Update later after the operational Content Brain workflow on mwmscontentbrain.site is proven and after future Content Brain AI Employee needs become clearer.

This page may later help define actual Content Brain AI Employees, role-routing logic, task ownership, workflow handoff responsibilities, and future employee registry entries.

MCR remains the source of truth.

Purpose

The Content Brain Employee Registry defines the structural roles operating inside Content Brain.

It clarifies which functions exist inside Content Brain and what responsibilities each function holds.

The registry ensures:

role clarity

responsibility boundaries

consistent execution structure

alignment with MWMS Brain architecture

transparency of content production authority

stable interaction with other Brains

The registry does not define performance outcomes.

The registry defines structural responsibility.

This page is now retained as a legacy role reference only.

It should not be treated as the final operational AI Employee structure for Content Brain.

Current Active Operational Pages

The active first operational layer on mwmscontentbrain.site 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 should be used before this registry for current operator workflow decisions.

Core Principle

Brains operate through defined roles.

Roles ensure clarity of responsibility.

Clarity improves consistency of output.

Consistency improves system learning.

However, roles should not be turned into AI Employees too early.

A role becomes a true AI Employee candidate only when repeated workflow responsibility is proven through manual use.

Content Brain Mission

Content Brain exists to produce structured content assets that support:

audience understanding

traffic generation

authority development

behavioural influence

signal generation for other Brains

affiliate content support

SEO content support

internal linking support

repurposing support

refresh support

publishing readiness

Content is not created randomly.

Content is produced to support system learning, reader clarity, and revenue outcomes.

The current Content Brain phase is manual-first.

No plugin, UI, queue, dashboard, generator, Supabase task route, Brain Room routing, or automation should be created from this registry yet.

Content Brain Functional Structure

Content Strategy Role

Responsible for defining:

content themes

topic clusters

authority positioning

narrative direction

alignment with MWMS strategic intent

content purpose

content priority logic

content opportunity logic

The Content Strategy Role helps ensure Content Brain does not create content randomly.

It supports structured decisions about what content should exist and why.

This role does not override HeadOffice, Research Brain, Search Intelligence Brain, Affiliate Brain, Finance Brain, or Experimentation Brain.

Content Research Role

Responsible for:

gathering supporting information

identifying knowledge gaps

identifying audience questions

identifying problem language patterns

supporting Research Brain outputs

collecting content planning inputs

noting content evidence gaps

identifying reader intent gaps

The Content Research Role helps Content Brain work from evidence, signals, and audience needs.

This role does not replace Research Brain.

Research Brain owns evidence quality and research verdicts.

Content Production Role

Responsible for:

creating structured content assets

maintaining clarity of communication

ensuring document consistency

ensuring content aligns with defined frameworks

preparing drafts

preparing outlines

preparing content sections

supporting article, email, social, YouTube, VEO3, affiliate, SEO, and support content structures

The Content Production Role creates content from approved briefs and clear workflow instructions.

It must not introduce unsupported claims, unapproved offers, unapproved guarantees, or compliance-sensitive language without review.

Content Optimisation Role

Responsible for:

improving performance of published content

identifying content improvement opportunities

refining structure for clarity and engagement

supporting refresh decisions

supporting internal linking improvement

supporting repurposing opportunities

supporting SEO improvement notes

supporting publishing readiness corrections

The Content Optimisation Role helps improve existing content.

It should work through Content Brain Refresh, Content Brain Publishing Readiness, Content Brain Internal Linking, and Content Brain SEO Content Briefs where relevant.

This role does not own Data Brain measurement interpretation.

Content Signal Role

Responsible for identifying:

audience response signals

engagement patterns

behavioural indicators

content effectiveness signals

topic traction signals

content gap signals

internal linking signals

refresh signals

repurposing signals

affiliate support signals

These signals may support:

Research Brain

Affiliate Brain

Search Intelligence Brain

Experimentation Brain

Ads Brain

Conversion Brain

Data Brain

HeadOffice

The Content Signal Role may observe signals, but Data Brain owns data reliability and measurement interpretation.

Content Brain must not over-interpret weak signals.

Content Governance Role

Responsible for:

maintaining content standards

ensuring structural consistency

ensuring alignment with MWMS document standards

preventing structural drift

protecting naming discipline

protecting parent-page discipline

protecting source-of-truth discipline

protecting no-build boundaries

protecting approval boundaries

The Content Governance Role helps keep Content Brain clean and usable.

It should prevent Content Brain from becoming cluttered, duplicated, unclear, or disconnected from MCR.

Possible Future AI Employee Candidates

This registry may later inform actual AI Employee planning.

Possible future Content Brain AI Employees may 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 Signal Feedback Employee

Content Governance Employee

Do not create these AI Employees yet.

These are candidate roles only.

Manual workflow use must prove which employees are genuinely needed.

Cross-Brain Interaction Responsibilities

Research Brain

Content Brain uses Research Brain insight to:

understand audience problems

identify information gaps

refine topic selection

support content evidence needs

identify voice-of-customer language

confirm research basis for content

Research Brain owns research verdicts and evidence quality.

Content Brain may return research gaps found during content planning.

Search Intelligence Brain

Content Brain uses Search Intelligence Brain insight to:

understand search demand

interpret SERP patterns

align SEO briefs with intent

identify content gaps

support topic cluster planning

support refresh decisions

support internal linking opportunities

Search Intelligence Brain owns search validation, SERP interpretation, and query demand logic.

Affiliate Brain

Content Brain produces assets supporting:

offer education

pre-sell narrative structure

audience warming content

affiliate product content packs

affiliate funnel support

FAQ content

objection-handling content

trust content

YouTube and VEO3 support

Affiliate Brain owns offer logic and affiliate opportunity decisions.

Content Brain does not approve offers.

Ads Brain

Content Brain may support Ads Brain through:

YouTube description support

landing page support content

message match support

VEO3 pre-video support

content support for ad-to-page continuity

trust and FAQ support assets

Ads Brain owns campaign logic, ad structure, and paid performance decisions.

Experimentation Brain

Content Brain provides structured content variations for testing:

messaging variants

narrative positioning

content framing

angle support

brief variants

pre-sell variants

Experimentation Brain owns test design, test validity, and experiment verdicts.

Content Brain does not declare winners.

Conversion Brain

Content Brain may support Conversion Brain through:

objection-handling content

trust-building content

FAQ support

message clarity

decision support content

reader-fit guidance

CTA support

Conversion Brain owns conversion logic.

Finance Brain

Content Brain supports financial outcomes through:

traffic acquisition support

conversion support

authority development

content efficiency

reuse of approved assets

better refresh discipline

less wasted content production

Finance Brain owns budget, capital, and resource decisions.

Content Brain must not approve resource expansion by itself.

Data Brain

Content Brain may observe:

engagement signals

internal link signals

refresh signals

affiliate click signals

VSL click signals

repurposing signals

content quality signals

Data Brain owns measurement reliability, dashboard standards, tracking quality, and signal interpretation.

Compliance Brain

Content Brain may flag:

claim risk

health claim risk

income claim risk

legal claim risk

product performance claim risk

affiliate claim risk

urgency or scarcity risk

testimonial risk

Compliance Brain owns compliance interpretation.

Content Brain must not approve sensitive claims alone.

HeadOffice

HeadOffice monitors:

content production flow

structural alignment

cross-brain support effectiveness

content bottlenecks

content risk

workflow drift

employee role clarity

future AI Employee readiness

HeadOffice owns governance oversight and cross-brain priority.

Role Integrity Rule

Roles define responsibility.

Roles do not define hierarchy of importance.

All roles support system learning.

No role should overstep the authority of another Brain.

No role should become an AI Employee until repeated operational need is proven.

No role should create plugin, UI, queue, dashboard, generator, automation, Supabase work, or Brain Room routing by itself.

Registry Maintenance Rule

New roles may be added only when:

structural gaps are identified

repeated responsibilities emerge

cross-brain interaction requires clarification

manual workflow shows repeated handoff friction

a future AI Employee need becomes clear

HeadOffice approves the role expansion

Do not add roles just because they sound useful.

Do not create role bloat.

Do not convert every function into an AI Employee.

Relationship To Current Operational Layer

This page is not the active workflow page.

Use the active operational pages first:

Use Content Brain Workflow to decide how work moves.

Use Content Brain Content Briefs to structure content planning.

Use Content Brain SEO Content Briefs for search-focused briefs.

Use Content Brain Affiliate Content Packs for affiliate product content support.

Use Content Brain Affiliate Funnel Support for funnel-stage support.

Use Content Brain Internal Linking for link planning.

Use Content Brain Repurposing for approved content reuse.

Use Content Brain Refresh for existing content improvement.

Use Content Brain Publishing Readiness before use, handoff, or publishing.

This registry may later help map repeated workflow responsibilities into future AI Employee candidates.

Future Use

This page may later support:

Content Brain AI Employee Registry

Content Brain Employee Router

Content Brain role-to-task mapping

Content Brain workflow ownership model

Content Production Queue assignment logic

Content Refresh Queue assignment logic

Repurposing Queue assignment logic

Content Operations Dashboard role sections

Content Signal Feedback Dashboard roles

Brain Room task ownership

HeadOffice reporting on Content Brain roles

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

AI Employee implementation

This page is a legacy role reference only.

It does not authorize build work.

Drift Protection

The system must prevent:

this registry being treated as the final Content Brain AI Employee structure

roles being converted into AI Employees too early

role bloat

role confusion

Content Brain roles overriding other Brain authority

Content Brain roles approving offers

Content Brain roles approving claims

Content Brain roles approving campaigns

Content Brain roles approving budgets

Content Brain roles declaring experiment winners

Content Brain roles interpreting data reliability without Data Brain

plugin or UI work starting before manual workflow proves need

Supabase work starting from this registry

Brain Room routing starting from this registry

automation starting from this registry

M’s active build areas being touched without assignment

Recommended Future Action

Later, after the first operational layer has been used manually, review whether these roles should be converted into:

actual Content Brain AI Employees

workflow ownership fields

task routing categories

queue ownership logic

dashboard role sections

Brain Room task assignment logic

HeadOffice reporting groups

Until then, keep this page as a legacy role reference.

Do not delete today.

Do not treat it as the final employee structure.

Architectural Intent

Content Brain Employee Registry exists as an early role map for Content Brain.

It helped define the functional responsibilities needed inside Content Brain before the live operational layer was fully built.

The current architecture has moved toward a cleaner manual-first operational page layer.

This registry should be retained only while its useful role definitions may still inform future AI Employee design.

The long-term intent is:

MCR defines Content Brain.

mwmscontentbrain.site operates Content Brain.

Manual workflow proves employee need.

Future AI Employees are created only after repeated workflow responsibility becomes clear.

Final Rule

Keep this page as a legacy role reference for now.

Do not delete it today.

Do not use it as the final Content Brain AI Employee structure.

Do not build plugin, UI, queue, dashboard, generator, automation, Supabase routes, Brain Room routing, or AI Employees from this page yet.

Useful role logic may be updated later after manual Content Brain operations prove which AI Employees are genuinely needed.

Change Log

Version: v1.1
Date: 2026-05-24
Author: HeadOffice
Change: Updated Content Brain Employee Registry from active registry status to legacy role reference status. Clarified that the page is not the final Content Brain AI Employee structure, preserved useful historical role definitions, added relationship to the active first operational layer, added possible future AI Employee candidates, expanded cross-brain responsibility boundaries, added no build rule, drift protection, and recommendation to update later only after manual workflow proves actual Content Brain AI Employee needs.

Version: v1.0
Date: 2026-04-09
Author: HeadOffice
Change: Initial creation of Content Brain Employee Registry defining Content Strategy Role, Content Research Role, Content Production Role, Content Optimisation Role, Content Signal Role, Content Governance Role, cross-brain interaction responsibilities, role integrity rule, and registry maintenance rule.

Change Impact Declaration

Pages Created:
None

Pages Updated:
Content Brain Employee Registry

Pages Renamed:
None

Pages Deprecated:
None

Registries Requiring Update:
No immediate registry update required unless future Content Brain AI Employees are formally created

Canon Version Update Required:
No

Change Log Entry Required:
No

END CONTENT BRAIN EMPLOYEE REGISTRY v1.1