Content Brain Workflow Map

Document Type: Workflow Map
Version: v1.2
Parent Page: Content Brain
Status: Active
Migration Classification: Copy To Content Brain
Plugin Or UI Candidate: Possible Workflow Dashboard Later
Notes: Defines the complete movement of work from request, need or opportunity through intake, qualification, existing-content checking, action decision, project definition, asset planning, intelligence assembly, briefing or direct production instruction, content production, editing, specialist review, human approval, publishing preparation, human-controlled publication or delivery, outcome recording, measurement and lifecycle action. Includes dedicated branches for websites, articles, social content, scripts, advertising, newsletters, emails, manuals, documentation, content packs, refresh, merging, repurposing and Site Intelligence.

Content Brain Workflow Map

Purpose

The Content Brain Workflow Map defines how content work moves through Content Brain from the first request, need or opportunity to a completed asset and its later lifecycle decisions.

The Workflow Map converts the Content Brain Canon, Content Brain Architecture and Content Brain Operating Model into a clear movement path.

It governs how Content Brain:

receives content requests
qualifies the work
checks whether suitable content already exists
decides what action is required
creates projects where needed
plans content assets
assembles approved source material
creates briefs or direct production instructions
produces complete content
edits and improves content
manages specialist review
obtains human approval
prepares assets for publication or delivery
records outcomes
receives measurement and feedback
refreshes, repurposes, improves, consolidates, retires or archives content

The Workflow Map must support both:

individual content assets
coordinated multi-asset content projects

The Workflow Map must not reduce Content Brain to:

Site Intelligence
research records
content opportunities
briefs
publishing checklists
compliance signals
content recommendations
WordPress pages
Supabase records

These are supporting parts of the workflow.

They are not the complete workflow.

Primary Workflow

The main Content Brain workflow is:

Request, Need Or Opportunity
→ Intake
→ Qualification
→ Existing Content Check
→ Action Decision
→ Project Definition Where Required
→ Asset Planning
→ Source And Intelligence Assembly
→ Brief Or Direct Production Instruction
→ Content Production
→ Editing And Quality Control
→ Specialist Review Where Required
→ Human Approval
→ Publishing Preparation
→ Human-Controlled Publication Or Delivery
→ Outcome Recording
→ Measurement And Feedback
→ Lifecycle Decision

The lifecycle decision may result in:

monitor
refresh
improve
expand
repurpose
consolidate
relink
correct
redistribute
retire
archive
no action

Current Workflow Status

The current workflow remains manual and human controlled.

Current operating status:

Martyn controls the Content Brain 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 content worker
no autonomous publishing
no autonomous social posting
no autonomous newsletter sending
no autonomous advertising deployment
no autonomous queue execution
no Brain Room routing
no automatic M handoff
no AI Employee authority activated
no full Content Brain production interface completed
no full generator completed
no unrestricted content generation

The current Site Intelligence Records screen remains a supporting technical proof.

It is not the main Content Brain workflow.

Workflow Entry Points

Content work may enter Content Brain through several valid entry points.

Human Request

A direct instruction from Martyn or another authorised human.

Examples:

create a website
write an article
create a newsletter
create a social campaign
write a script
create an email sequence
create a manual
improve an existing page
repurpose an existing asset

Brain Request

A request or approved input from another MWMS Brain.

Examples:

Affiliate Brain requests an affiliate content pack
Ads Brain requests ad scripts
Strategy Brain requests launch content
Research Brain supplies approved intelligence
Customer Brain supplies audience language
Product Brain requests user documentation
Ecommerce Brain requests product education content

Site Intelligence Finding

A website review identifies:

missing content
thin content
duplicate content
outdated content
weak internal linking
publishing-readiness problems
compliance concerns
refresh opportunities
repurposing opportunities

Performance Signal

Data or feedback indicates:

content underperformance
content decay
weak engagement
weak conversion support
ranking decline
outdated evidence
poor user understanding
high-performing content worth expanding or repurposing

Existing Content Lifecycle Trigger

An existing asset reaches a scheduled or evidence-based review point.

Campaign Or Launch Trigger

A launch, promotion, offer, product, service or campaign requires coordinated content.

Stage 1: Intake

The Intake stage records the content request, need or opportunity.

The intake should identify as much of the following as is available:

