System: MWMS
Document Type: Framework
Authority Level: MCR Source Of Truth
Status: Draft For MCR
Primary Location: MCR
Future Operational Destination: HeadOffice Brain, AI Business Systems Brain, Offer Brain, Content Brain, Creative Brain, Sales Brain, Conversion Brain, Customer Brain, AI Manager, AI Employee Router, Future AIBS Client Systems
Parent Page: HeadOffice
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 Context-Driven Asset Builder Framework.
This framework establishes how MWMS creates business assets from approved context libraries instead of relying on generic prompts, templates, disconnected AI drafts, or surface-level marketing structures.
MWMS must not create important assets from thin context.
A business asset should be built from the actual intelligence inside the offer, client, buyer, voice, proof, methodology, and objections.
This framework exists to ensure that when MWMS creates assets such as lead magnets, landing pages, emails, webinars, opt-in funnels, VSL support material, sales assets, content assets, client reports, or campaign briefs, the output is grounded in:
the right buyer
the right offer
the right voice
the right methodology
the right objections
the right proof
the right differentiation
the right customer language
the right compliance boundaries
the right business goal
The goal is to prevent MWMS outputs from becoming:
generic
template-first
off-brand
over-polished
detached from buyer reality
misaligned with the offer
unsupported by proof
inconsistent across Brains
created too early before context is ready
The Context-Driven Asset Builder Framework turns approved context libraries into useful business assets.
Scope
This framework applies to all MWMS asset creation workflows where AI is used to create, draft, structure, improve, or review business outputs.
This includes:
lead magnets
opt-in funnels
landing pages
thank-you pages
webinar outlines
email sequences
sales pages
VSL support assets
ad scripts
VEO3 scripts
content briefs
social posts
carousels
newsletter assets
sales call support assets
client reports
offer explanation documents
AI Business Systems client assets
internal MWMS operating assets
This framework supports:
AI Business Systems Brain
Offer Brain
Content Brain
Creative Brain
Sales Brain
Conversion Brain
Customer Brain
Research Brain
Ads Brain
Affiliate Brain
HeadOffice Brain
future AIBS client systems
This framework does not authorize development work, plugin changes, Supabase changes, WordPress changes, automation wiring, live publishing, or M developer action.
Core Definition
Context-Driven Asset Building is the process of creating business assets by first activating the correct context library and then using that context to shape the asset.
The process is not:
choose a template
fill in blanks
ask AI for a generic asset
polish the output
publish
The correct process is:
identify the business goal
activate the approved context library
select the relevant context files
choose the correct asset type
define the asset’s job
build from source truth
validate against context
route for review
capture learning back into the system
Core Principle
The core principle of this framework is:
Business assets should be built from source intelligence, not from generic AI creativity.
AI may help structure, write, format, and generate variations.
But AI must not replace the context layer.
A strong MWMS asset should feel specific because it is built from:
real offer logic
real buyer pain
real buyer language
real objections
real methodology
real proof
real voice
real positioning
A weak MWMS asset usually feels generic because it is built from:
a prompt
a template
a trend
a vague audience
a shallow offer summary
a guessed objection
a fake proof point
Asset Builder Inputs
Before creating an asset, MWMS should identify the required inputs.
Required inputs may include:
asset objective
owning Brain
offer or client name
approved context library
target buyer
offer profile
voice architecture
differentiation profile
objection library
methodology map
customer language bank
proof library
brand visual style
retired language
compliance notes
destination or platform
human review requirement
If required context is missing, the AI Employee must flag the gap before producing a high-value output.
Asset Objective Rule
Every asset must have a clear job.
An asset may be designed to:
capture attention
generate a lead
educate the buyer
shift belief
build trust
handle objections
explain the method
increase desire
reduce anxiety
support conversion
prepare a sales call
support onboarding
drive a click
support a campaign
improve retention
create proof
A business asset without a job becomes content noise.
The AI Employee must identify the asset objective before drafting.
Primary Asset Categories
MWMS recognizes several asset categories.
- Lead Generation Assets
Purpose:
Capture attention and convert interest into a lead.
Examples:
lead magnets
checklists
guides
quizzes
diagnostic tools
resource packs
PDF downloads
mini-trainings
Required context:
Right-Fit Client Profile
Offer Profile
Objection Library
Customer Language Bank
Differentiation Profile
Voice Architecture
Compliance Notes where relevant
- Conversion Assets
Purpose:
Move the buyer toward action.
Examples:
landing pages
sales pages
thank-you pages
CTA blocks
checkout support copy
VSL support copy
offer explanation pages
Required context:
Offer Profile
Right-Fit Client Profile
Proof Library
Objection Library
Differentiation Profile
Customer Language Bank
Compliance Notes
- Nurture Assets
Purpose:
Build trust, clarity, and relationship over time.
Examples:
email sequences
newsletter sections
onboarding emails
education sequences
relationship-building content
trust-building content
Required context:
Voice Architecture
Right-Fit Client Profile
Customer Language Bank
Methodology Map
Objection Library
Proof Library
- Authority Assets
Purpose:
Demonstrate expertise, differentiation, and point of view.
Examples:
framework posts
thought leadership content
webinars
case breakdowns
expert guides
belief-shift content
Required context:
Contrarian Stances
Methodology Map
Expert Thinking Rules
Differentiation Profile
Proof Library
Voice Architecture
- Creative Assets
Purpose:
Turn strategy into engaging creative output.
Examples:
VEO3 scripts
ad concepts
image prompts
thumbnails
storyboards
hooks
creative briefs
Required context:
Right-Fit Client Profile
Differentiation Profile
Customer Language Bank
Voice Architecture
Brand Visual Style
Retired Language
Compliance Notes
- Sales Assets
Purpose:
Support sales conversations, objection handling, and buyer progression.
Examples:
sales call notes
objection handling sheets
proposal copy
follow-up messages
diagnostic call frameworks
one-page offer summaries
Required context:
Offer Profile
Objection Library
Proof Library
Expert Thinking Rules
Right-Fit Client Profile
Sales Brain standards
- Client System Assets
Purpose:
Support future AIBS delivery and client reporting.
Examples:
client report drafts
AI system explanation pages
client onboarding guides
business process summaries
workflow documentation
training assets
Required context:
Client Context Library
Offer Context Library
AI Business Systems Brain standards
Voice Architecture
Client Approval Rules
Compliance Notes where relevant
Asset Build Workflow
MWMS uses the following workflow to build context-driven assets.
Step 1: Define The Asset Objective
The AI Employee must identify what the asset is supposed to do.
Examples:
generate opt-ins
prepare the buyer for the sales page
handle one specific objection
explain the core methodology
convert paid traffic to VSL clicks
nurture a cold lead
warm up a sales call
If the objective is unclear, ask for clarification or propose a likely objective for review.
Step 2: Identify Owning Brain
The AI Employee must identify which Brain owns the asset.
Examples:
Content Brain owns content assets.
Offer Brain owns offer structure assets.
Sales Brain owns sales assets.
Creative Brain owns creative assets.
Conversion Brain owns conversion assets.
AIBS Brain owns future client system assets.
HeadOffice governs cross-Brain and system-level usage.
Step 3: Activate The Context Library
The AI Employee must activate the relevant approved context library.
If no approved library exists, use draft context only with a warning or recommend IP Excavation / context library construction first.
Step 4: Select Relevant Context Files
The AI Employee selects only the files needed for the asset.
Examples:
For a lead magnet:
Right-Fit Client Profile
Offer Profile
Objection Library
Customer Language Bank
Differentiation Profile
Voice Architecture
For a webinar:
Contrarian Stances
Methodology Map
Expert Thinking Rules
Offer Profile
Right-Fit Client Profile
Objection Library
Proof Library
For a sales page:
Offer Profile
Right-Fit Client Profile
Differentiation Profile
Objection Library
Proof Library
Customer Language Bank
Compliance Notes
Step 5: Define The Asset Structure
The AI Employee selects or creates a structure that fits the asset’s job.
Structure should follow the objective and context.
Do not force a generic template when the offer requires a different structure.
Step 6: Build The Asset
The AI Employee drafts the asset using the selected context.
The output must preserve:
offer truth
buyer truth
voice
methodology
proof limits
retired language rules
compliance notes
Step 7: Validate Against Context
The AI Employee checks the asset against the context library.
The validation must confirm:
correct buyer
correct offer
correct voice
correct promise
correct proof
correct objections
correct methodology
no retired language
no invented claims
clear next step
Step 8: Route For Review
The output must be routed to the correct review path.
Possible destinations:
HeadOffice review
MCR draft
Content Brain
Offer Brain
Sales Brain
Creative Brain
Conversion Brain
AIBS client review
Parking System
Human review
Step 9: Capture Learning
If asset creation reveals useful new insight, MWMS should update the relevant context file after approval.
Examples:
new objection
new wording
new proof
new positioning
new retired phrase
new buyer insight
Asset Quality Standards
A strong context-driven asset should be:
specific
grounded
buyer-aware
offer-accurate
voice-aligned
proof-safe
conversion-aware
clear in purpose
easy to review
connected to a next action
A weak asset is usually:
generic
template-first
too polished
not tied to a buyer
not tied to a real offer
missing objections
missing proof
using fake urgency
using unsupported claims
using retired language
unclear in purpose
too broad for the desired action
Context Use Rules
Rule 1: Use Context Before Creation
The AI Employee must not create important assets before selecting the relevant context files.
Rule 2: Do Not Invent Missing Context
If buyer, offer, proof, or objections are missing, flag the gap.
Rule 3: Retired Language Must Be Checked
Any public-facing or customer-facing asset must check Retired Language where available.
Rule 4: Proof Must Be Approved
Use only approved proof.
Do not invent testimonials, case studies, numbers, examples, or claims.
Rule 5: Asset Structure Must Serve The Objective
Do not use a template just because it exists.
Use the structure that best serves the asset’s job.
Rule 6: Voice Must Be Preserved
Do not over-polish founder or brand voice into generic AI marketing language.
Rule 7: Asset Output Remains Draft Until Reviewed
AI-created assets should remain draft until reviewed by the appropriate human or Brain.
Rule 8: New Learning Must Feed Back Into Context
Useful new insights should not remain trapped in the asset.
If approved, they should update the relevant context library.
Manual Build Versus Skill Build
MWMS distinguishes between manual builds and skill builds.
Manual Build
Use when the asset is large, one-off, or requires custom structure.
Examples:
custom lead magnet
full webinar outline
new sales page
client system explanation page
large launch asset
Skill Build
Use when the same asset type is created repeatedly using a stable procedure.
Examples:
standard content brief
weekly newsletter summary
standard VEO3 pre-video script
recurring client report
repeated lead magnet outline
standard offer evaluation report
The rule is:
If the workflow repeats and has a specific method, consider turning it into a skill.
If the asset is one-off, use a manual build.
Lead Magnet Asset Rule
A lead magnet must be built from buyer need, not from random topic selection.
Before creating a lead magnet, identify:
buyer problem
urgent pain
desired quick win
belief shift needed
connection to offer
next step
delivery format
proof or credibility need
Lead magnets should not be disconnected freebies.
They should create movement toward the offer.
Landing Page Asset Rule
A landing page must preserve message match.
Before creating a landing page, identify:
traffic source
buyer awareness level
promise
core pain
proof requirement
objection sequence
CTA
next step
Landing pages must not change the offer promise or create claims not supported by the context library.
Thank-You Page Asset Rule
A thank-you page should not be wasted space.
It may support:
delivery confirmation
expectation setting
trust building
next step
VSL click
sales call booking
email whitelist instruction
related asset routing
The thank-you page should match the funnel goal.
Webinar Asset Rule
A webinar must be built from the offer’s belief shift, methodology, and buyer objections.
Before creating a webinar, identify:
target buyer
old belief
new belief
core methodology
main transformation
proof
objections
offer bridge
A webinar should not become generic teaching content.
It should create strategic readiness for the offer.
Email Asset Rule
Emails must use voice, customer language, objections, and offer truth.
Before creating email assets, identify:
email objective
sequence role
buyer stage
core message
CTA
objection handled
proof used
Emails should not feel disconnected from the wider offer and content system.
Creative Asset Rule
Creative assets must be grounded in strategy.
Before creating creative assets, identify:
buyer
hook angle
emotional trigger
belief shift
visual direction
offer connection
platform
compliance risk
Creative should not exist only to look good.
It must serve business movement.
Asset Validation Checklist
Before an asset is approved, check:
Is the objective clear?
Is the owning Brain clear?
Was the correct context library used?
Was the buyer profile used?
Was the offer profile used?
Was the voice preserved?
Was differentiation clear?
Were objections addressed where needed?
Was proof approved?
Was retired language avoided?
Were claims safe?
Was the next step clear?
Is the asset too generic?
Does the structure match the asset’s job?
Does human review remain required?
Should any new insight update the context library?
Common Failure Modes
MWMS must prevent:
creating assets before context activation
using generic templates without offer fit
inventing buyer language
inventing proof
changing the offer promise
ignoring objections
ignoring voice rules
over-polishing founder tone
using retired language
building lead magnets disconnected from the offer
creating webinars that teach but do not move belief
creating landing pages with poor message match
creating creative assets that are visually interesting but strategically weak
treating draft assets as approved
forgetting to update context after new learning
Governance Role
HeadOffice owns the MWMS Context-Driven Asset Builder Framework.
HeadOffice is responsible for:
ensuring important assets use approved context
preventing generic asset creation
preventing unsupported claims
requiring review before activation
ensuring correct Brain ownership
ensuring asset learning feeds back into context
preventing client context misuse
protecting MCR from weak page creation
protecting future AIBS client systems from shallow asset generation
Individual Brains may govern asset-specific logic.
Offer Brain governs offer accuracy.
Content Brain governs content usage.
Creative Brain governs creative asset quality.
Sales Brain governs sales asset fit.
Conversion Brain governs conversion flow.
Compliance Brain governs claim safety.
AI Business Systems Brain governs future client asset packages.
Relationship To Other MWMS Standards
This framework supports and must align with:
MWMS Document Structure Standard
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 AI Agent Memory And Context Framework
MWMS AI Agent Skill Library Framework
MWMS AI Skill Builder And Audit Protocol
MWMS AI Brain Audit And Decay Prevention Framework
MWMS AI Output Validation Standard
MWMS Messy Input Normalization Framework
MWMS Brain Routing Rule
MWMS MCR Promotion To Brain Protocol
Content Brain VOC Grounded AI Copy Framework
Content Brain Content Brief Template
Offer Brain Offer Structure Framework
Creative Brain Belief Shift Framework
Sales Brain Objection Resolution Framework
Conversion Brain Landing Page Structure Framework
Compliance Brain Claims Risk Framework
AI Business Systems Brain Canon
This framework defines how approved context becomes useful business assets.
Drift Protection
This framework protects MWMS from:
generic AI asset creation
template-first marketing
asset creation before context is ready
invented proof
invented buyer language
wrong buyer targeting
wrong offer promise
voice drift
retired language returning
poor message match
weak lead magnets
disconnected webinars
sales assets without objections
creative assets without strategy
client assets built from incomplete context
future AIBS systems producing shallow outputs
Any important asset created without approved context activation should be treated as a draft requiring review.
Architectural Intent
The architectural intent of the MWMS Context-Driven Asset Builder Framework is to ensure that MWMS can turn approved intelligence into business assets without losing specificity, voice, proof, buyer reality, or strategic purpose.
MWMS is not creating assets for the sake of output volume.
MWMS is creating assets that should move the business forward.
The long-term goal is that every major asset can answer:
What is this asset for?
Which Brain owns it?
Which buyer is it for?
Which offer does it support?
Which context files were used?
What proof supports it?
What objections does it address?
What next step does it create?
What language must it avoid?
What review is required?
What learning should feed back into the system?
When MWMS can answer these questions consistently, AI-assisted asset creation becomes more reliable, more strategic, more scalable, and safer for future client systems.
Change Log
v1.0 — Initial Draft
Created the MWMS Context-Driven Asset Builder Framework as the framework for creating business assets from approved context libraries instead of generic prompts or disconnected templates.
This framework defines asset builder inputs, asset objective rules, primary asset categories, asset build workflow, quality standards, context use rules, manual build versus skill build, lead magnet rules, landing page rules, thank-you page rules, webinar rules, email rules, creative asset rules, validation checklist, failure modes, governance role, drift protection, and architectural intent.
Change Impact Declaration
Pages Created:
MWMS Context-Driven Asset Builder Framework
Pages Updated:
None
Pages Deprecated:
None
Registries Requiring Update:
MWMS Architecture Registry
HeadOffice Page Registry
AI Business Systems Brain Page Registry
Content Brain Page Registry
Offer Brain Page Registry
Creative Brain Page Registry
Sales Brain Page Registry
Conversion Brain Page Registry
Canon Version Update Required:
No
Change Log Entry Required:
Yes
Employee Impact Check
Employees impacted:
HeadOffice Manager Employee
AI Manager
AI Employee Router
Context Library Builder
Offer Strategist Employee
Content Planner Employee
Creative Strategist Employee
Sales Strategist Employee
Conversion Strategist Employee
AIBS Asset Builder Employee
AI Business Systems Architect Employee
Required behaviour updates:
AI Employees must identify the asset objective before creating business assets.
AI Employees must activate the relevant context library before creating important offer, content, sales, creative, conversion, or client-facing outputs.
AI Employees must not create template-first assets disconnected from buyer, offer, proof, objections, methodology, voice, and business goal.
AI Employees must validate assets against context before routing them forward.
AI Employees must capture useful new insights from asset creation and route them back into the relevant context library after approval.
END MWMS CONTEXT-DRIVEN ASSET BUILDER FRAMEWORK v1.0