System: MWMS
Document Type: Framework
Authority Level: MCR Source Of Truth
Status: Draft For MCR
Version: v1.1
Primary Location: MCR
Future Operational Destination: Content Brain, AIBS Brain, Research Brain, Automation Brain, Data Brain, Client AIOS Systems
Parent Page: Content Brain
Owner: Martyn
Developer Boundary: Do Not Touch M’s Active Build Areas Unless Specifically Assigned
Source Of Truth: MCR
Last Reviewed: 2026-06-02
Source / Origin: MWMS Market Driven Social Content Production Framework v1.0 + AI Automations by Jack — Nano Banana / Gemini Visual Asset Production Block
MWMS Classification: Content Production Framework / Market-Driven Social Content System / AI Content Automation Standard / Source-Led Content Intelligence Framework / AI Visual Asset Enrichment Standard
Primary Brain: Content Brain
Supporting Brains: AIBS Brain, Research Brain, Automation Brain, Data Brain, Sales Brain, Customer Brain, Risk Brain, Compliance Brain, SIT Brain, HeadOffice Brain, Ads Brain, Video Creation Brain, Affiliate Brain
Related Pages: MWMS n8n Operating And Deployment Standard, MWMS Client Intelligence Report Automation Framework, MWMS Lead Intake Qualification And Follow-Up Automation Framework, MWMS Client Communication Automation Framework, MWMS Outbound Lead Enrichment And Cold Outreach Governance Framework, MWMS AI Dashboard Capability Framework, MWMS Supabase RAG And Vector Memory Framework, MWMS AI Agent Operations Core, MWMS AI Agent Memory And Context Framework, MWMS AI Tool Permission And Access Framework, MWMS AI Automation Security And Risk Checklist, MWMS Automation Build Planning Framework, MWMS Automation Client Demo And Handover Framework, AIBS Brain Canon, MWMS Advanced AI Capability Activation Registry
Source Evidence: The current v1.0 framework defines market-driven content production as a governed workflow that uses real market data, customer language, competitor signals, source material, and human review to generate content angles and platform-specific content. The Nano Banana / Gemini block adds a tactical visual production layer showing AI image editing for YouTube thumbnails, LinkedIn visuals, infographics, expression changes, brand-personalized pitch graphics, audit visuals, and client asset enrichment. The block emphasizes that visual intrigue can increase attention because people glance before reading, and that business pitch/audit visuals can feel stronger when enriched with a prospect’s brand assets and visual identity.
Purpose
The purpose of the MWMS Market Driven Social Content Production Framework is to define how MWMS should create, govern, automate, and improve social media content systems that are driven by real market data instead of random AI prompting.
This framework exists because most AI content automation is weak.
Weak AI content systems usually start with:
“Write me 10 social posts.”
That creates generic output.
MWMS needs a stronger model.
The absorbed course block shows a better pattern:
scrape or collect real market source data → extract useful themes → generate content angles → store content ideas → apply human review → create platform-specific content → publish or route for approval.
This is the correct direction for Content Brain.
The major lesson is:
Good AI content does not come from asking AI to guess.
Good AI content comes from feeding AI real market signals.
The v1.1 update adds a visual asset enrichment layer.
This update recognises that market-driven content is not only written content.
Market-driven content can also become:
- YouTube thumbnails
- LinkedIn visual posts
- infographics
- pitch graphics
- client audit visuals
- branded report visuals
- proposal visuals
- YouTube channel assets
- social media image assets
- client-personalized visuals
- VEO3 pre-video support assets
- ad creative test visuals
The new principle is:
Good AI visuals should not come from random image prompting.
Good AI visuals should be created from market signals, platform context, brand context, client context, and clear business purpose.
This framework turns that into an MWMS content operating standard.
Core Doctrine
The MWMS doctrine is:
Content should be created from market evidence, customer language, competitor signals, pain points, objections, questions, reviews, conversations, visual patterns, platform behaviour, and source-backed insight.
Content Brain should not become a random post generator.
Content Brain should become a system that turns real-world signals into:
- content angles
- social posts
- ad hooks
- newsletter ideas
- campaign concepts
- lead magnet ideas
- FAQ updates
- audience education
- objection-handling content
- platform-specific content assets
- client content systems
- YouTube thumbnails
- LinkedIn graphics
- pitch visuals
- branded audit visuals
- AIOS report visuals
- market-driven visual assets
The strongest content is not invented.
It is extracted, shaped, visualised, reviewed, and adapted.
Strategic Importance
This framework is strategically important because Content Brain will eventually need to work with:
- Research Brain
- Affiliate Brain
- Ads Brain
- AIBS Brain
- Customer Brain
- Sales Brain
- Newsletter Intelligence
- Client Intelligence Reports
- Experimentation Brain
- Automation Brain
- Video Creation Brain
- VEO3 creative systems
- YouTube campaign workflows
- client proposal systems
- client audit systems
The course block confirms that automated content production becomes much stronger when source material comes from the target market.
The Nano Banana / Gemini block adds that AI visual generation can make content more attention-worthy when used to create thumbnails, LinkedIn graphics, infographics, expression edits, branded pitch assets, and visual demonstrations.
This can support:
- MWMS internal content
- affiliate marketing content
- client social media packages
- AIBS content systems
- market research-based content
- competitor gap content
- review-mined content
- customer objection content
- niche authority content
- platform-specific posting systems
- YouTube thumbnail generation
- LinkedIn visual hooks
- infographic creation
- client audit personalization
- AIBS proposal enhancement
- branded client report assets
- pitch presentation assets
- ad creative testing
- visual pattern testing
- social engagement testing
This is especially useful because MWMS does not want low-quality, generic AI content.
MWMS wants content that creates business movement.
That includes both words and visuals.
Definition
Market Driven Social Content Production is the process of collecting real market source material, extracting usable signals, turning those signals into content angles, reviewing those angles, and producing platform-specific written, visual, or video-adjacent content.
MWMS Definition
An MWMS Market Driven Social Content Production System is:
A governed content workflow that uses real market data, customer language, competitor signals, source material, visual context, platform behaviour, brand context, and human review to generate content angles, platform-specific social content, and supporting visual assets that support business outcomes.
Market Driven Content Is Not Generic AI Content
Generic AI content starts with a blank prompt.
Market driven content starts with evidence.
Generic AI Content
Usually creates:
- vague posts
- bland advice
- generic hooks
- recycled tips
- no real audience insight
- weak differentiation
- no source grounding
- no strategic learning
- random visuals
- generic AI images
- platform-mismatched assets
Market Driven Content
Uses:
- websites
- reviews
- comments
- competitor pages
- customer questions
- sales calls
- support chats
- newsletters
- market reports
- forum discussions
- community conversations
- social trends
- client intelligence reports
- YouTube thumbnail patterns
- LinkedIn visual patterns
- brand assets
- client logos and design language
- campaign context
- audit findings
- proposal context
- platform-specific creative behaviour
MWMS Rule
Content should be generated from market signals whenever possible.
Visual content should be generated from market, brand, platform, and business signals whenever possible.
Core Workflow Pattern
The standard MWMS Market Driven Content workflow is:
- Target market defined
- Source data collected
- Source data cleaned
- Signals extracted
- Content angles generated
- Ideas stored
- Human review applied
- Platform-specific content generated
- Visual asset requirement defined
- AI visual asset generated or briefed
- Compliance/risk checked
- Content scheduled or routed
- Performance logged
- Learning captured
Stage 1: Target Market Defined
Before collecting content signals, define the target market.
This may include:
- niche
- audience
- buyer type
- pain points
- customer stage
- platform
- offer
- product
- client
- geography
- traffic source
- content objective
- visual style expectation
- platform visual behaviour
- desired action
Rule
Do not create content until the audience and business purpose are known.
Do not create visual assets until the platform, audience, and content purpose are known.
Stage 2: Source Data Collected
Source data may come from:
- target market websites
- competitor websites
- Google reviews
- Reddit/forum discussions
- YouTube comments
- social posts
- sales calls
- support conversations
- WhatsApp groups
- newsletters
- customer surveys
- lead forms
- search results
- blog posts
- product pages
- ad libraries
- client documents
- YouTube thumbnails
- LinkedIn post visuals
- client brand assets
- client website screenshots
- client logos
- client reports
- proposal/audit notes
- campaign creative examples
Rule
Collect source material that reflects the audience, not just the creator’s opinion.
For visual content, collect source material that reflects the platform, brand, and desired audience reaction.
Stage 3: Source Data Cleaned
Raw source data must be cleaned before content generation.
Cleaning may include:
- removing HTML
- extracting page text
- removing navigation noise
- removing duplicate text
- separating headings
- cleaning review text
- preserving source URL
- preserving source title
- preserving date
- grouping similar items
- removing irrelevant sections
- converting to structured format
- separating brand assets from market assets
- labeling competitor examples
- labeling inspiration versus source evidence
- storing image source and intended use
Rule
Clean source data creates better content angles.
Clean visual source data creates safer and stronger visual assets.
Stage 4: Signals Extracted
Signals are the useful insights inside source material.
Possible signals:
- pain points
- objections
- desires
- frustrations
- common questions
- repeated phrases
- buying triggers
- emotional language
- competitor promises
- offer gaps
- customer complaints
- customer praise
- misconceptions
- urgency signals
- trust barriers
- success stories
- failure stories
- visual intrigue patterns
- thumbnail hooks
- facial expression patterns
- layout patterns
- contrast patterns
- brand asset opportunities
- client audit visual opportunities
- infographic opportunities
- pitch personalization opportunities
Rule
Extract signals before writing content.
Extract visual signals before generating visual assets.
Stage 5: Content Angles Generated
Content angles are strategic directions for content.
Examples:
- myth-busting angle
- mistake angle
- before/after angle
- warning angle
- education angle
- objection-handling angle
- comparison angle
- customer language angle
- industry shift angle
- hidden cost angle
- checklist angle
- case study angle
- contrarian angle
- beginner guide angle
- authority-building angle
- visual intrigue angle
- branded audit angle
- client-specific pitch angle
- report visualization angle
- thumbnail curiosity angle
- platform-native visual angle
Rule
A content angle should be traceable to a market signal.
A visual angle should be traceable to a platform, brand, audience, or business signal.
Stage 6: Ideas Stored
Content ideas should be stored before production.
Possible storage:
- Airtable
- Supabase
- Google Sheets
- Content Brain database
- MCR content registry
- client content board
- approval queue
- dashboard
- visual asset library
- thumbnail test board
- client pitch asset folder
- campaign creative registry
Stored fields may include:
- idea title
- source
- signal
- angle
- platform
- target audience
- status
- priority
- owner
- compliance note
- approval state
- created date
- performance result
- visual requirement
- image prompt
- source image/reference
- brand asset used
- visual approval status
Rule
Good content ideas should become reusable assets, not disappear after one post.
Good visual assets should also become reusable assets, not one-off lost files.
Stage 7: Human Review Applied
Human review prevents weak or risky content from being published.
Review should check:
- audience fit
- brand fit
- source accuracy
- compliance risk
- tone
- claim strength
- platform suitability
- offer alignment
- originality
- usefulness
- CTA clarity
- visual accuracy
- brand asset use
- possible misleading visual edits
- competitor creative similarity
- logo/brand use
- whether AI-generated image needs disclosure or approval
- whether visual could imply false endorsement or fake association
Rule
Human review is required before client-facing or public content automation becomes trusted.
Human review is required before brand-personalized visual assets are used externally.
Stage 8: Platform-Specific Content Generated
Once approved, content can be adapted for platforms.
Platforms may include:
- YouTube Community
- X/Twitter
- TikTok
- YouTube Shorts
- blog
- newsletter
- Google Business Profile
- client social channels
- YouTube thumbnails
- YouTube banners
- LinkedIn image posts
- infographics
- proposal visuals
- report visuals
- ad creative images
Rule
Do not post the same generic format everywhere.
Adapt content to platform behavior.
Adapt visual assets to platform behavior.
Stage 9: Visual Asset Requirement Defined
Before generating an AI visual, define what the visual must do.
The visual may need to:
- stop the scroll
- create curiosity
- explain a concept
- show a process
- support a claim
- make a report easier to understand
- personalize a client audit
- improve a proposal
- support a YouTube title
- support a LinkedIn hook
- show before/after contrast
- communicate brand fit
- help a client feel the system is custom
- make a pitch feel more professional
Visual Requirement Fields
Visual Purpose:
Platform:
Audience:
Source Signal:
Core Message:
Visual Style:
Brand Assets Needed:
Reference Assets:
Risk Level:
Approval Required:
Output Size / Format:
Destination:
Rule
Do not generate visuals just because the tool can.
Generate visuals only when they support the content purpose.
Stage 10: AI Visual Asset Generated Or Briefed
AI visual generation may use tools such as Gemini / Nano Banana-style image editing, image generation tools, Photoshop, Canva, Ideogram, Fal, Bria, VEO3 support prompts, or other approved design tools.
Possible outputs:
- YouTube thumbnails
- thumbnail variations
- expression variations
- LinkedIn visuals
- infographics
- pitch graphics
- client audit graphics
- proposal visuals
- branded mockups
- social post graphics
- YouTube transition assets
- campaign creative concepts
- visual pattern tests
Rule
AI should create visual assets from approved signals, brand context, and platform purpose.
AI should not create random visuals disconnected from strategy.
Stage 11: Compliance / Risk Checked
Content may require compliance review when it includes:
- health claims
- financial claims
- income claims
- legal claims
- competitor comparisons
- performance promises
- client results
- testimonials
- sensitive topics
- affiliate offers
- paid ads
- regulated industries
- manipulated facial expressions
- altered person likeness
- client logos
- brand assets
- competitor-inspired layouts
- implied endorsements
- fake screenshots
- fake transactions
- AI-generated evidence visuals
- before/after visuals
- public-facing audit visuals
Rule
Content that could create platform, legal, or reputation risk must be reviewed before publishing.
AI-generated visual assets that could mislead, copy, imply endorsement, or misuse brand assets must be reviewed before use.
Stage 12: Content Scheduled Or Routed
Content may be:
- scheduled
- posted manually
- sent for approval
- routed to client
- added to campaign queue
- converted into ad hook
- converted into email
- added to newsletter
- turned into video script
- added to content calendar
- sent to thumbnail testing
- sent to client proposal
- sent to report design
- saved to visual asset library
- sent to VEO3 creative workflow
- routed to designer/human review
Rule
Content output should have a destination.
Visual output should also have a destination, status, and owner.
Stage 13: Performance Logged
Content performance should be logged where possible.
Metrics may include:
- impressions
- clicks
- comments
- shares
- saves
- watch time
- CTR
- lead capture
- engagement rate
- replies
- qualified conversations
- conversions
- follower growth
- client feedback
- thumbnail CTR
- visual engagement lift
- LinkedIn dwell/engagement signal
- visual test winner
- proposal/client response feedback
- report usefulness feedback
Rule
Content Brain should learn from performance, not just produce volume.
Visual assets should also be tested and improved when performance data exists.
Stage 14: Learning Captured
Learning may include:
- which angles perform
- which audience signals matter
- which platforms respond
- which topics create leads
- which formats work
- which claims create risk
- which sources are most useful
- which content should be repurposed
- which content should be retired
- which thumbnail patterns improve CTR
- which LinkedIn visuals increase attention
- which infographics improve clarity
- which brand-personalized visuals improve pitch response
- which AI visual styles feel too generic
- which visual edits create risk
- which visual assets should become templates
Rule
Every content cycle should improve the next cycle.
Every visual asset cycle should improve the next visual cycle.
Source Types
MWMS recognises the following source types for market driven content.
1. Target Market Websites
Useful for understanding:
- how the market describes itself
- what services exist
- common language
- competitor positioning
- niche terminology
- buyer expectations
Rule
Website data is useful, but it must be cleaned and interpreted carefully.
2. Competitor Websites
Useful for:
- positioning analysis
- offer comparison
- content gaps
- pricing/packaging clues
- promise patterns
- trust elements
- market expectations
Rule
Competitor content should inspire market understanding, not be copied.
3. Customer Reviews
Useful for:
- pain points
- praise
- complaints
- emotional language
- decision triggers
- trust signals
- objections
- content hooks
Rule
Reviews are one of the strongest sources of customer language.
4. Comments And Community Discussions
Useful for:
- real questions
- confusion
- objections
- objections in natural language
- trending problems
- frustration points
- content topics
Rule
Community language should be mined for insight, not copied without context.
5. Sales Calls And Support Conversations
Useful for:
- objections
- buying triggers
- repeated questions
- offer confusion
- onboarding gaps
- customer expectations
Rule
Sales and support conversations should feed content strategy when privacy rules allow.
6. Lead Intake Forms
Useful for:
- stated problems
- desired outcomes
- budget language
- readiness signals
- content needs
- buyer education gaps
Rule
Lead form answers can become content intelligence when consent and privacy rules are respected.
7. Client Intelligence Reports
Useful for:
- competitor changes
- review themes
- customer complaints
- opportunity gaps
- content recommendations
- FAQ improvements
Rule
Client intelligence should feed content planning.
8. Visual Platform Patterns
Visual platform patterns include examples of what catches attention on a specific platform.
Useful sources include:
- YouTube thumbnails
- LinkedIn image posts
- Instagram carousels
- Facebook post visuals
- TikTok/Shorts cover frames
- ad creative examples
- infographics
- visual hooks used by outlier content
These may be used to understand:
- layout
- contrast
- curiosity
- facial expression
- text placement
- visual simplicity
- emotional pull
- visual hierarchy
- platform-native style
Rule
Visual patterns may inspire structure, but they must not be copied directly.
9. Client Brand Assets
Client brand assets may include:
- logos
- website screenshots
- app screenshots
- product images
- colours
- fonts
- icons
- design language
- marketing pages
- pitch deck elements
- social images
These are useful for:
- audit visuals
- proposal visuals
- branded mockups
- report graphics
- client-personalized pitch assets
- AIOS interface concepts
Rule
Client brand assets should be used only for approved, ethical, client-relevant purposes.
Do not imply endorsement, partnership, or official approval where none exists.
Content Angle Standard
Each content angle should have a defined structure.
Angle Title:
Source Signal:
Audience:
Pain / Desire:
Core Insight:
Platform Fit:
Content Type:
Claim Risk:
CTA Type:
Evidence / Source:
Visual Asset Needed:
Visual Signal / Reference:
Approval Status:
Rule
If an angle has no source signal, it may be generic.
If a visual has no visual purpose, it may be decorative noise.
Content Idea Statuses
Content ideas should move through clear statuses.
Possible statuses:
- Raw Signal
- Angle Generated
- Needs Review
- Approved
- Rejected
- Needs Rewrite
- Ready For Platform Adaptation
- Visual Asset Needed
- Visual Draft Created
- Visual Needs Review
- Visual Approved
- Scheduled
- Published
- Repurposed
- Archived
- High Performer
- Low Performer
- Compliance Review Required
Rule
Content production should have workflow states, not loose lists.
Visual asset production should also have workflow states.
Human Review Rules
Human review is required before content is published when:
- content is client-facing
- content uses scraped source material
- content references competitors
- content includes strong claims
- content is for paid ads
- content is compliance-sensitive
- content uses testimonials
- content is health/finance/legal-related
- content could affect brand trust
- content is part of a new system
- visual assets use client logos
- visual assets use altered likenesses
- visual assets are competitor-inspired
- visual assets imply brand relationship
- visual assets show fake screenshots or fake transactions
- AI-generated visuals are used in client reports, proposals, or ads
Rule
Automation can draft content, but publishing authority must be governed.
AI can generate visual assets, but public or client-facing use must be reviewed.
Platform Adaptation Rules
Different platforms require different formats.
Best for:
- professional insights
- authority content
- case studies
- market observations
- lessons learned
- problem/solution posts
- visual explainers
- workflow graphics
- pitch-style visuals
- infographic-style posts
Rule
LinkedIn should sound useful, clear, and professionally credible.
LinkedIn visuals should create intrigue without becoming clickbait or confusing.
Best for:
- community-style posts
- local business content
- story-based content
- simple tips
- engagement prompts
- easy-to-understand visuals
- community-friendly graphics
Rule
Facebook content should be accessible and conversation-friendly.
Best for:
- visual hooks
- carousel ideas
- short captions
- educational snippets
- brand presence
- infographics
- before/after style concepts where compliant
- visual identity building
Rule
Instagram should be visual-first, not text-dump first.
YouTube Shorts / TikTok
Best for:
- hooks
- fast education
- pattern interrupts
- short story beats
- myth/mistake/warning formats
- visual curiosity
- strong first-frame concepts
Rule
Short-form video content needs hook-first structure.
YouTube Thumbnails
Best for:
- curiosity
- contrast
- emotional expression
- simple visual idea
- clear title support
- outlier-inspired structure
- audience-relevant promise
- thumbnail/title alignment
Thumbnail visuals may use AI to:
- test expressions
- test layouts
- create background concepts
- adapt visual metaphors
- create variations
- create brand-consistent thumbnails
- support VEO3 campaigns
Rule
YouTube thumbnails should create curiosity without misleading the viewer.
AI-edited likeness, expression, or scene changes must not create deceptive claims.
Newsletter
Best for:
- deeper insight
- curated analysis
- client education
- trend commentary
- trust building
- simple supporting visuals
- chart/infographic explanations
Rule
Newsletter content should provide more depth than social posts.
Client Reports And Proposals
Best for:
- decision support
- simplified insight
- visual summaries
- branded mockups
- audit graphics
- proposal diagrams
- competitor comparison visuals
- AIOS value proof visuals
Rule
Client reports and proposals should use visuals to improve clarity and perceived value, not to decorate weak substance.
Content Repurposing Rule
One strong market signal can become multiple assets.
Example:
A repeated customer complaint can become:
- LinkedIn post
- Facebook post
- Instagram carousel
- YouTube Short hook
- email section
- FAQ update
- sales objection note
- ad angle
- blog outline
- infographic
- YouTube thumbnail concept
- client report visual
- proposal proof point
- VEO3 pre-video visual direction
Rule
Repurpose strong signals across formats, but adapt each format properly.
Repurpose strong visual ideas across formats only when they remain truthful, relevant, and platform-appropriate.
AI Content Generation Rules
AI may generate content, but it must be guided by:
- source signal
- audience
- platform
- tone
- offer
- CTA
- claim restrictions
- compliance boundaries
- brand voice
- approval status
- visual purpose
- platform visual behaviour
- brand asset permission
- source evidence
- destination
AI must not:
- invent customer quotes
- copy competitor text
- make unsupported claims
- exaggerate results
- create fake case studies
- ignore platform context
- use private source material publicly
- publish without approval where required
- copy competitor visuals too closely
- create fake endorsements
- misuse client logos
- misrepresent screenshots
- imply a brand relationship that does not exist
- turn AI-generated visuals into fake evidence
Rule
AI should convert approved signals into content, not invent reality.
AI should convert approved context into visuals, not fabricate proof.
AI Visual Asset Enrichment Rule
AI visual asset enrichment is the controlled use of AI image generation or editing tools to strengthen content, reports, pitches, proposals, thumbnails, and social assets.
This may include:
- thumbnail concepts
- thumbnail variations
- expression changes
- background changes
- LinkedIn graphics
- infographics
- pitch visuals
- brand-personalized client visuals
- report graphics
- proposal mockups
- app/interface mockups
- social post images
- YouTube transition visuals
- campaign creative concepts
The Nano Banana / Gemini block shows that AI image tools can now take reference images, brand assets, thumbnails, or app visuals and create higher-quality, more personalized, more visually engaging creative assets.
MWMS Rule
AI visual tools should be used to enrich market-driven content, not replace strategic thinking.
Visual asset enrichment must remain:
- purpose-led
- source-aware
- platform-aware
- brand-aware
- approval-controlled
- compliance-reviewed where needed
- performance-tested where possible
Visual Asset Enrichment Use Cases
1. YouTube Thumbnail Enhancement
Use AI visual tools to generate thumbnail drafts and variations.
May include:
- stronger expression
- clearer contrast
- simplified layout
- title-aligned visual metaphor
- curiosity-building background
- outlier-inspired structure
- brand-consistent design
- VEO3 campaign thumbnail support
Rule
Thumbnail inspiration may come from outliers, but the final creative must not directly copy another creator’s asset.
2. LinkedIn Visual Hook Creation
Use AI visuals to create LinkedIn graphics that make a post easier to notice.
May include:
- workflow diagram
- infographic
- before/after visual
- concept graphic
- founder-style visual
- brand-coded visual
- simple visual metaphor
Rule
LinkedIn visuals should clarify and intrigue.
They should not be random AI art.
3. Infographic Generation
Use AI visuals to turn concepts into visual explanations.
May include:
- timeline
- process map
- comparison
- checklist
- framework diagram
- market explanation
- customer journey
- AIOS system map
Rule
Infographics must be checked for accuracy before use.
AI image tools often make text, labels, or logic errors.
4. Client Pitch And Audit Visuals
Use AI visuals to personalize client-facing audits or proposals.
May include:
- client-branded audit graphics
- mock AIOS dashboard concepts
- app-style mockups
- report screenshots
- branded workflow graphics
- competitor gap visuals
- proposal diagrams
Rule
Client personalization should increase relevance and perceived care.
It must not imply that a client has approved, endorsed, or already used a system unless true.
5. Branded Report Visuals
Use AI visuals to support client reports.
May include:
- competitor report graphics
- review sentiment visuals
- lead flow visuals
- AIOS activity visuals
- customer insight diagrams
- monthly value proof visuals
Rule
Report visuals must support the data.
They must not make weak or uncertain findings look stronger than they are.
6. Campaign Creative Testing
Use AI visuals to test creative directions quickly.
May include:
- ad angle visuals
- hero image concepts
- thumbnail variations
- first-frame concepts
- social image variations
- VEO3 pre-video visual prompts
Rule
AI visual creative may be used for testing, but ad/public use requires claim and platform compliance review.
Visual Asset Risk Rules
AI-generated visuals require risk review when they involve:
- real people
- facial expression changes
- altered likeness
- competitor-inspired thumbnails
- brand logos
- client logos
- fake app transactions
- financial amounts
- testimonials
- before/after claims
- health/finance/income claims
- screenshots
- client dashboards
- public ads
- political or sensitive topics
- implied endorsement
- fake evidence
- hidden AI manipulation
Rule
AI-generated visual assets must not mislead the viewer about what is real, proven, endorsed, or approved.
Visual Asset Approval Standard
Before using an AI-generated visual publicly or with a client, check:
Visual Purpose:
Source / Reference Used:
Brand Assets Used:
Client / Competitor Assets Used:
Person Or Likeness Used:
Claim Implied:
Risk Level:
Platform:
Destination:
Approval Required:
Reviewer:
Status: Draft / Approved / Rejected / Needs Revision
Rule
High-risk visuals require approval before public use.
Content Storage Schema
A reusable content database may include:
Content ID:
Source Type:
Source Title:
Source URL:
Source Date:
Signal Extracted:
Audience:
Pain / Desire:
Angle:
Platform:
Draft Content:
CTA:
Claim Risk:
Compliance Status:
Human Review Status:
Visual Asset Needed:
Visual Prompt / Brief:
Visual Source Reference:
Brand Assets Used:
Visual Risk Level:
Visual Approval Status:
Publishing Status:
Published URL:
Performance Metrics:
Repurpose Notes:
Owner:
Created Date:
Last Updated:
Rule
Content systems should preserve source, status, performance, and visual asset history.
Automation Pattern
The original course block points toward this automation pattern:
- Collect target market websites
- Scrape/extract text
- Clean text
- Generate content angles
- Store angles in Airtable/database
- Human reviews and approves
- Generate platform-specific posts
- Store or schedule outputs
MWMS Upgrade
For MWMS, the stronger version is:
- Define audience and outcome
- Collect approved source signals
- Clean and tag sources
- Extract signals
- Generate angles
- Score angles by relevance and risk
- Identify visual asset need
- Generate or brief visual asset
- Human review
- Produce platform-specific content
- Route to schedule/publish/approval
- Log performance
- Feed learning back into Content Brain
Rule
Automation should support the content strategy, not replace it.
Visual automation should support the content strategy, not create random decorative output.
Content Approval Queue
Content should pass through an approval queue where required.
Approval queue fields:
- content title
- source signal
- platform
- draft
- claim risk
- compliance flag
- reviewer
- status
- requested edits
- approval date
- publishing destination
- visual asset needed
- visual draft
- visual risk
- visual approval status
Rule
Client-facing content should not bypass approval unless the system is mature and low-risk.
Client-facing visuals should not bypass approval unless the system is mature and low-risk.
Content Performance Feedback Loop
Content performance should improve future creation.
Feedback should answer:
- Which angle performed?
- Which platform worked?
- Which source signal was strong?
- Which hook got attention?
- Which CTA worked?
- Did content generate leads?
- Did content support sales?
- Did content create comments/questions?
- Did content need compliance correction?
- Which visual improved performance?
- Which thumbnail style improved CTR?
- Which infographic clarified the message?
- Which visual style felt off-brand?
- Which client pitch visual increased response?
- Which AI visual created risk or confusion?
Rule
Content Brain must learn from outcomes, not just produce more content.
Visual performance should feed creative learning.
Client Package Models
This framework can support several AIBS or Content Brain packages.
Package 1: Market-Driven Social Content Engine
Client receives:
- source-led angle generation
- approved content ideas
- platform-specific posts
- content calendar
- review queue
- optional visual asset drafts
Package 2: Review-Mined Content System
Client reviews are mined for:
- customer language
- pain points
- praise
- objections
- social post ideas
- FAQ content
- ad angles
- infographic ideas
- customer language visuals
Package 3: Competitor Gap Content System
Competitor pages/reviews are analysed to find:
- content gaps
- positioning opportunities
- customer complaints
- educational angles
- comparison topics
- competitor gap visuals
- positioning graphics
Package 4: Sales Conversation Content Engine
Sales calls and support conversations are mined for:
- objections
- FAQs
- content ideas
- follow-up posts
- sales enablement content
- proposal visuals
- sales objection graphics
Package 5: Content Intelligence Dashboard
Dashboard shows:
- source signals
- approved angles
- draft posts
- platform status
- visual asset status
- publishing schedule
- performance feedback
Package 6: Visual Asset Enrichment Add-On
Client receives:
- social post visuals
- LinkedIn graphics
- thumbnail drafts
- branded audit visuals
- proposal visuals
- report graphics
- AIOS value proof graphics
Rule
Visual Asset Enrichment should be an add-on to content intelligence, not a standalone shiny-object product unless there is clear demand.
Minimum Viable Content Product
Recommended MVP:
Market Signal To Social Post Engine
Inputs:
- 5–10 target market pages or review sources
- audience
- offer
- platform focus
- brand tone
- approval rule
Outputs:
- extracted signals
- 20 content angles
- approved/rejected status
- platform-specific post drafts
- simple content calendar
Why this is strong:
- simple
- source-backed
- visible value
- can be used internally or sold to clients
- can later connect to scheduling tools
v1.1 Optional Visual Add-On
The visual add-on may include:
- 5 thumbnail or social image concepts
- 3 LinkedIn image drafts
- 1 infographic concept
- 1 branded audit/pitch visual
- visual approval status
MWMS Rule
Start with signal extraction and reviewed drafts before fully automated posting.
Start with reviewed visual drafts before fully automated visual publishing.
Compliance And Risk Rules
Content requires risk review when it includes:
- health claims
- income claims
- financial claims
- legal advice
- medical advice
- affiliate offers
- product performance claims
- before/after claims
- customer testimonials
- competitor comparisons
- scraped content
- private customer data
- regulated industry claims
- AI-edited people
- client logos
- competitor-inspired visuals
- fake screenshots
- implied endorsements
- generated financial amounts
- altered facial expressions
- AI-generated thumbnails for paid ads
Rule
Content automation must not publish high-risk claims without review.
Visual automation must not publish high-risk or potentially misleading assets without review.
Scraping And Source Use Rules
When source material is scraped or collected:
- record source URL
- record date
- avoid copying wording
- avoid private sources without permission
- respect platform rules
- use source as insight, not theft
- avoid exposing sensitive data
- separate source evidence from generated content
- label visual references as inspiration, not assets to copy
- preserve client asset permission notes where relevant
Rule
Use sources to learn, not to plagiarize.
Use visual references to understand patterns, not to copy protected creative.
Brand Voice Rule
Market data should inform content, but brand voice must still control final output.
Brand voice should define:
- tone
- formality
- humor level
- directness
- forbidden phrases
- claim style
- CTA style
- audience relationship
Rule
Source data provides substance.
Brand voice provides expression.
Brand Visual Rule
Brand context should guide visual output.
Brand visual context may include:
- colour palette
- logo rules
- typography
- design tone
- image style
- level of polish
- platform-safe zones
- white-space preference
- thumbnail/banner standards
- client brand standards
Rule
Source data provides substance.
Brand identity provides visual expression.
Application To Content Brain
Content Brain owns this framework.
Content Brain should use it to build:
- source-led content systems
- client content engines
- content approval workflows
- platform adaptation rules
- content performance feedback
- content signal libraries
- visual asset enrichment workflows
- thumbnail testing workflows
- social visual review queues
- branded visual asset libraries
Content Brain Rule
Content Brain should produce content from signals, not guesses.
Content Brain should produce visuals from purpose, platform, and context — not random AI art.
Application To Research Brain
Research Brain supports market source quality.
Research Brain should identify:
- best sources
- strongest signals
- competitor gaps
- customer language
- trend evidence
- source limitations
- visual pattern evidence
- platform visual norms
- competitor visual gaps
- client brand opportunities
Research Rule
Research Brain improves content by improving source quality.
Research Brain improves visual content by improving visual signal quality.
Application To AIBS Brain
AIBS Brain may package this as a client system.
AIBS packages should focus on:
- consistent content output
- better market fit
- customer-language content
- reduced content workload
- approval workflow
- performance learning
- visual asset enrichment
- pitch/audit personalization
- content intelligence visibility
- client report/proposal improvement
AIBS Rule
Sell market-driven content production, not generic AI posting.
Sell visual asset enrichment as part of visible client value, not as a random design gimmick.
Application To Automation Brain
Automation Brain builds workflows for:
- scraping
- cleaning
- signal extraction
- angle generation
- storage
- review queue
- platform drafting
- scheduling integration
- performance logging
- visual prompt generation
- visual asset queueing
- image tool routing
- visual approval workflow
- visual asset storage
Automation Rule
Do not automate publishing before review and risk controls are ready.
Do not automate visual generation into public/client use before review and risk controls are ready.
Application To Data Brain
Data Brain owns content storage.
Data Brain should define:
- content database
- source metadata
- angle fields
- status fields
- platform fields
- performance fields
- approval fields
- visual asset fields
- visual source/reference fields
- visual approval fields
- visual performance fields
Data Rule
A content engine needs structured content data.
A visual content engine needs structured visual asset metadata.
Application To Sales Brain
Sales Brain can use content signals for:
- objection-handling posts
- lead nurture content
- sales enablement content
- case study ideas
- follow-up content
- pitch visuals
- proposal visuals
- audit visuals
- client-personalized proof assets
Sales Rule
Content should support the sales journey.
Visual assets should improve clarity, trust, and perceived relevance during the sales journey.
Application To Customer Brain
Customer Brain can feed:
- support questions
- customer complaints
- customer praise
- onboarding confusion
- FAQ gaps
- customer language
- visual explanation needs
- customer education gaps
Customer Rule
Repeated customer questions should become content assets.
Repeated customer confusion may also become visual explanation assets.
Application To Ads Brain
Ads Brain may use this framework for:
- ad hook visuals
- YouTube thumbnail concepts
- first-frame ideas
- ad creative variations
- visual angle testing
- compliance-safe creative concepts
- VEO3 pre-video support visuals
Ads Brain Rule
Ad visuals must be tested against platform compliance, claim safety, and audience clarity.
Application To Video Creation Brain
Video Creation Brain may use this framework for:
- YouTube thumbnails
- video title/thumbnail alignment
- VEO3 image prompts
- pre-video visual planning
- channel asset concepts
- transition assets
- short-form first-frame concepts
Video Creation Brain Rule
Video visuals must support the hook, message, and platform behaviour.
Application To Affiliate Brain
Affiliate Brain may use this framework for:
- affiliate ad thumbnails
- offer angle visuals
- VSL click-support visuals
- landing page visual concepts
- product-safe creative directions
- compliance-safe campaign visuals
Affiliate Brain Rule
Affiliate visuals must avoid exaggerated, misleading, or non-compliant product claims.
Application To Risk And Compliance Brain
Risk and Compliance Brain must review content involving:
- regulated claims
- affiliate offers
- product claims
- testimonials
- competitor comparisons
- scraped source material
- private data
- sensitive topics
- AI-edited likenesses
- client/competitor logos
- fake screenshots
- fake transactions
- misleading visuals
- AI-generated evidence-like assets
Risk Rule
Content automation must be compliance-aware before public publishing.
Visual automation must be compliance-aware before public, client-facing, or paid use.
Application To SIT Brain
SIT Brain should test content workflows.
SIT should test:
- source extraction accuracy
- duplicate removal
- AI angle quality
- approval routing
- platform formatting
- compliance flags
- publishing path
- performance logging
- wrong-source handling
- private data leakage
- visual source tracking
- image prompt quality
- visual approval flow
- misleading visual risk
- brand asset misuse
- visual output destination
- thumbnail/platform formatting
SIT Rule
Content workflow tests should include quality, source, risk, and publishing checks.
Visual workflow tests should include source, brand, risk, approval, and platform checks.
Related AI Employee Capabilities
Market Signal Extractor
Extracts pains, desires, objections, questions, themes, and language from source data.
Content Angle Generator
Turns market signals into reusable content angles.
Content Risk Reviewer
Checks claims, source use, compliance risk, and brand safety.
Platform Adaptation Agent
Turns approved angles into platform-specific content.
Content Approval Coordinator
Routes drafts through review and status tracking.
Content Performance Analyst
Reviews results and identifies winning angles.
Content Repurposing Agent
Turns strong signals into multiple content formats.
Visual Signal Extractor
Identifies useful visual patterns from thumbnails, LinkedIn posts, infographics, brand assets, reports, and platform examples.
AI Visual Asset Prompt Builder
Turns approved content angles and visual requirements into image generation/editing prompts.
Visual Asset Risk Reviewer
Checks generated visuals for misleading edits, brand misuse, competitor copying, false endorsements, claim risk, and platform suitability.
Thumbnail Testing Analyst
Tracks thumbnail concepts, visual hooks, CTR, and learnings for YouTube/video workflows.
Client Pitch Visual Builder
Creates branded audit, proposal, and report visual drafts from approved client context.
Future Expansion
This framework may later produce:
- MWMS Content Signal Library Standard
- MWMS Market Signal Extraction Framework
- MWMS Social Content Approval Workflow Standard
- MWMS Platform-Specific Content Adaptation Standard
- MWMS Review-Mined Content System Framework
- MWMS Competitor Gap Content Framework
- MWMS Content Performance Feedback Loop Standard
- MWMS AI Visual Asset Enrichment Standard
- MWMS YouTube Thumbnail Testing Framework
- MWMS Client Pitch Visual Asset Framework
- MWMS AI Infographic Generation Checklist
- MWMS Brand-Safe AI Visual Governance Standard
These should be created only when needed.
Strategic Summary
This block is valuable because it confirms an important MWMS content principle:
AI should not guess what the market wants.
AI should extract what the market is already saying.
The Nano Banana / Gemini visual block adds a secondary but useful principle:
AI should not randomly generate visuals.
AI should enrich content with visuals that are tied to audience attention, platform behaviour, brand context, client relevance, and business purpose.
The strongest content systems will come from:
- customer reviews
- competitor gaps
- support questions
- sales objections
- market websites
- community conversations
- client intelligence reports
- lead intake data
- YouTube thumbnail patterns
- LinkedIn visual patterns
- brand assets
- audit/proposal context
- client report context
This gives Content Brain a stronger direction.
Content Brain should not be a content factory.
Content Brain should become a market intelligence-to-content system.
The v1.1 update expands that into:
Market intelligence → content angles → platform content → visual assets → performance learning.
That means better content, better client value, better affiliate angles, better ad hooks, better newsletters, stronger thumbnails, stronger pitch visuals, better report visuals, and better sales support.
Final Standard
The MWMS standard is:
Create content from market signals, not blank prompts.
Extract pains, desires, objections, questions, and customer language from real sources.
Turn signals into angles.
Review the angles.
Adapt by platform.
Create visuals from purpose, platform, brand, and source context.
Review visuals before client-facing, public, or paid use.
Track performance.
Feed learning back into Content Brain.
Market-driven content is not random posting.
Market-driven visual content is not random AI art.
It is content intelligence expressed through words, images, layouts, thumbnails, reports, and platform-specific creative assets.
Change Log
Version: v1.1
Date: 2026-06-02
Author: MWMS HeadOffice
Change:
Updated the MWMS Market Driven Social Content Production Framework using the AI Automations by Jack — Nano Banana / Gemini Visual Asset Production Block.
Preserved the existing v1.0 framework structure and expanded it to include AI visual asset enrichment as a tactical layer under Content Brain and AIBS content/report/pitch systems.
Added visual content scope across:
- YouTube thumbnails
- LinkedIn visual posts
- infographics
- pitch graphics
- client audit visuals
- branded report visuals
- proposal visuals
- social media image assets
- client-personalized visuals
- VEO3 pre-video support assets
- ad creative test visuals
Expanded Purpose, Core Doctrine, Strategic Importance, Definition, Market Driven Content Is Not Generic AI Content, Core Workflow Pattern, Target Market Definition, Source Data Collection, Signal Extraction, Content Angles, Ideas Stored, Human Review, Platform-Specific Content, Compliance/Risk, Routing, Performance Logging, and Learning Capture.
Added new stages:
- Visual Asset Requirement Defined
- AI Visual Asset Generated Or Briefed
Added new source types:
- Visual Platform Patterns
- Client Brand Assets
Expanded Content Angle Standard, Content Idea Statuses, Human Review Rules, Platform Adaptation Rules, Content Repurposing Rule, AI Content Generation Rules, Content Storage Schema, Automation Pattern, Content Approval Queue, and Content Performance Feedback Loop.
Added new sections:
- AI Visual Asset Enrichment Rule
- Visual Asset Enrichment Use Cases
- Visual Asset Risk Rules
- Visual Asset Approval Standard
- Brand Visual Rule
Added visual asset use cases for:
- YouTube Thumbnail Enhancement
- LinkedIn Visual Hook Creation
- Infographic Generation
- Client Pitch And Audit Visuals
- Branded Report Visuals
- Campaign Creative Testing
Expanded Client Package Models to include Visual Asset Enrichment Add-On.
Expanded Minimum Viable Content Product with optional visual add-on.
Expanded Compliance And Risk Rules, Scraping And Source Use Rules, and Brand Voice Rule to include AI visual risks.
Expanded Application To Content Brain, Research Brain, AIBS Brain, Automation Brain, Data Brain, Sales Brain, Customer Brain, Risk And Compliance Brain, and SIT Brain.
Added new application sections for:
- Ads Brain
- Video Creation Brain
- Affiliate Brain
Added related AI Employee capabilities:
- Visual Signal Extractor
- AI Visual Asset Prompt Builder
- Visual Asset Risk Reviewer
- Thumbnail Testing Analyst
- Client Pitch Visual Builder
Added future expansion pages including:
- MWMS AI Visual Asset Enrichment Standard
- MWMS YouTube Thumbnail Testing Framework
- MWMS Client Pitch Visual Asset Framework
- MWMS AI Infographic Generation Checklist
- MWMS Brand-Safe AI Visual Governance Standard
Purpose of update:
To absorb the useful tactical value from the Nano Banana / Gemini visual production lesson without creating a tool-specific MCR page, and to formally add AI visual asset enrichment into Content Brain as a governed, source-aware, platform-aware, brand-aware production layer for thumbnails, LinkedIn visuals, infographics, client pitch assets, report visuals, proposal visuals, and AIBS content packages.
Version: v1.0
Date: 2026-06-01
Author: MWMS HeadOffice
Change:
Created the MWMS Market Driven Social Content Production Framework from the AI Automations by Jack social media production engine, market website scraping, content angle generation, and platform-specific content automation block.
Captured the core workflow pattern: target market defined → source data collected → source data cleaned → signals extracted → content angles generated → ideas stored → human review applied → platform-specific content generated → compliance/risk checked → content scheduled or routed → performance logged → learning captured.
Defined market-driven social content production as a governed content workflow that uses real market data, customer language, competitor signals, source material, and human review to generate content angles and platform-specific social content that supports business outcomes.
Added source types including target market websites, competitor websites, customer reviews, comments/community discussions, sales calls/support conversations, lead intake forms, and client intelligence reports.
Added Content Angle Standard, Content Idea Statuses, Human Review Rules, Platform Adaptation Rules, Content Repurposing Rule, AI Content Generation Rules, Content Storage Schema, Automation Pattern, Content Approval Queue, and Content Performance Feedback Loop.
Added client package models including Market-Driven Social Content Engine, Review-Mined Content System, Competitor Gap Content System, Sales Conversation Content Engine, and Content Intelligence Dashboard.
Added Minimum Viable Content Product recommendation: Market Signal To Social Post Engine.
Added compliance and risk rules, scraping and source use rules, brand voice rule, and mapped responsibilities across Content Brain, Research Brain, AIBS Brain, Automation Brain, Data Brain, Sales Brain, Customer Brain, Risk Brain, Compliance Brain, and SIT Brain.
Added related AI Employee capabilities: Market Signal Extractor, Content Angle Generator, Content Risk Reviewer, Platform Adaptation Agent, Content Approval Coordinator, Content Performance Analyst, and Content Repurposing Agent.
Purpose of creation:
To establish market-driven content production as a governed MWMS Content Brain capability and future AIBS client package, ensuring social content is generated from real audience signals, customer language, competitor gaps, reviews, sales/support conversations, and source-backed insight rather than generic AI prompting.
END — MWMS MARKET DRIVEN SOCIAL CONTENT PRODUCTION FRAMEWORK v1.1