request title
request source
requesting Brain or human
business or workstream
objective
target audience
audience stage
requested asset
channel
destination
source material
required outcome
deadline
constraints
approval owner
known dependencies

The request may be incomplete at intake.

It must not proceed directly into production simply because it was submitted.

Intake Decision

At the end of Intake, the request moves to:

Qualification
Hold For Missing Information
Reject As Out Of Scope
Return To Requester
Escalate To Another Brain

Stage 2: Qualification

Qualification determines whether the request is valid, necessary and ready.

The qualification checks are:

Does this work belong to Content Brain?
Is the objective clear?
Is the audience clear enough?
Is the destination known?
Is the required asset or result understood?
Does suitable content already exist?
Is deeper research required?
Is strategy direction required?
Is offer or product information missing?
Are compliance requirements known?
Is specialist review likely?
Is the request one asset or a larger project?
Would the work create duplicate or unnecessary content?
Is the request commercially, operationally or strategically useful?
Is human approval ownership clear?

Qualification Outcomes

The request may be:

Qualified
Qualified With Conditions
Held For Missing Information
Returned To Another Brain
Rejected
Converted Into A Review Task
Converted Into A Content Project
No Action Required

Stage 3: Existing Content Check

Before new content is created, Content Brain checks whether suitable content already exists.

The check should include:

existing MCR source pages where the work is governance-related
existing Content Brain operational pages where the work is implementation-related
existing website content
existing articles
existing emails
existing newsletters
existing scripts
existing social assets
existing manuals
existing content packs
existing Supabase records where the item is repeatable structured work

The check must determine whether the correct action is:

create
refresh
expand
correct
merge
repurpose
reformat
relink
retire
archive
no action

Stage 4: Action Decision

Content Brain makes one clear action decision.

Create

Create a new asset because no suitable asset exists.

Refresh

Update an existing asset because it remains useful but is outdated, incomplete or weak.

Expand

Add meaningful depth, evidence, examples or supporting sections.

Correct

Repair inaccurate, unclear, misleading, non-compliant or broken content.

Merge

Combine overlapping assets into a stronger single asset.

Repurpose

Adapt an approved source asset into a new format or channel.

Reformat

Change the delivery format while preserving the main purpose.

Relink

Improve internal linking, calls to action or asset relationships.

Retire

Remove an asset from active use.

No Action

Do not create or change content because the existing state is sufficient.

Another Brain First

Pause Content Brain work because another Brain must supply authority or input.

Specialist Review First

Pause production until a specialist issue is resolved.

Action Decision Output

Every action decision should record:

selected action
reason
target asset or project
source requirement
next step
approval owner
known blocker

Stage 5: Project Definition

A Content Project is created when the work includes multiple related assets or requires coordinated production.

A project may support:

a business website
a site redesign
an affiliate offer
a launch
a campaign
a product
a service
a newsletter programme
an email sequence
a social media series
a video series
an advertising package
a manual or documentation package
a content refresh programme
a repurposing programme

A project should define:

project name
project objective
originating request
business or workstream
target audience
audience stage
requesting source
project owner
required assets
channels
destinations
source requirements
evidence requirements
compliance requirements
dependencies
production order
approval points
current stage
blocked conditions
next action
completion criteria

A simple one-asset request may skip formal project creation and move directly to Asset Planning.

Project Decision

The request becomes:

Single Asset Work
Multi-Asset Project
Website Project
Campaign Project
Content Pack
Refresh Programme
Repurposing Programme
Documentation Project
Hold
Reject

Stage 6: Asset Planning

Asset Planning defines exactly what must be created, updated or adapted.

Each asset should define:

asset type
asset title or working title
objective
audience
audience stage
channel
destination
format
length
message
angle
call to action
source requirements
evidence requirements
compliance requirements
relationship to other assets
production order
review requirement
approval owner
completion standard

Possible asset categories include:

Website Assets

home page
about page
service page
product page
category page
collection page
landing page
bridge page
advertorial
affiliate review page
comparison page
buyer guide
FAQ page
local page
authority page
pillar page
topic hub
supporting page
onboarding page
knowledge-base page

Article Assets

educational article
informational article
commercial article
affiliate review
comparison article
buyer guide
how-to article
list article
case study
authority article
thought-leadership article
research-led article
search-led article
evergreen article
refreshed 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 asset

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 ad copy
description
hook
search ad
display ad
native ad
YouTube ad script
Meta ad copy
TikTok ad script
advertorial
pre-sell content
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

