Brain Name: Content Brain
Document Type: Specification
Status: Draft
Version: v1.0
Authority: Content Brain under HeadOffice governance
Applies To: Content opportunity intake, content signal classification, affiliate product content planning, search demand content planning, AIBS education content planning, newsletter intelligence routing, cross-brain content prioritisation, future mwmscontentbrain.site operational planning, and future Content Brain plugin or UI planning
Parent: Content Brain Canon
Last Reviewed: 2026-05-24
Content Brain Content Opportunity Queue Specification
Purpose
The Content Brain Content Opportunity Queue Specification defines the queue where incoming signals become possible content opportunities before they enter production.
This page exists to prevent Content Brain from creating random content, chasing every idea, duplicating effort, or moving weak signals into production too early.
The Content Opportunity Queue acts as the intake and decision layer between system intelligence and content production.
It helps Content Brain decide whether a signal should be:
ignored
parked
researched
drafted
reviewed
approved
published
repurposed
refreshed
retired
The queue exists before the Content Production Queue.
The Content Opportunity Queue asks:
is this signal worth turning into content?
The Content Production Queue asks:
how do we track approved content work through production?
This specification defines the opportunity queue structure only.
It does not activate a plugin, create a database table, build a UI screen, automate routing, or interfere with M’s current build work.
Scope
This specification applies to:
content opportunity intake
content signal review
content idea classification
cross-brain content signal capture
affiliate product content opportunity planning
search demand content opportunity planning
AIBS education content opportunity planning
newsletter intelligence content routing
market trend content routing
compliance-sensitive content opportunity review
finance-aware content prioritisation
content opportunity parking
content opportunity rejection
content opportunity promotion into production
future mwmscontentbrain.site operational planning
future Content Brain plugin or UI planning
This specification does not govern:
live plugin development
Supabase implementation
Brain-to-Brain request automation
HeadOffice reporting implementation
Affiliate Brain opportunity approval
Research Brain verdicts
Search Intelligence Brain demand validation
Ads Brain campaign execution
Experimentation Brain test verdicts
Finance Brain capital approval
Compliance Brain compliance decisions
live publishing authority
M’s active build work
Those remain governed by the relevant Brain, Canon, protocol, standard, or implementation layer.
Core Principle
No content should enter production just because a signal exists.
A signal must first become a qualified content opportunity.
A qualified content opportunity should have:
a source
a reason
a target audience
a strategic purpose
a likely content type
a supporting Brain
a required review path
a priority
a risk level
a next action
a feedback destination
If these are unclear, the opportunity should be parked or sent for research before production begins.
Content Brain must protect the system from random production.
Governance Role
The Content Opportunity Queue is an opportunity classification and prioritisation system.
It does not create authority.
It does not approve affiliate offers.
It does not validate research.
It does not validate search demand.
It does not approve paid campaigns.
It does not approve compliance-sensitive claims.
It does not approve budget or capital allocation.
It does not authorise publishing.
It only classifies and tracks possible content opportunities before production.
Content Brain may use the queue to manage possible content work, but final authority remains with the relevant Brain, owner, or human approval path.
Relationship To MCR
MCR remains the source of truth.
This specification belongs in MCR because it defines the structure and future implementation logic of the Content Opportunity Queue.
The MCR version defines:
queue purpose
queue scope
field requirements
status model
source model
priority model
risk model
review rules
promotion rules
future UI candidate logic
drift protection
mwmscontentbrain.site may later operationalise this queue as a working screen, tracker, dashboard panel, or plugin feature.
Relationship To mwmscontentbrain.site
mwmscontentbrain.site is the likely future home of the operational Content Opportunity Queue.
The future queue may appear as:
a manual opportunity tracker
a WordPress admin table
a custom Content Brain page
a dashboard panel
a content opportunity board
a signal review queue
a Supabase-backed workflow surface
a Content Brain intake screen
A simple manual version should be used before any plugin or UI build.
Manual use must prove which fields, statuses, filters, and decisions are actually needed.
MCR To Brain Classification
Destination: Later Plugin Or UI
Reason: Repeated structured interaction, content signal classification, cross-brain opportunity review, priority tracking, risk tracking, and production promotion workflow
Source Of Truth: MCR
Future Use: Content opportunity intake and review screen inside mwmscontentbrain.site
Future Plugin Or UI: Yes
This page should be listed in the Content Brain Copy Map as a future plugin or UI candidate.
Queue Function
The Content Opportunity Queue should track possible content opportunities before production begins.
The queue should support:
signal intake visibility
source Brain visibility
opportunity classification
audience mapping
strategic purpose review
priority review
research requirement visibility
compliance risk visibility
finance priority visibility
SEO or authority value review
conversion value review
repurposing potential review
approval requirement visibility
promotion into production
parking of useful but not urgent opportunities
rejection of weak or unsafe opportunities
feedback routing after decision
The queue should not become a dumping ground.
Every opportunity must have a source, purpose, owner, status, and next action.
Queue Item Definition
A Content Opportunity Queue item is a single possible content opportunity.
A queue item may represent:
newsletter-derived content opportunity
affiliate product content opportunity
search demand content opportunity
research-derived content opportunity
ad learning content opportunity
experiment learning content opportunity
AIBS education content opportunity
market trend content opportunity
product support content opportunity
offer support content opportunity
authority building content opportunity
SEO content opportunity
comparison content opportunity
pre-sell content opportunity
FAQ content opportunity
trust-building content opportunity
objection-handling content opportunity
content refresh opportunity
repurposing opportunity
internal linking opportunity
client education opportunity
sales support content opportunity
compliance clarification content opportunity
Each queue item should move through a clear status model.
Input Sources
The Content Opportunity Queue may receive signals from:
HeadOffice
HeadOffice Newsletter Intelligence
Affiliate Brain
Research Brain
Search Intelligence Brain
Ads Brain
Experimentation Brain
AIBS Brain
Product Brain
Offer Brain
Conversion Brain
Sales Brain
Customer Brain
Compliance Brain
Finance Brain
Data Brain
manual operator request
market trend signal
product or offer intelligence
campaign learning signal
content performance signal
search demand signal
customer question
voice-of-customer insight
Every signal must identify its source.
If the source is unclear, the item should not move into production.
Core Queue Fields
Each Content Opportunity Queue item should include the following fields.
Identity Fields
Opportunity ID
Opportunity Title
Working Title
Date Created
Date Updated
Created By
Current Owner
Next Owner
Status
Priority
Notes
Source Fields
Source Brain
Source Signal
Source Type
Source Location
Source Date
Supporting Brain
Related Brain Request
Related Newsletter Signal
Related Research Signal
Related Search Signal
Related Ad Signal
Related Experiment Signal
Related Offer
Related Product
Related Campaign
Related Topic Cluster
Source Of Truth
Opportunity Definition Fields
Suggested Content Type
Target Audience
Audience Stage
Reader Intent
Strategic Purpose
Business Reason
Content Role
Funnel Role
Search Role
Authority Role
Affiliate Support Role
AIBS Education Role
Sales Support Role
Conversion Support Role
Trust Role
Value Fields
SEO Value
Authority Value
Conversion Value
Affiliate Support Value
AIBS Education Value
Repurposing Potential
Internal Linking Value
Strategic Value
Urgency
Expected Usefulness
Review Fields
Required Research
Research Owner
Approval Rule
Approval Owner
Needs Research Brain Review
Needs Affiliate Brain Review
Needs Search Intelligence Brain Review
Needs Ads Brain Review
Needs Experimentation Brain Review
Needs AIBS Brain Review
Needs Compliance Brain Review
Needs Finance Brain Review
Needs Human Review
Risk Fields
Risk Level
Compliance Risk
Claims Risk
Affiliate Risk
Finance Risk
Search Risk
Data Confidence Risk
Strategic Misalignment Risk
Repurposing Risk
Content Duplication Risk
Thin Content Risk
Decision Fields
Decision
Decision Reason
Decision Owner
Decision Date
Next Action
Promotion Destination
Production Queue Link
Refresh Queue Link
Repurposing Queue Link
Parking Reason
Retirement Reason
Rejection Reason
Feedback Fields
Feedback Destination Brain
Signal To Return
Learning Captured
Future Review Date
Outcome Notes
Lessons Learned
Source Type Model
The queue should classify the type of signal entering the system.
Recommended source types:
newsletter_intelligence
affiliate_opportunity
research_signal
search_demand_signal
ads_signal
experiment_signal
AIBS_education_signal
market_trend_signal
product_signal
offer_signal
customer_question
voice_of_customer_signal
content_performance_signal
compliance_alert
finance_priority_signal
manual_operator_request
content_gap_signal
internal_linking_signal
refresh_signal
repurposing_signal
Suggested Content Type Model
The queue should support these suggested content types:
Blog Post
SEO Article
Authority Article
Pillar Page
Topic Cluster Article
Product Support Page
Affiliate Support Article
Pre Sell Article
Comparison Article
Review Support Article
FAQ Content
Objection Handling Content
Trust Support Page
YouTube Script
VEO3 Pre Video Script
YouTube Description
Email Draft
Newsletter Section
Social Post Set
Short Form Script Seed
AIBS Education Article
Client Facing Explainer
Sales Support Asset
Conversion Support Asset
Research Brief
Internal Linking Plan
Content Refresh Task
Content Repurposing Task
Publishing Readiness Review
Status Model
The Content Opportunity Queue should use a simple status model first.
Recommended status values:
new
classified
parked
research_needed
under_research
ready_for_review
in_review
approved_for_production
promoted_to_production
promoted_to_refresh
promoted_to_repurposing
published_directly
ignored
retired
blocked
closed
Status Definitions
New
The signal has entered the queue but has not yet been classified.
Required next action:
identify source
define owner
classify opportunity
Classified
The opportunity has a source, suggested content type, purpose, audience, and basic priority.
Required next action:
decide whether to research, review, park, ignore, or promote
Parked
The opportunity may be useful later but is not ready or not urgent.
Required next action:
set future review date
record parking reason
Research Needed
The opportunity cannot be judged without more evidence.
Required next action:
send research requirement to Research Brain or relevant owner
Under Research
The opportunity is waiting for research, validation, or supporting evidence.
Required next action:
review research output when available
Ready For Review
The opportunity has enough information for a decision.
Required next action:
review opportunity value, risk, priority, and approval path
In Review
The opportunity is being reviewed by the relevant Brain or human owner.
Required next action:
complete review and record decision
Approved For Production
The opportunity has been approved to become a content task.
Required next action:
create or link production queue item
Promoted To Production
The opportunity has moved into the Content Production Queue.
Required next action:
track through production workflow
Promoted To Refresh
The opportunity has become a refresh task for existing content.
Required next action:
create or link refresh queue item
Promoted To Repurposing
The opportunity has become a repurposing task.
Required next action:
create or link repurposing queue item
Published Directly
The opportunity was small, low risk, and approved for direct use without full production workflow.
Required next action:
record outcome and feedback path
Ignored
The signal is not useful, not relevant, too weak, unsafe, duplicated, or not aligned.
Required next action:
record reason
Retired
The opportunity was previously active or parked but should no longer be pursued.
Required next action:
record retirement reason
Blocked
The opportunity cannot progress.
Required next action:
resolve blocker
Common blockers:
unclear source
unclear purpose
unclear audience
missing research
missing approval owner
unclear offer status
compliance risk
finance concern
duplicate content risk
no destination
dependency on another Brain
manual decision required
Closed
The opportunity has completed its path and requires no further action.
Required next action:
record outcome where useful
Decision Model
Every opportunity should receive a clear decision.
Recommended decisions:
Ignore
Park
Research
Draft
Review
Approve
Publish
Repurpose
Refresh
Retire
Ignore
Use when the opportunity is weak, irrelevant, duplicated, unsafe, misaligned, too vague, or not worth attention.
Park
Use when the opportunity may be useful later but is not urgent, validated, or strategically ready.
Research
Use when more information is needed before Content Brain can act.
Draft
Use when the opportunity is approved for early drafting, outlining, or brief creation.
Review
Use when the opportunity needs a human or Brain-level decision before production.
Approve
Use when the opportunity is approved for production, refresh, or repurposing.
Publish
Use only when the content is small, low risk, approved, and does not require a full production workflow.
Repurpose
Use when an existing approved asset should be adapted into another format.
Refresh
Use when an existing content asset should be updated, strengthened, corrected, or improved.
Retire
Use when the opportunity or related content should no longer be pursued.
Priority Model
The queue should use a simple priority model.
Priority values:
Low
Medium
High
Critical
Low Priority
Useful but not urgent.
May be future content, low-risk education, optional support, or low-impact content.
Medium Priority
Relevant and useful.
Should be completed when capacity allows.
High Priority
Important to active affiliate support, AIBS education, search demand, authority building, content structure, or near-term production.
Critical Priority
Required for active funnel support, major content gap, compliance risk control, HeadOffice priority, or urgent system need.
Critical priority should be used sparingly.
Risk Model
Every opportunity should have a risk level.
Risk values:
Low
Medium
High
Critical
Low Risk
General education, low-sensitivity content, low claims exposure, or internal planning.
Medium Risk
Content involving comparison, affiliate support, product discussion, trust claims, or moderate strategic importance.
High Risk
Content involving health, finance, income, legal, strong claims, testimonials, guarantees, scarcity, urgency, or paid traffic support.
Critical Risk
Content that may expose MWMS to compliance, platform, legal, financial, reputation, or strategic harm if mishandled.
Critical risk requires review before production or publication.
Review Rules
Not every opportunity needs every review.
Required review depends on the source, content type, risk level, and destination.
Possible reviews:
Research Review
Affiliate Review
Search Demand Review
Ads Signal Review
Experimentation Review
AIBS Review
Compliance Review
Finance Review
Conversion Review
Sales Review
Data Review
HeadOffice Review
Human Approval Review
Content Brain should not promote an opportunity into production when the required review path is unclear.
Approval Rules
Approval is required before a content opportunity becomes production work when it involves:
affiliate product recommendations
new offer support content
active funnel support
paid traffic support
health claims
finance claims
income claims
legal claims
testimonials
guarantees
scarcity or urgency language
sensitive comparisons
AIBS client-facing claims
large content packs
programmatic SEO
resource-heavy production
capital-sensitive work
Content Brain may classify and prepare the opportunity.
It does not grant approval by itself.
Research Requirement Rules
An opportunity should be marked Research Needed when:
the source signal is weak
the audience is unclear
the search demand is unclear
the offer status is unclear
the product claim is unsupported
the competitor landscape is unknown
the customer problem is unclear
the content would rely on assumptions
the compliance risk cannot be judged
the opportunity may duplicate existing content
Research Brain should own deeper evidence, source validation, and research verdicts.
Content Brain should not invent missing proof.
Affiliate Product Opportunity Rules
Affiliate product content opportunities must not move into production unless the related offer status is clear.
Required checks:
related offer identified
Affiliate Brain status known
Research Brain evidence available or requested
Compliance risk noted
Finance priority understood where relevant
content pack need assessed
approval owner identified
Affiliate product opportunities may create:
product support page
pre-sell article
FAQ content
objection-handling content
comparison article
review support content
YouTube script
VEO3 pre-video script
email follow-up draft
social post set
repurposing plan
Content Brain does not decide whether an affiliate product should be tested.
Search Demand Opportunity Rules
Search-driven opportunities must identify the search signal source.
Required checks:
search demand source identified
intent type understood
SERP or competitor context known where relevant
reader value clear
topic cluster fit considered
internal linking value considered
thin content risk reviewed
Search Intelligence Brain owns demand discovery.
Content Brain turns approved demand into structured content opportunities.
Ads Signal Opportunity Rules
Ads-driven opportunities may come from hooks, angles, message mismatch, audience objections, trust gaps, or campaign learning.
Required checks:
Ads Brain source signal identified
signal type recorded
hook or angle not treated as proven truth
content support role defined
destination defined
review owner identified
Content Brain may create supporting content from Ads Brain learning.
Content Brain does not declare ad winners.
Experimentation Signal Opportunity Rules
Experiment-driven opportunities may come from test learning, variant performance, message learning, trust learning, or content performance experiments.
Required checks:
Experimentation Brain source signal identified
learning quality understood
test verdict not over-interpreted
content implication clearly stated
required review owner identified
Content Brain may turn valid experiment learning into better content.
Content Brain does not validate the experiment.
AIBS Education Opportunity Rules
AIBS-related opportunities may come from approved AIBS positioning, service education, client objections, sales learning, consultant needs, or authority-building priorities.
Required checks:
AIBS source confirmed
positioning approved
target reader defined
education purpose clear
client-facing risk reviewed
sales support role defined where relevant
AIBS opportunities may create:
authority article
client-facing explainer
FAQ content
sales support article
objection education content
email education sequence
social post set
case-study support notes
Content Brain does not define AIBS strategy.
Compliance Alert Opportunity Rules
Compliance alerts may create content opportunities for safer language, clarification pages, disclaimers, claim reduction, content refresh, or retirement.
Required checks:
Compliance Brain source identified
risk level recorded
claim type identified
affected content identified
review owner assigned
next action defined
Compliance Brain owns compliance interpretation.
Content Brain may prepare safer content structures, but it does not approve risk-sensitive language.
Finance Priority Opportunity Rules
Finance-related signals may influence whether a content opportunity should proceed, wait, or be deprioritised.
Required checks:
resource requirement understood
content value considered
opportunity cost considered
related affiliate or business value identified
Finance Brain input recorded where relevant
Content Brain does not approve spend.
Content Brain may recommend content work, but Finance Brain controls financial discipline.
Promotion Rules
An opportunity may be promoted only when it has:
clear source
clear purpose
clear audience
suggested content type
priority
risk level
review path
approval owner
next action
promotion destination
Promotion destinations may include:
Content Production Queue
Content Refresh Queue
Repurposing Queue
Content Brief Template
SEO Content Brief Standard
Affiliate Product Content Pack Framework
Content Operations Dashboard later
If the opportunity does not meet minimum promotion requirements, it should be parked, researched, blocked, or ignored.
Blocking Rules
A queue item should be marked blocked when progress cannot continue.
Common blocking reasons:
unclear source
unclear strategic purpose
unclear audience
unclear offer status
missing research evidence
missing search validation
missing approval owner
compliance risk
finance concern
data reliability concern
duplicate content concern
no destination
dependency on another Brain
manual review required
operator decision required
The blocked status must include:
blocked reason
next action
next owner
Minimum Viable Opportunity Queue
The minimum useful Content Opportunity Queue should track:
Opportunity Title
Source Brain
Source Signal
Suggested Content Type
Target Audience
Strategic Purpose
Priority
Status
Required Research
Approval Rule
SEO Or Authority Value
Conversion Value
Repurposing Potential
Compliance Risk
Finance Priority
Experimentation Link
Feedback Destination
Owner
Next Action
This is enough to start manually without overbuilding.
Queue Views
The future Content Opportunity Queue should support useful views.
Status View
Groups opportunities by status.
Useful for:
daily review
blocked item detection
opportunity triage
Priority View
Groups opportunities by priority.
Useful for:
deciding what matters most
protecting high-value work
Source Brain View
Groups opportunities by source Brain.
Useful for:
seeing which Brains are creating content demand
understanding cross-brain needs
Content Type View
Groups opportunities by suggested content type.
Useful for:
batch planning
production planning
content pack planning
Risk View
Groups opportunities by risk level or compliance sensitivity.
Useful for:
review planning
preventing unsafe content production
Affiliate Product View
Shows opportunities connected to affiliate products.
Useful for:
content pack planning
pre-sell planning
FAQ planning
review support planning
Search Demand View
Shows opportunities connected to search demand.
Useful for:
SEO planning
topic cluster planning
authority building
AIBS Education View
Shows opportunities connected to AIBS education and authority.
Useful for:
client education
business owner education
sales enablement
authority positioning
Parked View
Shows useful but delayed opportunities.
Useful for:
future planning
weekly review
strategy review
Blocked View
Shows opportunities that cannot progress.
Useful for:
operator review
dependency removal
HeadOffice visibility where needed
Future Data Model
This specification does not activate a database table.
If built later, a future data model may include:
content_opportunity_items
content_opportunity_events
content_opportunity_reviews
content_opportunity_decisions
content_opportunity_handoffs
content_opportunity_feedback
This naming is conceptual only.
Any future Supabase or WordPress implementation must follow MWMS Supabase Naming Standard and MWMS Brain-to-Brain Request Protocol where relevant.
Future Minimal Table Concept
If this becomes a database-backed queue later, a simple first table may include:
id
created_at
updated_at
opportunity_title
working_title
source_brain
source_type
source_signal
supporting_brain
suggested_content_type
target_audience
audience_stage
strategic_purpose
priority
status
risk_level
required_research
approval_rule
approval_owner
seo_value
authority_value
conversion_value
affiliate_support_value
AIBS_education_value
repurposing_potential
compliance_risk
finance_priority
experimentation_link
feedback_destination_brain
decision
decision_reason
blocked_reason
next_action
next_owner
promotion_destination
notes_json
This is not an implementation instruction.
It is a future planning concept only.
First Manual Version
The first version of this queue should be manual.
A manual queue may use:
MCR tracking page
simple spreadsheet
Google Sheet
WordPress page table
Notion-style board
mwmscontentbrain.site page later
Manual use should prove:
which fields are actually needed
which statuses are useful
which source types repeat
which opportunities are worth production
which review rules matter
which views save time
which UI would be useful later
Only after manual use should a plugin or UI be considered.
Future Plugin Or UI Candidate
The Content Opportunity Queue is a strong future plugin or UI candidate.
Possible future features:
Add Opportunity
Classify Source
Assign Source Brain
Set Suggested Content Type
Set Priority
Set Risk Level
Mark Research Needed
Park Opportunity
Approve For Production
Promote To Production Queue
Promote To Refresh Queue
Promote To Repurposing Queue
Record Decision
Record Feedback Destination
Filter By Brain
Filter By Status
Filter By Priority
Filter By Risk
Filter By Content Type
Filter By Affiliate Product
Filter By Search Demand
This should not be built yet.
Manual workflow must prove the need first.
Relationship To Content Brain Operating Model
The Content Brain Operating Model defines Content Brain’s role, boundaries, and responsibilities.
This specification defines the future opportunity queue that helps Content Brain decide which signals should become content work.
Operating Model = role and boundaries
Opportunity Queue = signal-to-content decision layer
Relationship To Content Brain Workflow Map
The Content Brain Workflow Map defines how content work moves through Content Brain.
The Content Opportunity Queue sits before production.
Workflow Map = full content movement
Opportunity Queue = intake and qualification before production
This queue should feed approved opportunities into the correct workflow stage.
Relationship To Content Brain Content Production Queue Specification
The Content Production Queue tracks approved content production work.
The Content Opportunity Queue tracks possible content opportunities before production.
Opportunity Queue = should this become content?
Production Queue = how do we track the content being produced?
The two queues must remain separate.
Relationship To Content Brain Content Refresh Queue Specification
Some opportunities should not become new content.
They should become refresh tasks.
If an opportunity relates to existing content that should be updated, corrected, strengthened, republished, merged, or retired, it should be promoted into the Content Refresh Queue.
Relationship To Content Brain Repurposing Queue Specification
Some opportunities should not become new content or refresh work.
They should become repurposing tasks.
If an opportunity relates to an existing approved asset that can be adapted into another format, it should be promoted into the Repurposing Queue.
Relationship To Content Brain Content Operations Dashboard Specification
The future Content Operations Dashboard may display Content Opportunity Queue metrics.
Possible dashboard signals:
new opportunities
parked opportunities
blocked opportunities
research needed
approved for production
promoted to production
promoted to refresh
promoted to repurposing
high-risk opportunities
affiliate product opportunities
search demand opportunities
AIBS education opportunities
The dashboard must remain a visibility surface, not an authority system.
Relationship To Content Brain Page Registry
This page should be added to the Content Brain Page Registry as:
Page Title: Content Brain Content Opportunity Queue Specification
Document Type: Specification
Parent Page: Content Brain Canon
Status: Draft
Migration Classification: Later Plugin Or UI
Plugin Or UI Candidate: Yes
Notes: Defines the future intake and qualification queue where signals become possible content opportunities before production, refresh, or repurposing.
Relationship To Content Brain Copy Map
This page should be added to the Content Brain Copy Map as:
Page Title: Content Brain Content Opportunity Queue Specification
Classification: Later Plugin Or UI
Reason: Repeated structured interaction, signal intake, content opportunity review, priority tracking, risk tracking, research routing, and promotion into production, refresh, or repurposing workflows.
Source Of Truth: MCR
Future Destination: mwmscontentbrain.site later
Future Use: Content opportunity intake and review screen
Plugin Or UI Later: Yes
Relationship To Other MWMS Documents
This page must align with:
Content Brain Operating Model
Content Brain Workflow Map
Content Brain Page Registry
Content Brain Copy Map
Content Brain Content Production Queue Specification
Content Brain Content Refresh Queue Specification
Content Brain Repurposing Queue Specification
Content Brain Content Operations Dashboard Specification
Content Brain Content Brief Template
Content Brain SEO Content Brief Standard
Content Brain Affiliate Funnel Support Map
Content Brain Content Production System Framework
Content Brain Content Repurposing Framework
Content Brain Content Signal Feedback Framework
Content Brain Information Gain Framework
Content Brain E E A T Content Trust Framework
MWMS MCR To Brain Copy Rule
MWMS Brain Interaction Map
MWMS Brain To Brain Request Protocol
MWMS Supabase Naming Standard
MWMS Supabase Task Schema Standard
MWMS Document Structure Standard
MWMS Page Naming Standard
MWMS AI Output Standard Full File Delivery Rule
MWMS Architecture Registry
MWMS Active Brain Status Board
Drift Protection
The system must prevent:
content opportunities entering production without review
signals being treated as approved content tasks
newsletter insights becoming content automatically
affiliate product ideas becoming content without offer status
search demand becoming content without reader value
ad hooks being treated as proven truths
experiment signals being over-interpreted
AIBS education content being created from unapproved positioning
compliance-sensitive content moving forward without risk flag
finance-heavy content work proceeding without priority discipline
the opportunity queue becoming a dumping ground
the opportunity queue replacing Research Brain
the opportunity queue replacing Affiliate Brain
the opportunity queue replacing Search Intelligence Brain
the opportunity queue replacing Ads Brain
the opportunity queue replacing Experimentation Brain
the opportunity queue replacing Compliance Brain
the opportunity queue replacing Finance Brain
the opportunity queue granting approval by itself
the opportunity queue being built as a plugin before manual workflow proves the need
mwmscontentbrain.site becoming a duplicate of MCR
Content Brain interfering with M’s active build areas
Content Brain must remain a governed content execution Brain.
The Opportunity Queue must qualify content opportunities before production.
Architectural Intent
The Content Brain Content Opportunity Queue Specification exists to make content opportunity intake visible, controlled, and scalable.
Its role is to define the future queue before implementation so that Content Brain can safely absorb signals from many Brains without becoming chaotic.
The queue should help MWMS know:
which signals could become content
where the signal came from
why the content might matter
who the content would serve
which Brain the content supports
what review is required
what risk exists
what priority it deserves
whether it should be ignored, parked, researched, drafted, reviewed, approved, published, repurposed, refreshed, or retired
The long-term intent is to support a practical operational opportunity queue on mwmscontentbrain.site while preserving MCR as the source of truth.
Final Rule
The Content Opportunity Queue qualifies signals.
It does not create authority.
If an opportunity has no source, no purpose, no audience, no review path, no owner, and no feedback destination, it should not move into production.
If the queue does not improve content decision quality, it should not be built yet.
Change Log
Version: v1.0
Date: 2026-05-24
Author: HeadOffice
Change: Initial creation of Content Brain Content Opportunity Queue Specification defining the future signal-to-content opportunity queue, including source types, required fields, status model, decision model, priority model, risk model, review rules, approval rules, promotion rules, manual-first workflow, future plugin or UI candidate logic, relationships to Content Brain Operating Model, Workflow Map, Production Queue, Refresh Queue, Repurposing Queue, Operations Dashboard, Page Registry, and Copy Map.
Change Impact Declaration
Pages Created:
Content Brain Content Opportunity Queue Specification
Pages Updated:
None
Pages Deprecated:
None
Registries Requiring Update:
Content Brain Page Registry
Content Brain Copy Map
Canon Version Update Required:
No
Change Log Entry Required:
No
END CONTENT BRAIN CONTENT OPPORTUNITY QUEUE SPECIFICATION v1.0