System: MWMS
Document Type: Framework
Authority Level: MCR Source Of Truth
Status: Draft For MCR
Primary Location: MCR
Future Operational Destination: Content Brain, HeadOffice Brain, AI Business Systems Brain, Research Brain, Offer Brain, Creative Brain, Sales Brain, Affiliate Brain, Future AIBS Client Systems
Parent Page: Content Brain Canon
Owner: Martyn
Developer Boundary: No Development Action Authorized By This Page
Source Of Truth: MCR
Purpose
The purpose of this document is to define the MWMS Content Intelligence Scanner Framework.
This framework establishes how MWMS scans existing content libraries, folders, transcripts, posts, emails, newsletters, sales assets, course material, articles, scripts, and client content archives to identify reusable content intelligence.
MWMS must not treat existing content as dead material.
Old content may contain:
strong angles
customer language
founder beliefs
reusable frameworks
offer explanations
objection handling
story assets
proof points
sales arguments
email ideas
social post ideas
lead magnet ideas
webinar ideas
ad hooks
VEO3 script ideas
AI Employee training material
The purpose of the Content Intelligence Scanner is to turn existing content into structured, reusable intelligence for the MWMS ecosystem.
This framework exists because many businesses already have valuable content, but that value is usually scattered across folders, platforms, documents, emails, and transcripts.
Without a scanning framework, MWMS risks:
missing useful existing assets
creating new content unnecessarily
duplicating old ideas
ignoring high-value founder language
losing strong angles inside old files
failing to reuse proven messages
building client systems from incomplete content
creating generic AI content when better source material already exists
The Content Intelligence Scanner Framework turns content archives into strategic source material.
Scope
This framework applies to all MWMS content scanning, archive review, source material review, client content intake, course absorption support, and content opportunity extraction.
This includes:
Content Brain
HeadOffice Brain
AI Business Systems Brain
Research Brain
Offer Brain
Creative Brain
Sales Brain
Affiliate Brain
Ads Brain
Customer Brain
Conversion Brain
Course Absorption System
Newsletter Intelligence
Future AIBS Client Systems
This framework applies to scanning:
blog posts
emails
newsletters
social posts
YouTube scripts
VEO3 scripts
podcast transcripts
course transcripts
sales pages
landing pages
webinar scripts
lead magnets
client documents
workshop notes
voice memos
support replies
testimonials
case studies
old campaign files
content folders
This framework does not authorize technical development, automation wiring, file-system tooling, plugin changes, Supabase changes, WordPress changes, or M developer action.
Core Definition
Content Intelligence Scanning is the process of reviewing existing content and extracting reusable strategic signals.
The scanner does not summarize content for passive reading.
It identifies what the content can do for MWMS.
Content intelligence may include:
angle opportunities
content themes
belief shifts
buyer objections
customer phrases
proof points
stories
frameworks
offer insights
sales arguments
educational sequences
repurposing opportunities
asset creation opportunities
AI Employee training value
context library updates
Core Principle
The core principle of this framework is:
Existing content should be scanned for reusable business intelligence before creating new content from scratch.
AI should not immediately generate new ideas when useful source material already exists.
The first question is not:
What new content can we create?
The first question is:
What intelligence already exists that MWMS can reuse, improve, route, or turn into assets?
Content Scanner Objectives
The Content Intelligence Scanner may be used to achieve several objectives.
Angle Discovery
Identify strong angles hidden inside existing content.
Examples:
contrarian claims
buyer frustrations
belief-shift ideas
unexpected lessons
strong opening lines
category villains
Offer Support
Identify content that can support an offer.
Examples:
explain the problem
handle objections
show methodology
build trust
support a sales page
prepare a buyer for a webinar
Content Repurposing
Identify existing material that can become new formats.
Examples:
blog post to email sequence
webinar transcript to social posts
course lesson to lead magnet
newsletter to ad hooks
script to carousel
sales page to VEO3 pre-video ideas
Context Library Enrichment
Identify material that should update a context library.
Examples:
new buyer language
new proof
new objection
new methodology explanation
new retired phrase
new voice example
AI Employee Training
Identify content that can help train or guide AI Employees.
Examples:
decision examples
quality standards
voice examples
process demonstrations
before/after examples
Strategic Gap Detection
Identify what is missing from existing content.
Examples:
no objection content
no proof content
no buyer-aware content
no authority content
no comparison content
no sales transition content
Input Types
The scanner may process several content input types.
Content Folders
A grouped folder of posts, scripts, emails, transcripts, or files.
Single Asset
One article, email, script, transcript, sales page, or document.
Campaign Archive
A set of assets from one campaign.
Course Archive
Course lessons or transcripts being reviewed for reusable MWMS system value.
Client Archive
A client’s existing content library during AIBS intake.
Offer Archive
Content related to one specific offer.
Channel Archive
Content from one platform such as YouTube, email, blog, LinkedIn, or TikTok.
Scanner Output Categories
The Content Intelligence Scanner should classify findings into useful categories.
- Reusable Angles
Angles that could become content, ads, hooks, emails, or campaigns.
- Frameworks And Methods
Structured thinking that could become MCR pages, internal frameworks, or client context.
- Buyer Language
Real or near-real language that reflects buyer problems, desires, objections, or outcomes.
- Objections And Friction
Resistance signals that should feed Sales Brain, Conversion Brain, or Offer Brain.
- Proof And Credibility
Evidence that may support offers, content, or sales assets after approval.
- Voice Examples
Strong examples of founder or brand voice.
- Asset Opportunities
Ideas for lead magnets, webinars, emails, landing pages, social posts, or scripts.
- Repurposing Opportunities
Existing content that can be transformed into another useful format.
- Context Library Updates
Information that should update an approved context file.
- Ignore Or Archive
Material that is weak, outdated, generic, irrelevant, or duplicated.
Scanner Workflow
MWMS uses the following workflow.
Step 1: Define The Scan Objective
Before scanning, define the purpose.
Possible objectives:
find content angles
extract buyer language
find lead magnet ideas
find webinar ideas
enrich context library
identify sales assets
support offer positioning
review client archive
repurpose existing content
Step 2: Identify The Source Set
Define what content is being scanned.
Examples:
one folder
one transcript set
one email archive
one campaign archive
one client content folder
one offer folder
Step 3: Identify The Owning Brain
Determine which Brain owns the scan.
Examples:
Content Brain owns content opportunity scans.
Offer Brain owns offer support scans.
Sales Brain owns objection and sales asset scans.
Research Brain owns signal extraction and evidence review.
HeadOffice governs cross-system value and MCR promotion.
Step 4: Activate Relevant Context
If the scan relates to an offer or client, activate the relevant context library.
If no context exists, scan may proceed as discovery but output should remain draft.
Step 5: Extract Signals
Extract useful business signals.
Do not summarize everything.
Look for reusable intelligence.
Step 6: Classify Findings
Classify each finding into the scanner output categories.
Step 7: Score Usefulness
Score each finding based on business usefulness.
Suggested scores:
High Value
Medium Value
Low Value
Ignore
Step 8: Recommend Destination
Each useful finding should have a destination.
Possible destinations:
Content Brain
Offer Brain
Sales Brain
Creative Brain
Research Brain
Affiliate Brain
Context Library
MCR
Parking System
Archive
No Action
Step 9: Define Next Action
Each useful finding should have a clear next action.
Examples:
create content brief
update objection library
create lead magnet idea
create webinar idea
add to customer language bank
route to sales asset creation
park for later
ignore
Step 10: Capture Learning
If the scan reveals durable intelligence, route it into the correct library or registry after review.
Content Signal Scoring
The scanner should score content signals using four checks.
Business Value
Does this signal support revenue, trust, conversion, positioning, retention, client delivery, or system improvement?
Specificity
Is the signal specific enough to be useful?
Reusability
Can it be reused across assets, Brains, AI Employees, or workflows?
Context Fit
Does it fit an existing offer, Brain, client, campaign, or future MWMS system?
Scoring Outcomes
High Value
Strong candidate for action, routing, or context update.
Medium Value
Useful but may need refinement or more evidence.
Low Value
Minor usefulness; may be archived or parked.
Ignore
Generic, weak, duplicated, outdated, or irrelevant.
Content Repurposing Rules
Existing content may be repurposed only when it has strategic value.
Do not repurpose content simply because it exists.
Repurposing should preserve:
message accuracy
voice
buyer fit
offer alignment
proof limits
context relevance
Repurposing may create:
email sequence
social posts
ad hooks
VEO3 scripts
blog post
carousel
lead magnet
webinar section
sales page block
FAQ
client report section
Repurposed content must still be validated before use.
Context Library Update Rules
Scanner findings may update a context library only after review.
Possible updates include:
new customer phrase
new objection
new proof point
new voice example
new retired language
new methodology detail
new differentiation point
new expert thinking rule
Do not dump entire scanned content into the context library.
Extract only durable, useful context.
The rule is:
Scan broadly. Promote selectively.
Client Content Scan Rules
Future AIBS client content scans require stricter handling.
Client content must remain isolated.
Client content should only update that client’s context library.
Client content must not be used for MWMS internal assets unless approved.
Client proof must not be used unless approved.
Client language must not be reused across other clients.
Client scans should identify:
voice
offer clarity
buyer language
proof
objections
content gaps
repurposing opportunities
workflow opportunities
skill candidates
Course Content Scan Rules
Course content scanning must follow the MWMS Course Absorption Operating Rule.
The scanner must not absorb course material as content just because it exists.
Course content must pass:
Value Test
Novelty Test
Superiority Test
Fit Test
Course signals should be extracted at capability level, not lesson level.
Possible outcomes:
Absorb Now
Merge Into Existing Page
Park For Later
Ignore
Content Gap Detection
The scanner should identify missing content categories.
Possible gaps:
no buyer problem content
no objection content
no proof content
no methodology content
no founder belief content
no comparison content
no case study content
no FAQ content
no trust-building content
no sales transition content
no onboarding content
no retention content
Gap detection helps Content Brain plan future content.
Content Opportunity Record
Each useful finding may be captured using the following structure.
Source:
Content Type:
Relevant Offer Or Client:
Signal Type:
Extracted Signal:
Why It Matters:
Recommended Destination:
Recommended Action:
Priority:
Context Update Required:
Human Review Required:
Notes:
Minimum Scanner Output
For quick scans, use:
Source:
Top Signals:
Useful Angles:
Content Opportunities:
Context Updates:
Ignore:
Next Action:
Common Failure Modes
MWMS must prevent:
summarizing instead of extracting
treating all old content as useful
repurposing weak content
copying content into context libraries without review
mixing client content with MWMS content
inventing customer language
ignoring proof limits
missing strong founder language
failing to route useful findings
creating content ideas with no offer connection
overloading Content Brain with low-value ideas
turning course lessons into duplicate MCR pages
Scanner Quality Standards
A strong content scan should be:
selective
business-relevant
source-aware
offer-aware
Brain-routed
action-oriented
context-grounded
clear about what to ignore
clear about next actions
A weak content scan is:
a summary
too broad
too long
not routed
not scored
not tied to business value
not tied to an offer
filled with generic ideas
missing action recommendations
Governance Role
Content Brain owns the MWMS Content Intelligence Scanner Framework.
HeadOffice governs cross-system routing, MCR promotion, and source-of-truth discipline.
Research Brain supports evidence extraction and signal quality.
Offer Brain supports offer-fit interpretation.
Sales Brain supports objection and sales asset interpretation.
Creative Brain supports angle and creative opportunity interpretation.
AI Business Systems Brain governs future client content scan application.
Individual Brains may use scanner outputs, but Content Brain governs content opportunity logic.
Relationship To Other MWMS Standards
This framework supports and must align with:
MWMS Document Structure Standard
MWMS Course Absorption Operating Rule
MWMS Client IP Excavation Framework
MWMS Offer Context Library Standard
MWMS Context Library Governance And Folder Map Standard
MWMS AI Context Activation And Usage Protocol
MWMS Context-Driven Asset Builder Framework
MWMS Context-Grounded Lead Magnet Funnel Framework
MWMS Context-Grounded Evergreen Webinar Framework
MWMS Tool-Agnostic Context Portability Protocol
MWMS AI Skill Builder And Audit Protocol
MWMS AI Brain Audit And Decay Prevention Framework
Content Brain VOC Grounded AI Copy Framework
Research Brain Voice Of Customer Extraction Framework
Offer Brain Offer Structure Framework
Sales Brain Objection Resolution Framework
Creative Brain Belief Shift Framework
AI Business Systems Brain Canon
This framework defines how existing content becomes reusable content intelligence.
Drift Protection
This framework protects MWMS from:
content archive waste
random repurposing
generic content ideas
summary-style scanning
weak content being promoted
client content leakage
course content duplication
context library bloat
lost founder language
lost buyer language
lost objections
unrouted content opportunities
creating new content while ignoring better existing source material
Any content scan that produces summaries without routing, scoring, or next actions should be treated as a drift risk.
Architectural Intent
The architectural intent of the MWMS Content Intelligence Scanner Framework is to turn existing content into reusable strategic intelligence.
MWMS and future clients will often already have valuable material.
The system should be able to scan that material and answer:
What is useful here?
What should be ignored?
What can become new content?
What can become an ad angle?
What can become a lead magnet?
What can become a webinar section?
What should update the context library?
What should support sales?
What should support offer positioning?
What should be parked?
What should be routed to another Brain?
When MWMS can answer these questions consistently, content archives become intelligence assets instead of forgotten folders.
Change Log
v1.0 — Initial Draft
Created the MWMS Content Intelligence Scanner Framework as the framework for scanning existing content libraries, folders, transcripts, posts, emails, newsletters, sales assets, course material, articles, scripts, and client archives to extract reusable content intelligence.
This framework defines scanner objectives, input types, output categories, scanner workflow, signal scoring, repurposing rules, context library update rules, client scan rules, course scan rules, content gap detection, opportunity records, failure modes, governance role, drift protection, and architectural intent.
Change Impact Declaration
Pages Created:
MWMS Content Intelligence Scanner Framework
Pages Updated:
None
Pages Deprecated:
None
Registries Requiring Update:
MWMS Architecture Registry
Content Brain Page Registry
AI Business Systems Brain Page Registry
Offer Brain Page Registry
Sales Brain Page Registry
Creative Brain Page Registry
Research Brain Page Registry
Canon Version Update Required:
No
Change Log Entry Required:
Yes
Employee Impact Check
Employees impacted:
Content Planner Employee
Creative Strategist Employee
Offer Strategist Employee
Sales Strategist Employee
Research Analyst Employee
Course Absorption Agent
AI Business Systems Architect Employee
Context Library Builder
Required behaviour updates:
AI Employees must scan existing content for reusable business intelligence before creating new content from scratch where relevant.
AI Employees must classify scanned content into angles, frameworks, buyer language, objections, proof, voice examples, asset opportunities, repurposing opportunities, context library updates, or ignore/archive.
AI Employees must not treat content scanning as summarization.
AI Employees must route useful findings to the appropriate Brain, context library, parking system, or next action.
AI Employees must keep client content isolated and avoid promoting client material into MWMS general context without approval.
END MWMS CONTENT INTELLIGENCE SCANNER FRAMEWORK v1.0