Manuals 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

Stage 7: Source And Intelligence Assembly

Content Brain assembles the approved material needed for production.

Possible inputs include:

business objective
strategic direction
offer intelligence
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
voice guidance
brand guidance
creative direction
conversion requirements
compliance rules
previous performance data
experiment learnings
human instructions

Each input should be classified where possible as:

confirmed fact
verified evidence
approved strategy
validated insight
emerging signal
working assumption
human instruction
content interpretation

Working assumptions must not be presented as confirmed truth.

Source Assembly Outcomes

The asset may be:

Ready For Briefing
Ready For Direct Production
Waiting For Research
Waiting For Strategy
Waiting For Offer Information
Waiting For Product Information
Waiting For Compliance Direction
Waiting For Human Input
Blocked

Research Required Branch

Where deep research is required:

Content Request
→ Qualification
→ Research Gap Identified
→ Research Brain Or Approved Human Research
→ Research Output Reviewed
→ Source Assembly Updated
→ Production Continues

Content Brain must not replace Research Brain’s broad research authority.

Stage 8: Brief Or Direct Production Instruction

Content Brain decides whether the work requires:

a full content brief
a short production brief
an outline
a script structure
an asset plan
a direct production instruction

A brief may include:

objective
audience
audience stage
intent
asset type
channel
destination
message
angle
source material
evidence
structure
headings
questions to answer
objections to address
trust requirements
conversion role
call to action
voice and tone
compliance constraints
internal-link requirements
metadata requirements
approval requirements
completion criteria

A large formal brief is not mandatory for simple work.

The workflow must apply proportional control.

Briefing Outcomes

The asset becomes:

Ready For Production
Returned For Missing Information
Returned For Source Correction
Returned For Scope Correction
Held
Cancelled

Stage 9: Content Production

Content Brain creates the actual content.

The Production stage may produce:

outline
full page copy
article
social post
carousel copy
script
ad copy
advertorial
pre-sell content
newsletter
email
email sequence
manual
guide
report
checklist
workbook
lead magnet
content pack
refreshed asset
repurposed asset

Production must follow:

approved objective
audience requirements
source material
evidence boundaries
channel requirements
message requirements
voice requirements
compliance constraints
asset relationships
completion criteria

Content Brain must produce the requested asset.

It must not replace a completed asset with recommendations when production has been approved.

Production Outcomes

The asset becomes:

Draft Complete
Partial Draft
Blocked
Source Gap Found
Compliance Risk Found
Scope Conflict Found
Returned To Planning
Cancelled

Stage 10: Editing And Quality Control

Editing and Quality Control is a separate workflow stage.

It 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-link review
formatting preparation
completeness checking

The review should determine:

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 useful?
Is it complete?
Is the structure appropriate?
Is the persuasion level appropriate?
Is the next action clear?
Does it align with related assets?
Is it ready for specialist or human review?

Editing Outcomes

The asset may be:

Ready For Specialist Review
Ready For Human Approval
Revision Required
Major Rework Required
Evidence Required
Compliance Review Required
Rejected
Held

Stage 11: Specialist Review

Specialist review occurs where the content presents material risk or requires specialist confirmation.

Possible specialist reviews include:

compliance
legal
factual
technical
medical
financial
offer
product
strategy
campaign
brand
stakeholder
client

Specialist review may be required because of:

claim risk
regulatory exposure
technical complexity
financial implications
product accuracy
campaign sensitivity
brand risk
legal risk
reputational risk

Specialist Review Outcomes

The asset may be:

Approved
Approved With Changes
Changes Required
Evidence Required
Blocked
Rejected
Held For Later

Where changes are required:

Specialist Review
→ Revision
→ Editing And Quality Control
→ Specialist Review Or Human Approval

Stage 12: Human Approval

Human approval remains mandatory before publication or delivery under the current operating model.

The approver may:

approve
approve with changes
request revision
reject
hold
request evidence
request specialist review
change the objective
change the destination
stop the project

The workflow must distinguish between:

Draft Complete
Quality Review Complete
Specialist Review Complete
Approved
Publishing-Ready
Published
Delivered

These states must not be merged.

Human Approval Outcomes

The asset becomes:

Approved
Approved With Minor Changes
Revision Required
Rejected
Held
Cancelled

Stage 13: Publishing Preparation

