Brain Name: Content Brain
Document Type: Operational Copy
Status: Draft
Version: v1.1
Authority: Content Brain under HeadOffice governance
Applies To: mwmscontentbrain.site future content brief page, Content Brain manual briefing workflow, content requests, content projects, content assets, website content, articles, social content, scripts, advertising content, newsletters, email sequences, manuals, documentation, affiliate content packs, refresh work, repurposing work and publishing preparation
Parent: Content Brain
Enforcement Mode: Operational
Last Reviewed: 2026-06-16
Content Brain Content Brief Template Operational Copy
Purpose
The Content Brain Content Brief Template Operational Copy defines the prepared future operator template for briefing Content Brain production work.
This page remains an MCR-controlled operational copy.
It is not yet the live mwmscontentbrain.site content brief page.
Its purpose is to give an operator a practical and proportionate structure for turning qualified content work into a clear production instruction.
The brief connects:
the original content request
the qualification decision
the existing-content check
the selected content action
the related content project
the individual content asset
the approved sources and evidence
the production requirements
the editing requirements
the specialist-review requirements
the human-approval requirements
the publishing-preparation requirements
the intended destination
the future lifecycle requirements
A content brief is a production tool.
It is not:
the starting point for every Content Brain task
a substitute for qualification
a substitute for checking existing content
a substitute for approved research
a substitute for content production
a completed content asset
an approval decision
a publishing instruction
an automation trigger
Scope
This operational copy applies to:
full content briefs
short production briefs
direct production instructions
website-content briefs
article briefs
social-content briefs
script briefs
advertising-content briefs
newsletter briefs
email briefs
email-sequence briefs
manual briefs
guide briefs
documentation briefs
lead-magnet briefs
training-content briefs
content-pack briefs
affiliate-support briefs
refresh briefs
repurposing briefs
content-correction briefs
content-expansion briefs
content-merge briefs
internal-linking requirements
publishing-preparation requirements
This operational copy does not replace:
Content Brain Canon
Content Brain Architecture
Content Brain Operating Model
Content Brain Workflow Map
Content Brain Content Brief Template
Content Brain SEO Content Brief Standard
Content Brain Page Registry
Content Brain Copy Map
approved research
approved strategy
approved customer intelligence
approved compliance decisions
approved campaign requirements
human approval
This page does not authorise:
unrestricted content generation
autonomous content production
autonomous publishing
automatic task routing
worker activation
queue execution
AI Employee activation
Brain Room routing
automatic M handoff
changes to M’s Research Brain work
Core Rule
Use the smallest briefing structure that gives production enough clarity and control.
Do not force every task into a large formal brief.
Use:
a Full Content Brief for complex, high-value or higher-risk work
a Short Production Brief for clear and contained content work
a Direct Production Instruction for simple, low-risk and well-defined work
The briefing level must match:
the complexity of the asset
the number of connected assets
the number of Brains involved
the research requirement
the evidence requirement
the compliance risk
the destination risk
the approval requirement
the cost of getting the content wrong
Every briefing method must still identify:
what is being produced
why it is being produced
who it is for
where it will be used
what approved sources support it
what must not be claimed
who must review it
who must approve it
what happens after production
Briefing Position In The Workflow
The correct workflow position is:
Content Request
Qualification
Existing Content Check
Action Decision
Content Project Where Required
Asset Planning
Source And Evidence 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
Lifecycle Management
The brief must not be created before the operator understands:
the request
the selected action
the asset
the available source material
the intended destination
the approval requirements
Briefing Decision
Before creating a brief, choose one briefing level.
Full Content Brief
Use when:
the content is strategically important
the content is commercially important
the content is compliance sensitive
the content uses research that must be interpreted
the asset is complex
multiple assets are connected
multiple Brains are involved
a major website page is required
a major article is required
a campaign script is required
an advertising asset is required
an email sequence is required
a content pack is required
specialist review is likely
the destination has significant risk
Short Production Brief
Use when:
the request has already been qualified
the content action is clear
the asset is clearly defined
the audience is known
the destination is known
the approved sources are available
the production requirements are contained
the approval path is clear
Direct Production Instruction
Use when:
the task is simple
the required change is minor
the source material is complete
the exact asset is known
the intended result is clear
the destination is known
the work is low risk
the approval owner is known
Examples include:
correcting a confirmed error
updating a confirmed date
rewriting a short section
creating a short approved social variation
reformatting approved content
adding an approved internal link
updating approved metadata
creating a minor derivative from approved source content
No Brief
A new brief is not required when:
the work should not proceed
the request is rejected
the request is parked
another Brain must act first
no content action is required
existing approved content can be reused without change
the asset is already covered by an active approved brief
Briefing Status
Each brief should show one current status.
Available statuses:
Draft Brief
Waiting For Information
Waiting For Sources
Waiting For Research
Waiting For Strategy
Waiting For Product Information
Waiting For Compliance Direction
Waiting For Human Decision
Ready For Production
Returned For Correction
Superseded
Cancelled
Completed
A brief should not be marked Ready For Production unless the minimum production inputs are available.
Full Content Brief Template
Brief Identity
Brief Title:
Brief ID:
Brief Version:
Brief Status:
Date Created:
Last Updated:
Created By:
Related Request:
Related Project:
Related Asset:
Related Parent Asset:
Request And Action
Original Request:
Request Source:
Requesting Human Or Brain:
Business Or Workstream:
Selected Content Action:
Create
Refresh
Expand
Correct
Merge
Repurpose
Reformat
Relink
Retire
Other Approved Action
Reason For Selected Action:
Existing Content Checked:
Yes / No
Existing Asset Reference:
Why Existing Content Is Not Sufficient:
Project Context
Project Title:
Project Objective:
Project Owner:
Related Assets:
Asset Production Order:
Dependencies:
Known Blockers:
Content Asset
Working Asset Title:
Asset Type:
Asset Purpose:
Primary Objective:
Secondary Objective:
Required Outcome:
Completion Standard:
Asset Relationship:
Standalone Asset
Supporting Asset
Parent Asset
Child Asset
Part Of Content Pack
Part Of Website Project
Part Of Campaign
Part Of Sequence
Part Of Refresh Programme
Audience
Primary Audience:
Secondary Audience:
Audience Stage:
Problem Or Need:
Desired Outcome:
Current Knowledge Level:
Known Objections:
Known Questions:
Required Customer Language:
Language Or Phrases To Avoid:
Intent
Primary Intent:
Secondary Intent:
Search Intent Where Relevant:
Reader Intent:
Business Intent:
Journey Or Funnel Role:
Required Next Action:
Destination And Channel
Primary Destination:
Secondary Destination:
Channel:
Platform:
Format:
Required Length Or Duration:
Publishing Owner:
Delivery Owner:
Destination Requirements:
Sources And Evidence
Primary MCR Source Pages:
Approved Research Sources:
Approved Strategy Sources:
Approved Customer Intelligence:
Approved Product Or Offer Information:
Approved Data:
Approved Statistics:
Approved Examples:
Approved Testimonials:
Approved Case Studies:
Existing Content Sources:
Site Intelligence Findings:
Other Approved Sources:
Evidence Gaps:
Research Required:
Yes / No
Research Owner:
Source Classification
Classify each important input as:
Confirmed Fact
Verified Evidence
Approved Strategy
Validated Insight
Approved Human Instruction
Approved Customer Language
Emerging Signal
Working Assumption
Restricted Claim
Unverified Claim
Working assumptions and emerging signals must not be presented as confirmed facts.
Unverified claims must not be used as factual statements.
Content Direction
Core Message:
Primary Promise Or Outcome:
Supporting Messages:
Required Angle:
Required Perspective:
Required Information Gain:
Required Differentiation:
Required Examples:
Required Proof Elements:
Required Trust Elements:
Required Experience Elements:
Required Expertise Elements:
Required Authority Elements:
Required Objection Handling:
Required Questions To Answer:
Required Call To Action:
Content Structure
Required Opening:
Required Hook:
Required Introduction:
Required Sections:
Required Headings:
Required Sequence:
Required Summary:
Required Closing:
Required Call To Action Placement:
Required Supporting Elements:
Tables
Checklists
Examples
Frequently Asked Questions
Comparisons
Steps
Warnings
Definitions
Statistics
Sources
Visual Notes
Voice And Editorial Requirements
Required Voice:
Required Tone:
Required Reading Level:
Required Terminology:
Required Brand Language:
Words Or Phrases To Use:
Words Or Phrases To Avoid:
Formatting Requirements:
Editorial Consistency Requirements:
Accessibility Requirements:
Information-Gain Requirements:
Trust Requirements:
SEO Requirements
Use this section only where search visibility is relevant.
Primary Topic:
Primary Keyword Or Query:
Secondary Topics:
Search Intent:
SERP Or Competitor Context:
Required Search Coverage:
Required Information Gain:
Suggested Title:
Suggested Slug:
Meta Title Requirement:
Meta Description Requirement:
Heading Requirements:
Internal-Link Requirements:
External-Reference Requirements:
Schema Or Structured-Content Notes:
SEO requirements must not override usefulness, accuracy or reader intent.
Internal Linking Requirements
Required Source Pages:
Required Target Pages:
Suggested Anchor Text:
Reader-Journey Purpose:
Topic-Authority Purpose:
Funnel Or Conversion Purpose:
Links To Avoid:
New Link Opportunities:
Claims And Compliance
Compliance Risk:
Low
Moderate
High
Unknown
Claims Allowed:
Claims Restricted:
Claims Prohibited:
Required Disclosures:
Required Disclaimers:
Required Qualifications:
Evidence Required For Claims:
Sensitive Topics:
Compliance Review Required:
Yes / No
Compliance Reviewer:
Legal Review Required:
Yes / No
Other Specialist Review Required:
Yes / No
Specialist Type:
Content Brain must not turn:
a possibility into a certainty
an emerging signal into proven evidence
a customer opinion into a verified fact
a correlation into causation
a product claim into a medical claim
a working assumption into approved truth
Production Requirements
Required Output:
Full Finished Asset
First Draft
Outline
Script
Copy Set
Content Pack
Refresh Revision
Repurposed Asset
Publishing Package
Other Approved Output
Production Owner:
Production Priority:
Production Deadline:
Required Production Notes:
Required Creative Notes:
Required Visual Notes:
Required Technical Notes:
Required Platform Notes:
Required Asset Variations:
Production must create the requested asset.
It must not replace production with recommendations unless recommendations were the requested output.
Editing And Quality-Control Requirements
Editing Required:
Yes / No
Editing Type:
Structural
Developmental
Clarity
Factual
Voice
Compliance
Channel Adaptation
Formatting
Full Quality Review
Quality Checks Required:
Objective fulfilled
Audience aligned
Intent aligned
Accurate
Evidence supported
Complete
Clear
Useful
Well structured
Voice aligned
Claims controlled
Information gain present
Trust elements present
Call to action clear
Internal links correct
Destination requirements met
Duplication removed
Unsupported statements removed
Reviewer:
Specialist Review
Specialist Review Required:
Yes / No
Specialist Type:
Compliance
Legal
Medical
Technical
Financial
Research
Product
Offer
Search
Data
Campaign
Brand
Stakeholder
Client
Specialist Reviewer:
Reason Required:
Review Deadline:
Required Review Output:
Approved
Approved With Changes
Changes Required
Evidence Required
Blocked
Rejected
Human Approval
Human Approval Required:
Yes
Approval Owner:
Additional Approvers:
Approval Deadline:
Approval Decision Required:
Approved Destination:
Approved Version:
Approval Conditions:
Content must not move to publishing preparation without the required approval.
Publishing Preparation
Publishing Preparation Required:
Yes / No
Destination Owner:
Required Final Title:
Required Slug:
Required Metadata:
Required Internal Links:
Required External Links:
Required Images:
Required Alt Text:
Required Media:
Required Disclosures:
Required Tracking:
Required Formatting:
Required Delivery Package:
Required Publication Notes:
Publishing preparation does not equal publication.
Measurement And Lifecycle
Signal To Watch:
Measurement Owner:
Measurement Source:
Review Date:
Expected Outcome:
Refresh Trigger:
Repurposing Potential:
Expansion Potential:
Merge Potential:
Retirement Conditions:
Lifecycle Owner:
Known Risks And Blockers
Known Source Gaps:
Known Evidence Gaps:
Known Approval Gaps:
Known Compliance Risks:
Known Technical Risks:
Known Destination Risks:
Known Timing Risks:
Known Dependencies:
Current Blocker:
Next Action
Immediate Next Action:
Next Action Owner:
Next Action Due:
Ready For Production:
Yes / No
Reason Not Ready:
Final Brief Decision
Brief Decision:
Ready For Production
Waiting For Information
Waiting For Research
Waiting For Approval Direction
Waiting For Specialist Direction
Returned For Correction
Cancelled
Superseded
Decision Owner:
Decision Date:
Decision Notes:
Short Production Brief Template
Use this template for clear and contained work.
Brief Title:
Related Request:
Related Project:
Related Asset:
Selected Action:
Asset Type:
Asset Purpose:
Audience:
Destination:
Required Outcome:
Approved Sources:
Core Message:
Required Structure:
Required Call To Action:
Voice And Tone:
Claims Allowed:
Claims Restricted:
Compliance Review Required:
Specialist Review Required:
Approval Owner:
Production Owner:
Deadline:
Publishing Preparation Required:
Signal To Watch:
Known Blocker:
Next Action:
Ready For Production:
Yes / No
Direct Production Instruction Template
Use this template for simple, low-risk and well-defined work.
Task:
Target Asset:
Required Change Or Output:
Reason:
Approved Source:
Text Or Section Affected:
Audience:
Destination:
Restrictions:
Approval Owner:
Completion Standard:
Deadline:
Next Action After Completion:
Direct Production Instruction Rule
A direct instruction must not be used to bypass:
research requirements
source requirements
compliance review
specialist review
human approval
It is a shorter production instruction.
It is not reduced governance for risky work.
Website Content Brief
Use the Full Content Brief with these additional fields.
Website Name:
Website Objective:
Page Type:
Page Role:
Site Audience:
Journey Stage:
Parent Page:
Child Pages:
Related Pages:
Required Internal Links:
Page-Specific Call To Action:
Search Intent:
Conversion Role:
Trust Requirements:
Cross-Page Consistency Requirements:
Required Page Components:
Navigation Requirements:
Publishing Destination:
Article Brief
Use the Full Content Brief with these additional fields.
Article Type:
Educational
Informational
Commercial
Affiliate Review
Comparison
Buyer Guide
How-To
List
Case Study
Authority
Thought Leadership
Research Led
Search Led
Refresh
Primary Question:
Search Intent:
Primary Topic:
Supporting Topics:
Required Information Gain:
Required Examples:
Required Internal Links:
Required External Evidence:
Required FAQ Coverage:
Refresh Date:
Social Content Brief
Use the Short Production Brief or Full Content Brief depending on complexity.
Platform:
Content Format:
Post
Carousel
Thread
Short Script
Community Post
Series
Comment Response
Objective:
Hook:
Core Message:
Audience Action:
Source Asset:
Required Adaptation:
Platform Restrictions:
Visual Direction:
Caption Requirements:
Hashtag Requirements:
Approval Owner:
Repurposing Relationship:
Script Brief
Use the Full Content Brief for major scripts.
Script Type:
YouTube
YouTube Short
TikTok
Instagram Reel
Webinar
VSL
Sales Video
Explainer
Product Demonstration
Podcast
Voiceover
Presentation
Training
Advertisement
Platform Or Environment:
Target Duration:
Spoken Audience:
Opening Hook:
Core Narrative:
Required Sections:
Pacing:
Scene Notes:
Shot Notes:
Voiceover Notes:
On-Screen Text:
Proof Requirements:
Claim Restrictions:
Call To Action:
Production Handoff:
Advertising Content Brief
Use the Full Content Brief.
Requesting Brain:
Campaign:
Offer:
Product:
Audience:
Platform:
Funnel Stage:
Test Role:
Angle:
Hook:
Primary Message:
Destination:
Message-Match Requirement:
Required Variations:
Claims Allowed:
Claims Restricted:
Compliance Review:
Ads Brain Review:
Human Approval Owner:
Campaign Hand-Off Destination:
Content Brain creates the advertising content.
Ads Brain retains campaign and optimisation authority.
Newsletter Brief
Newsletter Name:
Audience Or List:
Issue Objective:
Main Topic:
Supporting Topics:
Source Material:
Required Sections:
Editorial Angle:
Primary Call To Action:
Secondary Call To Action:
Promotional Content:
Educational Content:
Links:
Subject-Line Requirement:
Preview-Text Requirement:
Sending Owner:
Approval Owner:
Signal To Watch:
Email Brief
Email Type:
Promotional
Educational
Welcome
Nurture
Launch
Affiliate Promotion
Re-Engagement
Post-Purchase
Abandoned Cart
Transactional Support
Audience Or Segment:
Sequence Position:
Email Objective:
Source Offer Or Content:
Subject-Line Requirement:
Preview-Text Requirement:
Opening:
Core Message:
Proof:
Objection Handling:
Call To Action:
Links:
Claims Restrictions:
Sending Owner:
Approval Owner:
Signal To Watch:
Email Sequence Brief
Sequence Name:
Sequence Objective:
Audience:
Trigger:
Number Of Emails:
Sequence Structure:
Email 1 Purpose:
Email 2 Purpose:
Email 3 Purpose:
Additional Email Purposes:
Progression Logic:
Primary Call To Action:
Secondary Call To Action:
Stop Conditions:
Compliance Requirements:
Approval Owner:
Sending Owner:
Manual Guide Or Documentation Brief
Document Type:
Manual
Guide
Standard Operating Procedure
Training Document
Workbook
Checklist
Playbook
Report
White Paper
Ebook
Lead Magnet
Onboarding Pack
Client Document
Course Lesson
Knowledge-Base Content
Reader Or User:
Required Outcome:
Authoritative Sources:
Required Steps:
Required Sections:
Warnings:
Dependencies:
Technical Requirements:
Examples:
Screenshots Or Visuals:
Specialist Reviewer:
Update Owner:
Review Date:
Delivery Format:
Content Pack Brief
Project Or Pack Name:
Central Objective:
Audience:
Campaign, Product, Service Or Offer:
Required Assets:
Asset Relationships:
Production Order:
Shared Sources:
Shared Evidence:
Shared Message:
Shared Voice:
Shared Claims:
Shared Restrictions:
Individual Asset Briefs Required:
Yes / No
Cross-Asset Consistency Reviewer:
Approval Owner:
Publishing Or Delivery Destinations:
Pack-Level Completion Standard:
Pack-Level Signal To Watch:
Affiliate Product Content Pack Brief
Use only after Affiliate Brain direction and offer status are clear.
Affiliate Offer:
Offer Status:
Affiliate Brain Owner:
Target Audience:
Funnel Role:
Traffic Source:
Primary Destination:
Research Basis:
Offer Evidence:
Claims Allowed:
Claims Restricted:
Compliance Risk:
Required Assets:
Review Page
Comparison Page
Buyer Guide
Pre-Sell Page
FAQ
Objection Content
Article
Social Posts
Video Script
Ad Support Asset
Other Approved Asset
Asset Relationships:
Internal Links:
Call To Action:
Affiliate Brain Review Required:
Compliance Review Required:
Approval Owner:
Handoff Destination:
Signal To Watch:
SEO Content Brief
Use with the Content Brain SEO Content Brief Standard.
Primary Topic:
Primary Query:
Search Intent:
Audience Intent:
Page Or Article Type:
Existing Content Checked:
Competing Existing Asset:
Content Gap:
SERP Context:
Primary Angle:
Required Information Gain:
Required Evidence:
Required Trust Elements:
Required Sections:
Required Questions:
Required Internal Links:
Required External References:
Title Requirement:
Slug Requirement:
Metadata Requirement:
Schema Notes:
Call To Action:
Publishing Destination:
Approval Owner:
Search Performance Signal:
SEO instructions support production.
They do not replace a complete audience-focused content brief.
Refresh Brief
Existing Asset:
Current URL Or Location:
Refresh Trigger:
Scheduled Review
Performance Decline
New Research
Outdated Evidence
Changed Product Information
Changed Offer Information
Search Change
Compliance Change
Broken Links
Thin Content
Site Intelligence Finding
Other Approved Trigger
Current Asset Purpose:
Existing Audience:
Current Destination:
Selected Refresh Action:
Update
Expand
Correct
Merge
Relink
Reformat
Republish
Retire
Current Problems:
Sections To Preserve:
Sections To Change:
New Sources:
New Evidence:
Claims To Review:
Links To Update:
Metadata To Update:
Approval Required:
Publishing Owner:
Measurement After Refresh:
Next Review Date:
Repurposing Brief
Approved Source Asset:
Source Asset Version:
Source Approval Status:
Repurposing Objective:
New Format:
New Channel:
New Audience Or Audience Stage:
Meaning To Preserve:
Claims To Preserve:
Claims That Must Not Be Strengthened:
Required Adaptation:
New Hook:
New Structure:
New Call To Action:
Platform Requirements:
Required Variations:
Review Owner:
Approval Owner:
Publishing Or Delivery Owner:
Signal To Watch:
Repurposing must adapt approved content to the new destination.
It must not become uncontrolled copying.
Merge Brief
Assets To Merge:
Primary Asset:
Secondary Assets:
Reason For Merge:
Useful Material To Preserve:
Duplicated Material To Remove:
New Combined Purpose:
New Combined Audience:
New Structure:
Source And Evidence Check:
Redirect Requirements:
Archive Requirements:
Retirement Requirements:
Internal-Link Updates:
Approval Owner:
Publishing Owner:
Completion Standard:
Correction Brief
Target Asset:
Confirmed Problem:
Problem Type:
Factual
Evidence
Compliance
Editorial
Technical
Link
Formatting
Voice
Destination
Required Correction:
Approved Correct Source:
Affected Sections:
Risk If Not Corrected:
Specialist Review Required:
Approval Owner:
Publishing Owner:
Completion Standard:
Brief Readiness Check
Before production begins, confirm:
the request is qualified
existing content has been checked
the content action is clear
the project is known where required
the asset is defined
the audience is defined
the destination is defined
approved sources are available
evidence gaps are recorded
working assumptions are identified
restricted claims are identified
production requirements are clear
review requirements are clear
the approval owner is known
the next action is clear
If a required field is unknown:
do not invent the answer
mark it as unknown
record the blocker
identify the owner
request the missing input
Production Handoff
When the brief is ready, the production handoff should include:
approved brief version
asset title
asset type
production owner
approved sources
source restrictions
required output
required structure
voice and tone
claims allowed
claims restricted
compliance requirements
review requirements
approval owner
deadline
completion standard
A production handoff must not include hidden assumptions.
Brief Change Control
A brief may change after production begins.
Material changes include:
objective change
audience change
destination change
asset-type change
source change
claim change
offer change
product change
strategy change
compliance change
approval-owner change
major deadline change
Where a material change occurs:
pause affected production
update the brief version
record the change
confirm affected sources
confirm affected claims
confirm review requirements
confirm approval requirements
resume production only when the change is clear
Minor editorial clarification does not require a full new brief version unless it changes meaning or authority.
Approval Boundaries
Content Brain preserves the following boundaries.
HeadOffice controls governance and major structural decisions.
Strategy Brain controls strategic direction.
Research Brain controls broad research evidence, confidence and research truth.
Customer Brain controls approved customer intelligence.
Creative Brain controls approved creative direction where applicable.
Affiliate Brain controls affiliate offer direction and affiliate campaign requirements.
Ads Brain controls advertising campaigns, testing and optimisation.
Conversion Brain controls conversion strategy.
Compliance Brain controls compliance interpretation and risk decisions.
Finance Brain controls financial and budget authority.
Experimentation Brain controls test validity and interpretation.
Data Brain controls data quality and trusted measurement.
Content Brain creates and manages content from approved inputs.
The brief must identify where another Brain’s decision is required.
It must not silently make that decision inside Content Brain.
Source-Of-Truth Rule
MCR remains the source of truth for:
Content Brain Canon
Content Brain Architecture
Content Brain Operating Model
Content Brain Workflow Map
Content Brain Content Brief Template
Content Brain SEO Content Brief Standard
Content Brain master frameworks
Content Brain master standards
Content Brain master templates
This operational copy provides practical operator guidance.
It does not replace the controlling MCR source pages.
Supabase Position
Future structured brief records may be stored in Supabase.
A structured brief record may include:
brief identity
request relationship
project relationship
asset relationship
selected action
audience
destination
source references
evidence references
production requirements
review requirements
approval requirements
status
blockers
next action
archive state
Supabase records must not replace the controlling template or Canon.
Plugin And UI Position
A future Content Brief workspace may eventually support:
brief creation
brief editing
request linking
project linking
asset linking
source linking
evidence linking
status tracking
blocker tracking
review routing
approval tracking
brief versioning
production handoff
No Content Brief Generator or full Brief workspace is authorised by this page.
Manual use must first prove:
the required fields
the optional fields
the asset-specific fields
the statuses
the relationships
the exceptions
the approval flow
Operator Warnings
Do Not Begin Every Task With A Full Brief
Choose the smallest suitable briefing method.
Do Not Skip Qualification
A clear-looking request may still be:
duplicated
out of scope
unsupported
blocked
owned by another Brain
Do Not Invent Missing Sources
Unknown sources must remain unknown until resolved.
Do Not Turn Assumptions Into Facts
Working assumptions must be labelled.
Do Not Treat A Brief As Content
A brief directs production.
It is not the completed asset.
Do Not Treat A Brief As Approval
Approval remains a separate decision.
Do Not Treat Ready For Production As Ready For Publishing
Production, editing, specialist review, human approval and publishing preparation still remain.
Do Not Automate Yet
Do not activate:
automatic brief generation
automatic source collection
automatic production
automatic review routing
automatic approval
automatic publishing
workers
queues
AI Employees
Brain Room routing
automatic M handoff
Current Operational Copy Status
Prepared In MCR: Yes
Replacement Page Required Due To Existing Page Size: Yes
Existing v1.0 Page To Move To Trash After Validation: Yes
Aligned With Content Brain Canon v1.1: Yes
Aligned With Content Brain Architecture v1.1: Yes
Aligned With Content Brain Operating Model v1.2: Yes
Aligned With Content Brain Workflow Map v1.2: Yes
Aligned With Content Brain Home Operational Copy v1.1: Yes
Aligned With Content Brain Workflow Operational Copy v1.1: Yes
Aligned With Content Brain Content Brief Template v1.2: Yes
Aligned With Content Brain Page Registry v3.3: Yes
Aligned With Content Brain Copy Map v2.8: Yes
Migrated To mwmscontentbrain.site: No
Live Operational Template: No
Connected To Full Plugin Or UI: No
Connected To Content Generation Automation: No
Connected To Publishing Automation: No
Connected To Workers: No
Connected To Queues: No
Connected To AI Employees: No
Connected To Brain Room Routing: No
Connected To M Handoff: No
Research Brain Impact: None
Relationship To Content Brain Home Operational Copy
The Home Operational Copy provides the operator’s starting point.
This page provides the appropriate briefing structure after:
the request is understood
the request is qualified
existing content has been checked
the content action has been selected
the asset has been planned
Relationship To Content Brain Workflow Operational Copy
The Workflow Operational Copy defines when a brief or direct production instruction is required.
This page defines how that briefing is completed.
Relationship To Content Brain Content Brief Template
Content Brain Content Brief Template v1.2 remains the controlling MCR template.
This operational copy simplifies and organises that template for future operator use.
Relationship To Content Brain SEO Content Brief Standard
SEO-specific work must use the SEO Content Brief Standard where search requirements are material.
The SEO standard adds specialist search fields.
It does not replace the universal content-production requirements.
Relationship To Content Brain Page Registry
This page should be recorded as:
Page Title: Content Brain Content Brief Template Operational Copy
Document Type: Operational Copy
Version: v1.1
Parent Page: Content Brain
Status: Draft
Migration Classification: MCR Only First
Plugin Or UI Candidate: Possible Content Brief Workspace Later
Notes: Prepared operational briefing template supporting full briefs, short production briefs and direct production instructions. Connects requests, projects, assets, sources, production, review, approval and publishing preparation.
Relationship To Content Brain Copy Map
The controlling Content Brain Content Brief Template is classified as:
Simplify Before Copy
This v1.1 operational copy provides the simplified operator structure.
It remains:
MCR Only First
Not migrated
Not live
Not connected to a production interface
Relationship To mwmscontentbrain.site
This page is prepared future operator content for mwmscontentbrain.site.
It must not be copied until:
the manual briefing workflow is validated
the required fields are confirmed
the revised operational structure is accepted
migration is approved
destination duplication is checked
source links are preserved
the new operational page is validated
rollback remains possible
Replacement Page Procedure
Because the existing v1.0 WordPress page is too large for safe replacement:
create a new WordPress page
use the exact title:
Content Brain Content Brief Template Operational Copy
set Parent to:
Content Brain
publish the complete v1.1 replacement
confirm the new page displays correctly
confirm the page title is exact
confirm the Parent is Content Brain
confirm the version inside the page is v1.1
confirm only one active page has the exact title
move the old v1.0 page to Trash as recovery
do not permanently delete the old page during replacement validation
Drift Protection
The system must prevent:
this page being treated as live migration
this page replacing the controlling Content Brief Template
this page replacing Content Brain Canon
this page replacing Content Brain Architecture
this page overriding Content Brain Workflow Map
this page overriding Content Brain Copy Map
every task being forced into a large brief
complex work being reduced to an unsafe direct instruction
briefs being created before qualification
briefs being created without existing-content checks
briefs being treated as completed assets
briefs being treated as approval
briefs being treated as publishing authority
unsupported sources being invented
working assumptions being presented as facts
restricted claims being used without approval
Content Brain being reduced to briefing
content production being omitted
editing being omitted
human approval being omitted
publishing preparation being omitted
automation being activated before manual proof
workers being activated
queues being activated
AI Employees being activated
Brain Room routing being activated
automatic M handoff
interference with M’s Research Brain work
Architectural Intent
The Content Brain Content Brief Template Operational Copy exists to connect approved content work to complete content production.
Its role is to help an operator move from:
a qualified request
to:
a defined action
to:
a defined project or asset
to:
approved sources and evidence
to:
a proportionate production instruction
to:
complete production
The briefing structure must provide enough clarity to prevent:
random content
unsupported content
duplicated content
misdirected content
unapproved claims
unclear ownership
unclear review requirements
unclear approval requirements
It must not become a bureaucratic barrier that stops straightforward content work.
The correct principle is:
enough structure for safe production
no unnecessary structure
Final Rule
A content brief exists to enable production.
It does not replace production.
Use:
a Full Content Brief for complex or higher-risk work
a Short Production Brief for clear and contained work
a Direct Production Instruction for simple, low-risk work
Do not brief work that should not proceed.
Do not invent missing information.
Do not create new content without checking existing content.
Do not treat assumptions as facts.
Do not treat a brief as approval.
Do not treat a draft as a completed asset.
Do not treat publishing preparation as publication.
MCR remains the source of truth.
mwmscontentbrain.site remains the future operational environment.
Supabase remains the structured records layer.
Human approval remains mandatory.
No content generation automation is authorised.
No publishing automation is authorised.
No worker is authorised.
No queue execution is authorised.
No AI Employee is authorised.
No Brain Room routing is authorised.
No automatic M handoff is authorised.
M’s Research Brain work remains untouched.
Change Log
Version: v1.1
Date: 2026-06-16
Author: HeadOffice
Change: Rewritten to align the Content Brain Content Brief Template Operational Copy with the complete request-to-lifecycle Content Brain workflow.
Replaced the earlier rule that important content must always begin with a formal brief.
Added proportional briefing through:
Full Content Brief
Short Production Brief
Direct Production Instruction
No-Brief decisions where work should not proceed or an existing approved brief already controls the asset
Added relationships to:
content requests
qualification decisions
existing-content checks
content action decisions
content projects
content assets
source records
evidence records
production requirements
editing requirements
specialist-review requirements
human approval
publishing preparation
measurement and lifecycle requirements
Expanded the Full Content Brief to include:
brief identity
request relationship
project relationship
asset relationship
existing-content decision
source classification
evidence gaps
content direction
content structure
voice and editorial requirements
SEO requirements where relevant
internal-linking requirements
claims and compliance
production requirements
editing and quality control
specialist review
human approval
publishing preparation
measurement
lifecycle requirements
blockers
next actions
Added specialist briefing structures for:
website content
articles
social content
scripts
advertising content
newsletters
emails
email sequences
manuals
guides
documentation
content packs
affiliate product content packs
SEO content
refresh work
repurposing
merging
corrections
Added:
brief-readiness checks
production-handoff requirements
brief change control
future Supabase record position
future Content Brief workspace position
replacement-page procedure
expanded drift protection
Clarified that:
a brief is a production tool
a brief is not the starting point for every task
a brief is not a completed asset
a brief is not approval
a brief is not publishing authority
simple work may use a direct production instruction
complex or higher-risk work requires stronger briefing
Content Brain must not invent missing sources or evidence
MCR remains the source of truth
manual workflow remains human controlled
no content generation, publishing automation, worker, queue, AI Employee, Brain Room routing or automatic M handoff is authorised
M’s Research Brain work remains untouched
Version: v1.0
Date: 2026-05-24
Author: HeadOffice
Change: Initial creation of Content Brain Content Brief Template Operational Copy. Defined the prepared simplified future content brief template for mwmscontentbrain.site, including full brief fields, fast brief version, affiliate product content-pack brief, SEO content brief, VEO3 pre-video support brief, repurposing brief, refresh brief, operator warnings, approval boundaries and source-of-truth controls.
Change Impact Declaration
Pages Created:
One replacement page using the existing exact title:
Content Brain Content Brief Template Operational Copy
Pages Updated:
None
Pages To Move To Trash After Validation:
Old Content Brain Content Brief Template Operational Copy v1.0 page
Pages Permanently Deleted:
None
Pages Deprecated:
Old v1.0 page after the v1.1 replacement is validated and moved to Trash
Registries Requiring Update:
Content Brain Page Registry
Content Brain Copy Map
Canon Version Update Required:
No
Architecture Version Update Required:
No
Operating Model Version Update Required:
No
Workflow Map Version Update Required:
No
Automation Status Change:
No
Plugin Or UI Status Change:
No
Worker Status Change:
No
Queue Status Change:
No
AI Employee Status Change:
No
Brain Room Routing Status Change:
No
M Handoff Required:
No
Research Brain Impact:
None
END CONTENT BRAIN CONTENT BRIEF TEMPLATE OPERATIONAL COPY v1.1
END OF FULL FILE OUTPUT