Document Type: Operating Model
Version: v1.2
Parent Page: Content Brain
Status: Active
Migration Classification: Copy To Content Brain Later
Plugin Or UI Candidate: No Direct UI
Notes: Defines how Content Brain is operated through request intake, qualification, existing-content checking, action decisions, project creation, asset planning, intelligence assembly, briefing, complete content production, editing, specialist review, human approval, publishing preparation, human-controlled delivery, measurement and lifecycle management. Supports websites, articles, social content, scripts, advertisements, newsletters, emails, manuals, documentation and multi-asset content packs.
Content Brain Operating Model
Purpose
The Content Brain Operating Model defines how Content Brain is operated in practice.
It converts the authority defined in the Content Brain Canon and the system structure defined in the Content Brain Architecture into a repeatable human-controlled working process.
The Operating Model governs how MWMS:
- receives content requests
- determines whether content work is required
- defines content projects
- plans content assets
- assembles approved intelligence
- creates briefs where needed
- produces complete content
- edits and improves content
- manages specialist review
- obtains human approval
- prepares content for publication or delivery
- records publication and delivery state
- receives performance and quality signals
- refreshes, repurposes, consolidates, corrects, retires or archives content
Content Brain must remain a production system.
It must not be reduced to:
- a research database
- a Site Intelligence register
- a content brief system
- a content recommendation system
- a page library
- a compliance register
- a records screen
- a workflow diagram
- a publishing checklist
Those functions may support Content Brain.
They do not represent the complete operating model.
Operating Objective
The operating objective is to move an approved content need from request to usable content without losing:
- objective clarity
- audience relevance
- source integrity
- evidence quality
- channel suitability
- strategic alignment
- compliance safety
- human control
- lifecycle visibility
The primary operating flow is:
Request Or Opportunity
→ Qualification
→ Action Decision
→ Content Project Definition
→ Source And Intelligence Assembly
→ Asset Planning
→ Briefing Where Required
→ Content Production
→ Editing And Quality Review
→ Specialist Review Where Required
→ Human Approval
→ Publishing Preparation
→ Delivery Or Publication
→ Measurement
→ Lifecycle Decision
The workflow may produce:
- one content asset
- multiple related assets
- a website content system
- an affiliate content pack
- a campaign content pack
- an article programme
- a social media series
- a script package
- an email or newsletter sequence
- a manual or guide
- a refresh programme
- a repurposing programme
Current Operating Status
The current Content Brain operating model remains manual and human controlled.
Current status:
- Martyn controls the workstream
- MCR is the source of truth
- the Content Brain site is the operational working environment
- Supabase stores repeatable structured records where appropriate
- humans approve final content
- humans approve publication
- no autonomous publishing
- no autonomous content worker
- no autonomous queue execution
- no autonomous Brain Room routing
- no automatic M handoff
- no AI Employee authority activated
- no full Content Brain production interface completed
- no full content generator completed
- no unrestricted content generation
- no automatic cross-Brain task wiring
The current Site Intelligence Records screen remains a technical and operational proof for structured records.
It is not the main Content Brain operating interface.
Core Operating Principles
Production Is A Core Function
Content Brain must create complete content assets.
Planning, analysis, records and briefs must support production.
They must not replace production.
MCR Is Checked First
Before creating or changing a governing Content Brain page, MCR must be checked for:
- exact title match
- close title match
- a source page covering the same purpose
- an existing master framework
- an existing master template
- an existing master specification
- a governance rule that already controls the work
The Content Brain site must not be treated as MCR source truth.
Existing Content Is Checked Before New Content Is Created
Before producing new content, Content Brain must determine whether an existing asset already satisfies the need.
Possible decisions are:
- create
- refresh
- expand
- correct
- merge
- repurpose
- reformat
- relink
- retire
- archive
- no action
- specialist review
- another Brain must act first
The existence of a content opportunity does not automatically justify new content.
Content Must Have A Defined Purpose
Every content asset must have a clear reason to exist.
The reason may include:
- supporting a business objective
- answering an audience need
- supporting a campaign
- supporting an offer
- supporting a website
- supporting a customer journey
- building authority
- creating demand
- supporting search visibility
- supporting conversion
- supporting retention
- documenting a process
- training a person or team
- improving an existing asset
- repurposing approved source content
Source Integrity Must Be Preserved
Content Brain must not invent:
- facts
- evidence
- sources
- statistics
- product details
- customer experiences
- testimonials
- offer conditions
- compliance interpretations
- research conclusions
Where information is missing, Content Brain must identify the gap.
It must not hide the gap by producing unsupported content.
Human Control Remains Active
Humans retain control over:
- final approval
- publication
- delivery
- high-risk claims
- ambiguous evidence
- major strategic interpretation
- legal or compliance escalation
- cross-Brain conflict
- activation of future automation
Operating Effort Must Be Proportional
Simple work must not be forced through unnecessary complexity.
A short social post may not require a large content brief.
A full website, affiliate content pack, regulated article or multi-channel campaign may require detailed planning, evidence and approvals.
The operating model must apply enough control to protect quality without creating avoidable delay.
Roles In The Current Manual Operating Model
Martyn
Martyn is the current Content Brain workstream owner and final human authority for the manual operating process.
Martyn may:
- initiate requests
- define priorities
- approve objectives
- approve page and system changes
- approve content
- reject content
- request revisions
- approve publication
- stop work
- resolve practical operating questions
- approve later build stages
Content Brain must not wait for M when the work belongs to Martyn’s Content Brain workstream.
M
M may later support implementation, development, migration, publishing or approved operational work.
Current rule:
- no automatic M handoff
- no M dependency for Martyn’s Content Brain planning work
- no interference with M’s Research Brain work
- no task should be sent to M without an approved handoff
Content Brain
Content Brain is responsible for:
- qualifying content work
- planning content projects
- identifying required assets
- creating briefs
- creating content
- editing content
- preparing review-ready assets
- preparing publishing-ready assets
- preserving source relationships
- tracking lifecycle needs
Other Brains
Other Brains provide specialist authority and inputs.
They do not replace Content Brain’s production responsibility.
Daily Operating Start
Each working session should begin from the current save point.
The operator should confirm:
- current task
- current operating status
- current source of truth
- pages or records already available
- work that must not be touched
- the last completed action
- the next required action
- whether any source page must be reviewed before work begins
The session must not restart from assumptions already disproven.
The operator must use the pages, records and screenshots already supplied unless a fresh check is genuinely required.
Step 1: Receive The Request Or Opportunity
Content work begins with a request, need, opportunity, problem or instruction.
The request may come 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
- an existing website
- an existing content asset
- a client requirement
- a customer requirement
- a manual operational instruction
The request should identify as much of the following as is available:
- what is needed
- why it is needed
- who it is for
- where it will be used
- what outcome it should support
- what source material exists
- what constraints apply
- who must approve it
- when it is needed
A request may be incomplete at intake.
It must not move into production until it is sufficiently qualified.
Step 2: Qualify The Request
Content Brain determines whether the request is valid and ready.
Qualification checks include:
- Does this request belong to Content Brain?
- Is the objective clear?
- Is the audience sufficiently clear?
- Is the content destination known?
- Is the content type known?
- Does suitable content already exist?
- Is the requested asset genuinely needed?
- Is required source material available?
- Is deeper research required?
- Is Strategy Brain direction required?
- Is Affiliate Brain, Ads Brain, Product Brain or another Brain required first?
- Are compliance boundaries known?
- Is human approval ownership clear?
- Would the request create duplicate or low-value content?
- Should this work become one asset or a larger content project?
The request must receive a clear operating decision.
Step 3: Make The Action Decision
The action decision determines what Content Brain should do.
Available actions include:
Create
Produce a new content asset because no suitable asset exists.
Refresh
Update an existing asset because it remains useful but is outdated, weak, incomplete or underperforming.
Expand
Add useful depth, examples, evidence, sections or supporting material to an existing asset.
Correct
Repair inaccurate, unclear, misleading, broken or non-compliant content.
Merge
Combine overlapping assets where consolidation produces a stronger result.
Repurpose
Adapt an approved source asset into a new channel or format.
Reformat
Change how content is delivered without changing its core purpose.
Relink
Improve internal linking, calls to action or relationships between assets.
Retire
Remove an asset from active use when it is no longer suitable.
Archive
Preserve an inactive asset or record without treating it as current.
No Action
Do not create or change content because the existing state is sufficient or the proposed work has insufficient value.
Specialist Review
Pause production until a specialist, human or relevant Brain resolves an issue.
Another Brain First
Return or route the work because Strategy Brain, Research Brain, Compliance Brain or another authority must act before production begins.
Step 4: Define The Content Project
A content project is created when the work contains multiple related assets or requires structured coordination.
A content project may support:
- a business website
- a site redesign
- an affiliate offer
- a product launch
- a campaign
- a newsletter programme
- a social media programme
- a video series
- a documentation package
- a manual or guide
- a refresh programme
- a repurposing programme
- a client content package
A content project should define:
- project name
- objective
- business or workstream
- requesting source
- target audience
- audience stage
- required assets
- channels
- destinations
- dependencies
- source requirements
- evidence requirements
- compliance requirements
- approval points
- production order
- current stage
- next action
- blocked conditions
- completion standard
A simple one-asset request does not require a large project structure.
Step 5: Assemble Sources And Intelligence
Content Brain gathers the approved information required for production.
Sources may include:
- business objectives
- strategic positioning
- market direction
- offer information
- product information
- customer research
- customer language
- awareness stage
- lifecycle stage
- search intent
- keyword context
- competitor context
- site intelligence
- existing content
- verified evidence
- research findings
- campaign requirements
- platform requirements
- brand guidance
- voice guidance
- creative direction
- compliance rules
- conversion requirements
- previous performance data
- experiment learnings
- human instructions
Content Brain must distinguish between:
- confirmed fact
- verified evidence
- approved strategy
- validated insight
- emerging signal
- working assumption
- human preference
- content interpretation
Working assumptions must not be presented as confirmed truth.
Where deeper research is required, Research Brain or an approved human research process must supply it.
Step 6: Plan The Required Assets
Content Brain identifies the assets needed to satisfy the objective.
Asset planning should define:
- asset type
- purpose
- audience
- channel
- destination
- format
- length
- message
- angle
- call to action
- source requirements
- evidence requirements
- relationship to other assets
- production order
- approval requirement
- completion standard
Possible asset types include:
Website Assets
- home page
- about page
- service page
- product page
- category page
- collection page
- landing page
- bridge page
- advertorial
- affiliate review
- comparison page
- buyer guide
- FAQ page
- local page
- authority page
- pillar page
- supporting page
- onboarding page
- knowledge-base page
Article Assets
- educational article
- informational article
- commercial article
- affiliate review
- comparison article
- how-to article
- list article
- case study
- authority article
- thought-leadership article
- research-led article
- search-led article
- evergreen article
- refresh article
Social Assets
- Facebook post
- Instagram caption
- Instagram carousel
- LinkedIn post
- X post
- X thread
- YouTube community post
- TikTok concept
- short-form script
- social series
- engagement prompt
- comment-response material
Script Assets
- YouTube script
- YouTube Shorts script
- TikTok script
- Instagram Reel script
- webinar script
- VSL script
- sales video script
- explainer script
- product demonstration script
- podcast script
- voiceover script
- presentation script
- training script
- ad script
Advertising Assets
- headline
- primary copy
- description
- hook
- search ad
- display ad
- native ad
- YouTube ad script
- Meta ad copy
- TikTok ad script
- advertorial
- pre-sell page
- creative brief
- message-match copy
- call-to-action variation
Email And Newsletter Assets
- newsletter
- promotional email
- educational email
- welcome sequence
- nurture sequence
- launch sequence
- affiliate promotional sequence
- re-engagement sequence
- post-purchase email
- abandoned-cart email
- subject line
- preview text
- email variation
Manual And Long-Form Assets
- instruction manual
- user guide
- implementation guide
- standard operating procedure
- training document
- workbook
- checklist
- playbook
- report
- white paper
- ebook
- lead magnet
- onboarding pack
- client document
- course lesson
- knowledge-base content
Step 7: Create A Brief Where Required
A brief converts the approved request and source inputs into production guidance.
A brief may contain:
- objective
- target audience
- audience state
- intent
- content type
- channel
- destination
- required message
- angle
- evidence
- source material
- structure
- headings
- questions to answer
- objections to address
- trust requirements
- conversion role
- call to action
- voice and tone
- compliance constraints
- internal-linking requirements
- metadata requirements
- approval requirements
- completion criteria
A brief is required when the work is complex enough to benefit from structured guidance.
A brief is not mandatory when:
- the task is simple
- the objective is already clear
- the required format is clear
- the source material is complete
- unnecessary briefing would add delay without improving quality
Step 8: Produce The Content
Content Brain creates the actual content asset.
Production may include:
- outline
- draft
- full page copy
- article
- social post
- script
- ad copy
- newsletter
- email sequence
- manual
- guide
- report
- checklist
- playbook
- content pack
- repurposed asset
- refreshed asset
Production must follow:
- the approved objective
- audience requirements
- source material
- evidence boundaries
- channel requirements
- message requirements
- compliance limits
- voice and tone requirements
- completion standard
The output must be usable.
Content Brain must not substitute a list of suggestions when the approved task requires a completed asset.
Step 9: Edit And Improve The Content
The first draft is not automatically the final output.
Editing may include:
- structural editing
- developmental editing
- clarity editing
- factual alignment
- evidence alignment
- voice alignment
- tone alignment
- audience alignment
- intent alignment
- channel adaptation
- repetition reduction
- readability improvement
- heading improvement
- flow improvement
- call-to-action improvement
- trust improvement
- claim-risk correction
- duplication removal
- internal-linking improvement
- formatting preparation
The editing process should check:
- Does the asset fulfil the objective?
- Is it suitable for the audience?
- Is it suitable for the channel?
- Is it accurate?
- Is it supported?
- Is it clear?
- Is it complete?
- Is it useful?
- Is the structure appropriate?
- Is the persuasion level appropriate?
- Is the next action clear?
- Does it fit with related assets?
- Is it ready for review?
Content may return to production for further revision.
Step 10: Complete Specialist Review Where Required
Some assets require specialist review before human approval.
Possible review types include:
- compliance
- legal
- factual
- technical
- medical
- financial
- offer
- product
- strategy
- campaign
- brand
- stakeholder
- client
Specialist review is required when:
- claim risk is high
- legal or regulatory exposure exists
- technical accuracy is important
- the content affects financial decisions
- the content represents a product or offer
- the content may create material reputational risk
- the approving human requires specialist confirmation
Review outcomes include:
- approved
- approved with changes
- changes required
- evidence required
- blocked
- rejected
- held for later
Step 11: Obtain Human Approval
Human approval is required before publication or delivery under the current operating model.
The approver may:
- approve
- request changes
- reject
- hold
- request more evidence
- require specialist review
- change the objective
- change the destination
- stop the project
Content Brain must preserve the difference between:
- draft complete
- review complete
- approved
- publishing-ready
- published or delivered
These states must not be treated as interchangeable.
Step 12: Prepare For Publishing Or Delivery
Approved content is prepared for its destination.
Publishing preparation may include:
- final title
- heading structure
- metadata
- URL guidance
- formatting
- call-to-action placement
- internal links
- external links
- image requirements
- creative requirements
- alt text
- disclosures
- compliance notes
- platform-specific formatting
- asset naming
- destination confirmation
- publishing checklist
- delivery notes
Publishing preparation creates a destination-ready package.
It does not automatically publish or send the content.
Step 13: Publish Or Deliver Through Human Control
Current publication and delivery remain human controlled.
This includes:
- WordPress publishing
- social posting
- social scheduling
- newsletter sending
- email sequence deployment
- ad deployment
- manual delivery
- client delivery
- document distribution
- ecommerce publication
Content Brain may prepare the work.
An authorised human completes or approves the publication or delivery action.
Future integrations must not be activated without approved permissions, gates and failure handling.
Step 14: Record The Outcome
After publication or delivery, the operating record should eventually capture:
- asset
- destination
- publication or delivery date
- version
- approving human
- source project
- related assets
- status
- known follow-up date
- measurement requirements
- refresh requirements
- archive state
The exact record structure may evolve.
The operating requirement is to preserve enough information for future review and lifecycle action.
Step 15: Receive Measurement And Feedback
Content Brain may receive signals from:
- Data Brain
- Search Intelligence
- Ads Brain
- Experimentation Brain
- Affiliate Brain
- Customer Brain
- Ecommerce Brain
- platform analytics
- website analytics
- email analytics
- social analytics
- human review
- customer feedback
- stakeholder feedback
- campaign outcomes
Signals may include:
- traffic
- rankings
- impressions
- engagement
- click-through rate
- conversion support
- email opens
- email clicks
- social response
- video retention
- lead generation
- sales contribution
- content decay
- factual issues
- compliance issues
- internal-link performance
- audience feedback
- stakeholder feedback
A signal must not automatically trigger a change.
Content Brain must distinguish:
- useful evidence
- weak evidence
- temporary fluctuation
- confirmed pattern
- channel-specific behaviour
- asset-specific behaviour
- measurement failure
Step 16: Make The Lifecycle Decision
Content Brain determines what should happen to the asset next.
Possible lifecycle actions include:
- monitor
- refresh
- improve
- expand
- repurpose
- update evidence
- update claims
- strengthen internal linking
- consolidate
- reformat
- redistribute
- reissue
- correct
- retire
- archive
- no action
Lifecycle decisions should consider:
- relevance
- accuracy
- age
- performance
- strategic value
- audience usefulness
- duplication
- evidence age
- search visibility
- compliance risk
- business value
- maintenance cost
- relationship to other assets
Website Production Operating Model
When creating or improving a website, Content Brain should:
- Confirm the business objective.
- Confirm the audience.
- Confirm the site purpose.
- Review existing pages where applicable.
- Identify required pages.
- Identify missing, weak, duplicate or outdated pages.
- Define create, refresh, merge, link, retire or no-action decisions.
- Create the site content plan.
- Create page briefs where required.
- Produce complete page copy.
- Review page relationships.
- prepare internal linking.
- complete editing and specialist review.
- obtain human approval.
- prepare pages for publishing.
- record future refresh and measurement needs.
A website content project may include:
- home page
- about page
- service pages
- product pages
- category pages
- location pages
- landing pages
- FAQs
- lead-generation pages
- supporting articles
- email follow-up
- social launch content
- content refresh plan
Article Production Operating Model
When producing an article, Content Brain should:
- Confirm the article objective.
- Confirm the audience and intent.
- Check whether suitable content already exists.
- Confirm the source material.
- confirm evidence requirements.
- define the angle and content role.
- create a brief or outline where required.
- produce the full article.
- edit for accuracy, usefulness, structure and clarity.
- review evidence and claims.
- review search and internal-link requirements where applicable.
- obtain human approval.
- prepare the publishing package.
- record lifecycle and refresh requirements.
An article is not complete merely because text has been generated.
It must be suitable for its intended destination.
Social Content Operating Model
When producing social content, Content Brain should:
- Confirm the platform.
- Confirm the audience.
- Confirm the objective.
- Confirm the source asset or message.
- define the hook.
- adapt the structure to platform behaviour.
- produce the post, caption, thread, carousel or script.
- confirm the call to action.
- review tone, clarity and compliance.
- obtain approval.
- prepare platform-ready output.
- record whether the asset belongs to a larger series or campaign.
Social repurposing must not be generic copying.
Each platform version must fit the destination.
Script Production Operating Model
When producing scripts, Content Brain should:
- Confirm the script type.
- Confirm the audience.
- Confirm the platform or delivery environment.
- Confirm the objective.
- define the hook and opening.
- define the structure.
- define pacing and duration.
- produce the complete script.
- add scene, shot, voiceover or on-screen guidance where required.
- review claims and evidence.
- edit for spoken delivery.
- obtain approval.
- prepare the production-ready script.
Advertising Content Operating Model
Ads Brain controls advertising strategy and testing.
Content Brain creates the required advertising assets.
The operating process is:
- Receive the approved campaign requirement from Ads Brain, Affiliate Brain or Martyn.
- confirm the offer and audience.
- confirm the platform.
- confirm the angle and test requirement.
- confirm claim and compliance boundaries.
- confirm the destination and message-match requirement.
- create the required copy, hook, script, advertorial or pre-sell asset.
- create controlled variations where required.
- review for message match and compliance.
- obtain human approval.
- deliver the asset to the authorised campaign process.
Content Brain does not control:
- campaign budgets
- bid strategy
- platform setup
- test interpretation
- optimisation
- scaling
Newsletter And Email Operating Model
When producing newsletters or email sequences, Content Brain should:
- Confirm the audience or list.
- Confirm the objective.
- Confirm the email type.
- Confirm the source content or offer.
- define the sequence where multiple emails are required.
- define subject lines and preview text.
- produce the full email content.
- define the call to action.
- review tone, claims and compliance.
- obtain human approval.
- prepare the email-platform-ready output.
- record follow-up and measurement needs.
Content Brain does not send emails automatically under the current operating model.
Manuals, Guides And Documentation Operating Model
When producing manuals, guides or documentation, Content Brain should:
- Confirm the user or reader.
- Confirm the required outcome.
- confirm the process or subject.
- assemble authoritative source material.
- define the structure.
- create step-by-step content.
- include warnings, requirements or dependencies.
- review technical and factual accuracy.
- test clarity and completeness.
- obtain specialist review where required.
- obtain human approval.
- prepare the final delivery format.
- define future update ownership.
Content Pack Operating Model
A content pack is a coordinated set of assets supporting one objective.
The operating process is:
- Confirm the central objective.
- Confirm the audience.
- confirm the campaign, site, product or offer.
- define all required assets.
- define asset relationships.
- define production order.
- assemble shared source intelligence.
- create shared message and evidence controls.
- create each asset for its specific channel.
- review cross-asset consistency.
- complete specialist review where required.
- obtain human approval.
- prepare each asset for its destination.
- record the pack as one coordinated project.
- measure individual assets and the pack as a whole where possible.
A content pack may include:
- website page
- article
- newsletter
- email sequence
- social posts
- social carousel
- video script
- short-form scripts
- ad copy
- advertorial
- lead magnet
- checklist
- internal-link actions
- publishing notes
Site Intelligence Operating Role
Site Intelligence is a supporting capability within Content Brain.
Its role is to identify:
- missing content
- thin content
- outdated content
- duplicate content
- overlapping content
- weak content
- content gaps
- refresh opportunities
- internal-linking opportunities
- compliance concerns
- publishing-readiness issues
- site structure issues
- content that should not be recreated
Site Intelligence must lead to an action decision.
Possible actions include:
- create
- refresh
- expand
- merge
- repurpose
- relink
- correct
- retire
- no action
- specialist review
- content project required
Site Intelligence must not become a separate Research Brain.
It must not define the entire Content Brain interface.
The current Site Intelligence Records screen remains a temporary test and diagnostic layer.
Cross-Brain Operating Boundaries
Research Brain
Research Brain supplies deep research, validated insights, emerging insights and source intelligence.
Content Brain converts approved research into content.
Content Brain must not duplicate broad research work.
Strategy Brain
Strategy Brain supplies positioning, narrative direction, launch priorities and strategic context.
Content Brain converts approved strategy into content assets.
Customer Brain
Customer Brain supplies customer states, motivations, language and journey context.
Content Brain uses these inputs to improve audience relevance.
Affiliate Brain
Affiliate Brain supplies offer and funnel requirements.
Content Brain creates the required affiliate content.
Ads Brain
Ads Brain supplies campaign and testing requirements.
Content Brain creates advertising content assets.
Creative Brain
Creative Brain supplies creative direction, emotional angles, concepts and narratives.
Content Brain produces complete assets from approved creative direction.
Conversion Brain
Conversion Brain supplies friction, trust, behavioural and conversion guidance.
Content Brain applies these requirements during production.
Compliance Brain
Compliance Brain supplies claim, policy and regulatory authority.
Content Brain must follow Compliance Brain decisions.
Data Brain
Data Brain supplies measurement and performance signals.
Content Brain uses approved signals for lifecycle decisions.
Experimentation Brain
Experimentation Brain controls test validity and interpretation.
Content Brain creates controlled test variants.
Search Intelligence
Search Intelligence supplies demand, intent and visibility inputs.
Content Brain creates and improves suitable search content.
SIT Brain
SIT Brain monitors authority, integrity and drift.
Content Brain must remain within approved operating status.
MCR Operating Boundary
MCR is the source of truth.
MCR contains:
- Canon
- architecture
- operating models
- governance
- master frameworks
- master templates
- master specifications
- approved operating rules
Before creating a new Content Brain page, the operator must check:
- exact MCR title match
- close MCR title match
- an MCR page covering the same purpose
- a Content Brain site-only operational page
- whether the item belongs in Supabase instead
A Content Brain site-only page must not be treated as Canon unless deliberately promoted or copied into MCR.
Content Brain Site Operating Boundary
The Content Brain site is the operational working environment.
It may contain:
- manual workflows
- plugin screens
- operating pages
- implementation pages
- working copies
- approved operational tools
- temporary test interfaces
The Content Brain site must not become the source of truth merely because it contains more recent implementation work.
Supabase Operating Boundary
Supabase stores repeatable structured records.
Future Content Brain records may include:
- content requests
- content projects
- content assets
- briefs
- source references
- evidence references
- production state
- review state
- approval state
- publishing state
- destination state
- refresh state
- repurposing state
- performance signals
- compliance flags
- archive state
Supabase records must not be treated as Canon.
Temporary Site Intelligence test fields must not define the complete Content Brain data model.
WordPress Page Boundary
WordPress pages should be used for:
- Canon
- architecture
- operating models
- frameworks
- protocols
- templates
- specifications
- operating pages
- short summary logs
- approved working copies
Repeatable production items should not become individual WordPress pages when structured records are the correct destination.
Current Records UI Decision
The Site Intelligence Records UI has proven that WordPress can:
- read Supabase records
- display active records
- add records
- view record detail
- safely edit records
- archive records
- hide archived records from the normal view
- calculate operational signals
This technical proof is useful.
However:
- the current screen is not the Content Brain home
- the current screen is not the production workspace
- the current record model is not the complete Content Brain data model
- the current labels make the screen appear too research-oriented
- further feature work must not continue until the main Content Brain operating model is respected
The current screen may remain as a supporting Site Intelligence area.
It must not define the future Content Brain product.
Future Main Operational Interface
The future main Content Brain interface should eventually support:
- content requests
- active content projects
- asset plans
- content packs
- briefs
- drafts
- production state
- review state
- approval state
- publishing preparation
- destination state
- completed assets
- refresh requirements
- repurposing requirements
- Site Intelligence inputs
- source relationships
- evidence relationships
- operational blockers
- next actions
The exact interface must follow validated manual work.
It must not be built from assumptions alone.
Future Automation Boundary
Future automation may include:
- request intake
- project creation
- brief creation
- controlled content drafting
- controlled editing
- compliance pre-checks
- review routing
- approval workflows
- publishing preparation
- refresh recommendations
- repurposing recommendations
- queue management
- worker processes
- AI Employees
- Brain Room routing
- publishing integrations
- status updates
- performance feedback
No future capability is authorised merely because it appears in this Operating Model.
Before activation, it must have:
- a proven manual workflow
- defined authority
- defined permissions
- stable records
- approval gates
- failure handling
- audit visibility
- human override
- safe rollback or correction
- SIT approval where required
Operating Prohibitions
Content Brain must not:
- create content without a clear purpose
- create duplicate content without reason
- create new WordPress pages before checking MCR
- treat Content Brain site pages as Canon
- treat Supabase records as Canon
- invent evidence
- invent facts
- invent sources
- invent testimonials
- invent customer experiences
- bypass Research Brain where deep research is required
- bypass Compliance Brain where specialist review is required
- bypass human approval
- publish automatically under the current status
- send newsletters automatically
- post social content automatically
- deploy ads automatically
- create autonomous workers
- activate AI Employees
- activate Brain Room routing
- send work to M automatically
- touch M’s Research Brain work
- build queues before the operating workflow is stable
- let Site Intelligence replace the full Content Brain
- let temporary test records define permanent architecture
Operating Success Standard
The Content Brain Operating Model is working correctly when Martyn can provide a real request and Content Brain can:
- determine whether work is needed
- identify whether the action is create, refresh, merge, repurpose, link, retire or no action
- identify the required project and assets
- assemble the correct source inputs
- create appropriate briefs
- produce complete content
- edit and improve it
- identify specialist review needs
- prepare it for human approval
- prepare it for publishing or delivery
- preserve the record of what was produced
- receive future performance signals
- recommend the correct lifecycle action
The operating model must support requests such as:
- create a complete business website
- produce a full article
- create a social media campaign
- create a YouTube video script
- create short-form video scripts
- create advertising assets
- create a newsletter
- create an email sequence
- create a manual
- create a lead magnet
- create an affiliate content pack
- improve an existing website
- refresh an existing article
- repurpose a source asset across several channels
Final Operating Rule
Content Brain exists to produce useful content, not only to study, classify or recommend it.
Every supporting layer must serve the complete path from approved need to usable content and long-term lifecycle management.
MCR remains the source of truth.
The Content Brain site remains the operational working environment.
Supabase remains the structured records layer.
Site Intelligence remains a supporting diagnostic capability.
Human control remains active until a later approved operating change.
Change Log
v1.2 — 2026-06-15
Expanded the Content Brain Operating Model to align with the revised Content Brain Canon and Content Brain Architecture.
Added the complete human-controlled operating process for:
- request intake
- qualification
- action decisions
- content projects
- source and intelligence assembly
- asset planning
- content briefing
- content production
- editing
- specialist review
- human approval
- publishing preparation
- delivery
- measurement
- lifecycle management
Added dedicated operating models for:
- website production
- article production
- social content
- scripts
- advertising content
- newsletters
- email sequences
- manuals
- guides
- documentation
- content packs
Clarified:
- Martyn’s workstream ownership
- MCR source-truth requirements
- Content Brain site boundaries
- Supabase boundaries
- Site Intelligence’s supporting role
- the temporary status of the current Records UI
- future production interface requirements
- future automation controls
- protection against Content Brain drifting into Research Brain
v1.1 — 2026-05-06
Expanded the Content Brain Operating Model to support structured execution, production, optimisation, refresh, repurposing, quality review, affiliate content deployment and cross-Brain support.
v1.0 — 2026-04-09
Initial creation of the Content Brain Operating Model.