Publishing Preparation converts an approved asset into a destination-ready package.

It may include:

final title
heading structure
metadata
URL guidance
call-to-action placement
internal links
external links
image requirements
creative requirements
alt text
disclosures
compliance notes
platform-specific formatting
version confirmation
asset naming
destination confirmation
publishing checklist
delivery notes

Publishing Preparation Outcomes

The asset becomes:

Publishing-Ready
Delivery-Ready
Formatting Required
Destination Not Confirmed
Asset Missing
Approval Gap Found
Returned For Revision
Held

Stage 14: Human-Controlled Publication Or Delivery

Current publication and delivery remain human controlled.

This includes:

WordPress publishing
website updates
social posting
social scheduling
newsletter sending
email deployment
ad deployment
manual delivery
client delivery
document distribution
ecommerce publication
training delivery

Content Brain may prepare the asset.

An authorised human completes or approves the final publication or delivery action.

Publication And Delivery Outcomes

The asset becomes:

Published
Delivered
Scheduled
Partially Published
Publication Failed
Delivery Failed
Cancelled
Held

Failures must return to the appropriate correction step.

Stage 15: Outcome Recording

After publication or delivery, the workflow should preserve:

asset title
asset type
project
destination
publication or delivery date
version
approving human
source request
related assets
publication state
delivery state
review date
measurement requirements
refresh requirements
archive state

The exact structured record may evolve.

The workflow requirement is to preserve enough information for future review and lifecycle action.

Stage 16: Measurement And Feedback

Content Brain may receive feedback 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 results

Possible signals 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
customer understanding
stakeholder response

The workflow must distinguish between:

useful evidence
weak evidence
temporary fluctuation
confirmed pattern
channel-specific behaviour
asset-specific behaviour
measurement failure

Measurement Outcomes

The asset may be:

Performing As Expected
Strong Performance
Weak Performance
Insufficient Data
Measurement Problem
Refresh Candidate
Repurposing Candidate
Expansion Candidate
Correction Required
Retirement Candidate
No Action

Stage 17: Lifecycle Decision

The Lifecycle Decision determines what happens next.

Available actions include:

monitor
refresh
improve
expand
repurpose
update evidence
update claims
strengthen internal linking
consolidate
reformat
redistribute
reissue
correct
retire
archive
no action

The decision 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

Lifecycle Loop

Measurement And Feedback
→ Lifecycle Decision
→ Refresh, Improve, Repurpose, Consolidate, Correct, Retire Or No Action
→ Updated Asset Planning
→ Source Assembly
→ Production Or Revision
→ Review
→ Approval
→ Publishing Preparation
→ Publication Or Delivery
→ Measurement

New Content Branch

Request
→ Qualification
→ Existing Content Check
→ Create Decision
→ Project Definition Where Required
→ Asset Planning
→ Source Assembly
→ Brief Or Direct Instruction
→ Production
→ Editing
→ Specialist Review Where Required
→ Human Approval
→ Publishing Preparation
→ Publication Or Delivery
→ Measurement
→ Lifecycle Decision

Refresh Branch

Performance Signal, Site Intelligence Finding Or Scheduled Review
→ Existing Asset Identified
→ Refresh Decision
→ Refresh Scope Defined
→ Current Sources Checked
→ New Evidence Added Where Required
→ Content Revised
→ Editing
→ Specialist Review Where Required
→ Human Approval
→ Publishing Preparation
→ Updated Publication
→ Measurement

Merge Branch

Duplicate Or Overlapping Assets Identified
→ Merge Decision
→ Primary Asset Selected
→ Useful Material Preserved
→ Consolidated Structure Created
→ Combined Asset Produced
→ Redirect Or Retirement Requirements Identified
→ Editing
→ Human Approval
→ Publishing Preparation
→ Publication
→ Old Assets Retired Or Archived
→ Measurement

Repurposing Branch

Approved Source Asset Identified
→ Repurposing Objective Defined
→ Channel And Format Selected
→ Audience And Call To Action Confirmed
→ Platform-Specific Asset Plan Created
→ Derivative Assets Produced
→ Channel Fit Review
→ Compliance And Quality Review
→ Human Approval
→ Publishing Preparation
→ Publication Or Delivery
→ Measurement

Repurposing must not be generic copying.

Each derivative must fit its destination.

Website Project Branch

Website Request
→ Business Objective Confirmed
→ Audience Confirmed
→ Site Purpose Confirmed
→ Existing Site Reviewed Where Applicable
→ Required Pages Identified
→ Create, Refresh, Merge, Link, Retire Or No-Action Decisions
→ Website Content Project Created
→ Page Relationships Planned
→ Source And Intelligence Assembly
→ Page Briefs Created Where Required
→ Full Page Copy Produced
→ Cross-Page Consistency Review
→ Internal Linking Review
→ Specialist Review Where Required
→ Human Approval
→ Publishing Preparation
→ Human-Controlled Publication
→ Site Measurement
→ Refresh And Lifecycle Review

A website project may include:

home page
about page
service pages
product pages
category pages
collection pages
landing pages
location pages
FAQs
lead-generation pages
supporting articles
onboarding pages
knowledge-base pages
email follow-up
social launch content
refresh plan

Article Branch

Article Request Or Opportunity
→ Objective Confirmed
→ Audience And Intent Confirmed
→ Existing Article Check
→ Create Or Refresh Decision
→ Source And Evidence Assembly
→ Angle Defined
→ Brief Or Outline
→ Full Article Production
→ Editing For Accuracy, Structure And Usefulness
→ Search And Internal-Link Review Where Applicable
→ Specialist Review Where Required
→ Human Approval
→ Publishing Preparation
→ Publication
→ Measurement
→ Refresh Or Repurposing Decision

Social Content Branch

Social Request Or Source Asset
→ Platform Confirmed
→ Audience Confirmed
→ Objective Confirmed
→ Message And Hook Defined
→ Asset Type Selected
→ Platform-Specific Production
→ Tone, Clarity And Compliance Review
→ Human Approval
→ Platform-Ready Formatting
→ Human-Controlled Posting Or Scheduling
→ Engagement Review
→ Improve, Extend, Repurpose Or Stop

Possible outputs include:

Facebook post
Instagram caption
Instagram carousel
LinkedIn post
X post
X thread
YouTube community post
TikTok concept
short-form script
social series

Script Branch

Script Request
→ Script Type Confirmed
→ Platform Or Delivery Environment Confirmed
→ Audience Confirmed
→ Objective Confirmed
→ Hook And Opening Defined
→ Structure, Pacing And Duration Defined
→ Full Script Produced
→ Scene, Shot, Voiceover Or On-Screen Guidance Added Where Required
→ Spoken Delivery Edit
→ Evidence And Claim Review
→ Human Approval
→ Production-Ready Script Delivered
→ Performance Or Use Feedback
→ Revision Or Repurposing Decision

Advertising Content Branch

Approved Campaign Requirement
→ Ads Brain, Affiliate Brain Or Martyn Defines Need
→ Offer Confirmed
→ Audience Confirmed
→ Platform Confirmed
→ Angle And Test Requirement Confirmed
→ Claim And Compliance Boundaries Confirmed
→ Destination And Message Match Confirmed
→ Ad Copy, Script, Advertorial Or Pre-Sell Asset Produced
→ Controlled Variations Created Where Required
→ Message Match Review
→ Compliance Review
→ Human Approval
→ Asset Delivered To Authorised Campaign Process
→ Campaign Performance Returned
→ Variant Improvement Or Retirement Decision

Ads Brain retains authority over:

campaign strategy
platform setup
budgets
bidding
test interpretation
optimisation
scaling

Newsletter And Email Branch

Email Or Newsletter Request
→ Audience Or List Confirmed
→ Objective Confirmed
→ Email Type Confirmed
→ Source Content Or Offer Confirmed
→ Sequence Defined Where Required
→ Subject Lines And Preview Text Created
→ Full Email Content Produced
→ Call To Action Confirmed
→ Tone, Claims And Compliance Reviewed
→ Human Approval
→ Email-Platform-Ready Output
→ Human-Controlled Sending
→ Open, Click And Conversion Feedback
→ Improve, Extend, Refresh Or Stop

Manual And Documentation Branch

Manual, Guide Or Documentation Request
→ Reader Or User Confirmed
→ Required Outcome Confirmed
→ Process Or Subject Confirmed
→ Authoritative Sources Assembled
→ Structure Defined
→ Step-By-Step Content Produced
→ Warnings, Requirements And Dependencies Added
→ Technical And Factual Review
→ Clarity And Completeness Review
→ Specialist Review Where Required
→ Human Approval
→ Final Delivery Format Prepared
→ Human-Controlled Delivery
→ Update Ownership And Review Date Recorded

Content Pack Branch

Central Objective Confirmed
→ Audience Confirmed
→ Campaign, Site, Product Or Offer Confirmed
→ All Required Assets Defined
→ Asset Relationships Defined
→ Production Order Defined
→ Shared Source Intelligence Assembled
→ Shared Message And Evidence Controls Created
→ Each Asset Produced For Its Specific Channel
→ Cross-Asset Consistency Review
→ Specialist Review Where Required
→ Human Approval
→ Each Asset Prepared For Its Destination
→ Human-Controlled Publication Or Delivery
→ Individual And Pack-Level Measurement
→ Refresh, Extend, Repurpose Or Retire Decision

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 Branch

Site Or Content Estate Selected
→ Existing Content Reviewed
→ Missing, Weak, Thin, Duplicate, Outdated Or Risky Content Identified
→ Content Action Decision Made
→ Create, Refresh, Merge, Repurpose, Relink, Correct, Retire Or No Action
→ Content Request Or Project Created Where Required
→ Main Content Production Workflow Continues

Site Intelligence does not end with a research record.

It must lead toward a practical content decision.

The current Site Intelligence Records screen may preserve:

test records
evidence
review outcomes
build signals
compliance flags
routing recommendations
archive state

It must not become the main Content Brain workflow.

No-Action Branch

Request Or Opportunity
→ Qualification
→ Existing Content Check
→ No Action Decision
→ Reason Recorded
→ Request Closed
→ Future Review Trigger Added Only If Required

No-action decisions protect Content Brain from unnecessary production.

Rejected Request Branch

Request
→ Qualification
→ Request Outside Scope, Unsupported, Duplicate, Unsafe Or Low Value
→ Rejection Reason Recorded
→ Requester Informed
→ Request Closed Or Returned

Blocked Work Branch

Work In Progress
→ Missing Source, Evidence, Authority, Approval Or Specialist Decision
→ Blocker Recorded
→ Work Held
→ Required Input Requested
→ Work Resumes When Blocker Is Resolved

Blocked work must not be marked complete.

Cross-Brain Workflow

Content Brain may receive inputs from other Brains.

The general cross-Brain workflow is:

Content Need Identified
→ Required Brain Input Identified
→ Human-Controlled Request Or Existing Approved Input Used
→ Input Received
→ Authority And Evidence Checked
→ Content Production Continues

Current status:

no autonomous cross-Brain routing
no automatic Brain Room task creation
no automatic M handoff
no autonomous worker delegation

Research Brain Workflow Boundary

Research Brain:

performs broad research
validates insights
preserves evidence
identifies confidence
supplies source intelligence

Content Brain:

consumes approved research
translates research into content
performs limited content-specific source checks
identifies missing research

The boundary is:

Research Produces Intelligence
→ Content Brain Produces Content

Ads Brain Workflow Boundary

Ads Brain:

defines campaign strategy
defines platform
defines testing structure
defines optimisation rules
evaluates campaign performance

Content Brain:

creates ad copy
creates ad scripts
creates advertorials
creates pre-sell content
creates landing-page message-match content
creates controlled content variants

Compliance Workflow Boundary

Content Production
→ Risk Identified
→ Compliance Review Required
→ Compliance Decision
→ Approved, Revised, Blocked Or Rejected
→ Human Approval
→ Publishing Preparation

Content Brain must not bypass a required Compliance Brain or human compliance decision.

MCR Workflow Boundary

Before creating a new Content Brain governing or source page:

Need Identified
→ Exact MCR Title Check
→ Close MCR Title Check
→ Existing Source Page Check
→ Content Brain Site Operational Page Check
→ Supabase Record Suitability Check
→ Update, Merge, Avoid, Create, Hold Or Store As Record

MCR remains the source of truth.

Content Brain Site Workflow Boundary

The Content Brain site supports:

operational working pages
manual workflows
plugin screens
implementation pages
working copies
approved operational tools
temporary test interfaces

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

Supabase Workflow Boundary

Supabase supports repeatable structured records such as:

content requests
content projects
asset records
briefs
source references
evidence references
production state
review state
approval state
publishing state
destination state
performance signals
refresh state
repurposing state
compliance flags
archive state

Supabase records must not be treated as Canon.

WordPress Page Workflow Boundary

WordPress pages should be used for:

Canon
architecture
operating models
workflow maps
frameworks
protocols
templates
specifications
operating pages
short summary logs
approved working copies

Repeatable content records should not become separate WordPress pages where Supabase is the correct destination.

Current Records UI Position

The current Site Intelligence Records UI has proven:

Supabase records can be read
active records can be displayed
records can be added
detail can be viewed
records can be safely edited
records can be archived
archived records can be hidden
operational signals can be calculated

The screen remains useful as:

a Site Intelligence test area
a structured records proof
a diagnostic support screen

It is not:

the Content Brain home
the production workspace
the content project screen
the asset planning screen
the drafting workspace
the review queue
the publishing workspace
the full Content Brain product

Future Main Workflow Interface

The future main Content Brain interface should eventually show:

incoming requests
qualified work
active content projects
asset plans
source requirements
briefs
drafts
production status
editing status
specialist review
human approval
publishing preparation
destination status
published or delivered assets
refresh requirements
repurposing requirements
blockers
next actions
Site Intelligence inputs
source relationships
evidence relationships

The interface must follow this workflow.

The workflow must not be redesigned around the temporary Site Intelligence test fields.

Future Automation Workflow Boundary

Future automation may support:

intake
qualification assistance
existing-content checks
project creation
asset planning
brief creation
controlled drafting
controlled editing
compliance pre-checks
review routing
approval workflows
publishing preparation
refresh recommendations
repurposing recommendations
status updates
queues
worker processes
AI Employees
Brain Room routing
publishing integrations
performance feedback

No automation is authorised by this Workflow Map.

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

Workflow Prohibitions

The workflow must not:

start production without sufficient qualification
create new content without checking existing content
create new MCR pages without checking exact and close matches
treat Content Brain site pages as MCR source truth
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
mark drafts as approved
mark approved assets as published before publication
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 workflow is stable
let Site Intelligence replace the full Content Brain
let temporary records define permanent architecture

Workflow Success Standard

The Workflow Map is working correctly when Content Brain can take a real request and clearly show:

where the work entered
why the work is required
whether suitable content already exists
what action was selected
whether a project is required
what assets are required
what sources are required
whether research is required
whether a brief is required
what has been produced
what editing has occurred
what specialist review is required
whether human approval has been obtained
whether the asset is publishing-ready
whether it has been published or delivered
what outcome was recorded
what measurement is required
what lifecycle decision follows

Standard Workflow Summary

Final Workflow Rule

Content Brain must move work from an approved need to a usable content asset.

The workflow must support production, not replace it with research, records, briefs or recommendations.

Site Intelligence is a supporting entry point.

Research Brain supplies intelligence.

Other Brains supply authority and specialist inputs.

Content Brain plans, creates, edits, prepares and manages content through its lifecycle.

Humans retain final control until a later approved operating change.

Change Log

v1.2 — 2026-06-15

Expanded the Content Brain Workflow Map to align with the revised Content Brain Canon, Content Brain Architecture and Content Brain Operating Model.

Replaced the narrower opportunity-led workflow with the complete workflow:

Request, Need Or Opportunity
Intake
Qualification
Existing Content Check
Action Decision
Project Definition
Asset Planning
Source And Intelligence Assembly
Brief Or Direct Production Instruction
Content Production
Editing And Quality Control
Specialist Review
Human Approval
Publishing Preparation
Human-Controlled Publication Or Delivery
Outcome Recording
Measurement And Feedback
Lifecycle Decision

Added branch workflows for:

new content
refresh
merge
repurposing
website projects
articles
social content
scripts
advertising content
newsletters
email sequences
manuals
guides
documentation
content packs
Site Intelligence
research-required work
no-action decisions
rejected requests
blocked work

Clarified:

Site Intelligence’s supporting role
Research Brain boundaries
Ads Brain boundaries
Compliance review boundaries
MCR source-truth checks
Content Brain site boundaries
Supabase boundaries
WordPress page boundaries
the temporary position of the current Site Intelligence Records UI
future main workflow interface requirements
future automation controls

v1.1 — 2026-05-28

Expanded the Content Brain Workflow Map to support opportunity classification, content briefing, production, review, publishing readiness, performance feedback, refresh and repurposing.

v1.0 — 2026-04-09

Initial creation of the Content Brain Workflow Map.