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, AI Manager, AI Employee Router, Brain Room, Course Absorption System, Content Brain, Offer Brain, Sales Brain, Creative Brain, 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 AI Brain Build Sequence Framework.
This framework establishes the correct operating sequence for building a reusable AI Brain, offer context library, client intelligence layer, AI Employee context base, or future AIBS client system.
MWMS must not build AI systems in a random order.
The system must avoid jumping straight from raw material to asset creation.
The correct sequence is:
Prepare
Excavate
Construct
Activate
Build
Audit
This sequence ensures that MWMS captures the right source material, extracts the right business intelligence, constructs the right context library, activates the right files, creates the right assets, and reviews the system before it decays.
The framework exists to prevent:
premature asset creation
generic AI output
missing context
weak offer understanding
duplicated files
unreviewed source material
unstructured client onboarding
AI Employees starting from empty context
context libraries sitting unused
skills being created before procedures are clear
future AIBS client systems being built on shallow foundations
The AI Brain Build Sequence gives MWMS a repeatable path for turning human expertise into usable AI operating intelligence.
Scope
This framework applies to all MWMS work where a business, offer, Brain, client system, product, service, campaign, or internal process needs to become reusable AI context.
This includes:
AI Business Systems Brain
HeadOffice Brain
AI Manager
AI Employee Router
Brain Room
Offer Brain
Content Brain
Creative Brain
Sales Brain
Conversion Brain
Customer Brain
Research Brain
Affiliate Brain
Ads Brain
Product Brain
Strategy Brain
Course Absorption System
Newsletter Intelligence
Opportunity System
future AIBS client systems
This framework applies when MWMS is building:
client AI Brains
offer context libraries
AI Employee context bases
content systems
sales systems
ad systems
funnel systems
context-driven asset systems
skill libraries
tool-agnostic context packs
future client delivery packages
This framework does not authorize development work, plugin changes, Supabase changes, WordPress changes, automation wiring, or M developer action.
Core Definition
An AI Brain Build Sequence is the governed process of transforming raw business material into reusable AI-operational intelligence.
It defines the order in which MWMS should move from:
raw source material
to extracted IP
to structured context files
to activated context
to business assets
to audited, maintained systems
The sequence ensures that MWMS does not confuse:
raw material with approved context
draft files with source truth
asset outputs with context libraries
skills with tools
memory with current source truth
AI drafts with approved business assets
Core Principle
The core principle of this framework is:
Do not build from prompts when the system needs context.
Prompts may help produce output.
Context gives the output direction.
Skills give the work repeatability.
Audits keep the system alive.
MWMS must build in the correct order so that each layer supports the next layer.
The MWMS AI Brain Build Sequence
The approved sequence is:
Stage 1: Prepare
Stage 2: Excavate
Stage 3: Construct
Stage 4: Activate
Stage 5: Build
Stage 6: Audit
Each stage has a distinct purpose.
Skipping stages creates drift.
Stage 1: Prepare
Purpose
Prepare is the source-gathering stage.
The purpose of Prepare is to collect the raw material needed to understand the business, offer, client, Brain, or system before asking AI to build anything meaningful.
Prepare answers:
What are we building around?
What source material exists?
What offer or system is the focus?
What buyer or user is involved?
What output is ultimately needed?
What context already exists?
What is missing?
What must not be touched?
What source is authoritative?
Inputs
Prepare may gather:
emails
newsletters
sales pages
landing pages
social posts
course outlines
SOPs
call notes
client notes
customer interviews
testimonials
objections
support messages
survey data
voice memos
workshop notes
ad scripts
offer pages
VSL notes
campaign material
existing MWMS pages
client documents
screenshots
tool exports
Output
The output of Prepare is a clean source material set.
This may include:
Raw Material folder
source list
missing material list
offer focus
buyer focus
workflow boundary
known constraints
developer boundary
human review requirement
Rules
Prepare must not become analysis too early.
Prepare collects and organizes.
It does not invent.
It does not promote.
It does not create major assets.
Prepare is complete when MWMS has enough source material to begin extraction or has clearly identified what is missing.
Stage 2: Excavate
Purpose
Excavate is the intelligence extraction stage.
The purpose of Excavate is to pull the real business intelligence out of the source material.
Excavate answers:
What does the founder believe?
What does the market misunderstand?
What is the methodology?
What expert judgment exists?
What customer language matters?
What objections appear?
What proof exists?
What makes the offer different?
Primary Extraction Layers
MWMS uses three primary extraction layers:
Contrarian Stances
Methodology And Process
Expert Thinking
Additional extraction may include:
customer language
objections
proof
voice patterns
visual style notes
retired language
offer claims
buyer false beliefs
Output
The output of Excavate may include:
My Contrarian Stances
My Methodology
My Expert Thinking
Customer Language Extract
Objection Extract
Proof Extract
Voice Notes
Retired Language Candidates
Missing Evidence List
Rules
Excavate must extract, not invent.
If evidence is missing, flag it.
If language is strong, preserve it.
If material is weak, mark it as weak.
If the source does not support a claim, do not create the claim.
Excavate is complete when MWMS has enough approved extracted intelligence to construct structured context files.
Stage 3: Construct
Purpose
Construct is the context library creation stage.
The purpose of Construct is to turn extracted intelligence into structured AI-readable context files.
Construct answers:
Which context files are needed?
What is the source truth for this offer or client?
What should AI read before creating outputs?
What must AI avoid?
What files belong in the library?
Which files are approved, draft, stale, or archived?
Required Context Files
Depending on the offer or client, Construct may create:
Right-Fit Client Profile
Offer Profile
Voice Architecture
Differentiation Profile
Objection Library
Methodology Map
Expert Thinking Rules
Customer Language Bank
Proof Library
Brand Visual Style
Retired Language
Compliance Notes
Output
The output of Construct is an approved or draft context library.
Rules
Construct must organize intelligence into usable files.
It must not create bloated libraries for the sake of volume.
It must preserve source-of-truth discipline.
It must separate draft from approved files.
It must keep client context isolated.
It must use clear folder structure.
Construct is complete when the context library is structured enough for AI Employees to use.
Stage 4: Activate
Purpose
Activate is the context usage stage.
The purpose of Activate is to make sure the correct context files are selected and used before AI performs meaningful work.
Creating a library is not enough.
AI Employees must know how to use it.
Activate answers:
Which library applies?
Which files are needed?
Which files are approved?
Which files should be ignored?
Which skill or workflow should be used?
What output is being created?
What review is required?
Output
The output of Activate may include:
context pack
selected file list
task-specific briefing
skill selection
manual build instruction
validation checklist
human review requirement
handoff destination
Rules
Activate must happen before important asset creation.
Memory alone is not enough.
Tool memory is not source truth.
Draft context must be marked.
Missing context must be flagged.
Retired Language must be checked for public-facing or customer-facing output.
Activate is complete when the AI Employee has the right working context for the task.
Stage 5: Build
Purpose
Build is the asset or workflow creation stage.
The purpose of Build is to create business outputs from approved context.
Build answers:
What asset is needed?
What is the asset’s job?
Which Brain owns it?
Which context files are required?
Which structure fits the objective?
What output should be produced?
Where should it go next?
Possible Outputs
Build may create:
lead magnets
landing pages
thank-you pages
webinar outlines
email sequences
sales pages
ad scripts
VEO3 scripts
content briefs
social content
client reports
offer summaries
sales call assets
AI Employee role cards
skill records
workflow documents
context packs
Rules
Build must be context-driven.
Do not create template-first assets.
Do not invent proof.
Do not invent buyer language.
Do not change the offer promise.
Do not ignore objections.
Do not use retired language.
Do not treat output as approved before review.
Build is complete when the output has been created, validated, and routed.
Stage 6: Audit
Purpose
Audit is the maintenance and decay-prevention stage.
The purpose of Audit is to make sure AI Brains, context libraries, skills, voice systems, offer files, and client systems remain accurate over time.
Audit answers:
Is this still true?
Is this still useful?
Is this still current?
Is this still source-grounded?
Is the output still good?
Is the skill still working?
Is the context library still clean?
Is old language returning?
Is buyer language still fresh?
Does the system need refreshing, splitting, merging, parking, or retiring?
Output
Audit may produce:
current status
refresh recommendation
merge recommendation
split recommendation
park decision
retirement decision
drift severity
skill update
context update
Kaizen learning
next review date
Rules
Audit must not be skipped for active systems.
AI systems decay when not reviewed.
Repeated human rewriting is a decay signal.
Client systems require ongoing audit expectations.
Audit is complete when a clear outcome is recorded.
Sequence Rules
Rule 1: Do Not Build Before Preparing
If source material is missing, do not pretend the system has enough context.
Rule 2: Do Not Construct Before Excavating
Context libraries should be built from extracted intelligence, not vague assumptions.
Rule 3: Do Not Activate Draft Context As Approved
Draft files must be marked as draft.
Rule 4: Do Not Build Assets Without Context Activation
Important outputs require activated context.
Rule 5: Do Not Treat Output As Source Truth Automatically
Asset outputs may contain useful learning, but they are not automatically context files.
Rule 6: Do Not Skip Audit
AI Brains and context libraries decay.
Audit is part of the build sequence.
Rule 7: Human Review Gates Must Be Respected
Human review is required for high-risk, client-facing, public-facing, compliance-sensitive, MCR, finance, paid traffic, and developer-related work.
MWMS Brain Build Modes
MWMS may use different build modes depending on the situation.
Mode 1: Internal MWMS Brain Build
Used when building context for an internal MWMS Brain or system.
Examples:
Content Brain
Offer Brain
AI Business Systems Brain
HeadOffice Brain
Mode 2: Offer Brain Build
Used when building context around a specific offer.
Examples:
AIBS Base Package
affiliate offer
lead magnet funnel
course product
consulting package
Mode 3: Client Brain Build
Used for future AIBS client systems.
Requires strict client isolation.
Mode 4: Campaign Brain Build
Used when building context for a temporary campaign.
Examples:
VEO3 ad campaign
launch campaign
newsletter campaign
paid traffic test
Mode 5: Skill Build
Used when building reusable procedural intelligence for an AI Employee.
Each mode still follows:
Prepare
Excavate
Construct
Activate
Build
Audit
Minimum Viable Brain Build
For quick internal work, MWMS may use a minimum viable version.
Minimum sequence:
Prepare source material
Extract top stances, methodology, and expert thinking
Create basic offer profile
Create buyer profile
Create voice notes
Build draft asset
Validate
Park or improve
This is acceptable for early internal exploration.
It is not enough for:
client delivery
public launch
paid traffic
automation
MCR canon promotion
client-facing systems
Full Brain Build Requirements
A full Brain or client system should include:
Raw Material folder
IP Excavation files
Offer Context Library
Voice Architecture
Objection Library
Proof Library
Retired Language
Skill definitions where needed
Context activation rules
Asset builder rules
Audit schedule
Human review gates
This level is required for serious MWMS or AIBS deployment.
Common Failure Modes
MWMS must prevent:
jumping straight to prompts
building assets before source material exists
building context from assumptions
creating context libraries without review
using memory instead of current source truth
skipping Retired Language
creating assets from templates without context
creating skills before procedure is clear
auditing only after failure
treating AI output as approved source truth
mixing client context with MWMS context
creating folders without governance
letting useful learning stay trapped in chat threads
Governance Role
HeadOffice owns the MWMS AI Brain Build Sequence Framework.
HeadOffice is responsible for:
defining the correct sequence
preventing premature build work
ensuring source material is gathered
ensuring excavation occurs before context construction
ensuring activation occurs before asset building
ensuring audits occur after use
ensuring human review gates are respected
protecting MCR from premature promotion
protecting M’s active build areas
protecting future AIBS client systems from shallow builds
Individual Brains may operate their own build sequences, but they must align with this framework.
AI Business Systems Brain governs future client-brain applications.
Offer Brain governs offer-specific context construction.
Content Brain governs content asset usage.
Sales Brain governs sales asset usage.
Creative Brain governs creative asset usage.
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 AI Skill Builder And Audit Protocol
MWMS AI Brain Audit And Decay Prevention Framework
MWMS Tool-Agnostic Context Portability Protocol
MWMS AI Agent Memory And Context Framework
MWMS AI Agent Skill Library Framework
MWMS AI Output Validation Standard
MWMS Messy Input Normalization Framework
MWMS Brain Routing Rule
MWMS MCR Promotion To Brain Protocol
MWMS Page Naming Standard
MWMS Architecture Registry
AI Business Systems Brain Canon
This framework provides the high-level sequence that connects the related context, skill, asset, and audit standards.
Drift Protection
This framework protects MWMS from:
building from shallow prompts
premature asset creation
missing source material
unstructured client onboarding
context libraries built from assumptions
skills created too early
AI Employees starting from empty context
tool-specific context traps
generic outputs
public-facing assets without review
client systems built without source truth
context decay after creation
audit neglect
Any major AI Brain, offer library, client system, or business asset created outside this sequence should be treated as a drift risk.
Architectural Intent
The architectural intent of the MWMS AI Brain Build Sequence Framework is to give MWMS a repeatable operating path for turning expertise into AI-operational intelligence.
MWMS is not building random AI outputs.
MWMS is building structured Brains.
The long-term goal is that every serious MWMS or client AI system can answer:
What source material was prepared?
What intelligence was excavated?
What context library was constructed?
What context was activated?
What asset or skill was built?
What validation occurred?
What audit cycle keeps it current?
When MWMS can answer these questions consistently, it becomes easier to scale internal Brains, future AI Employees, and AIBS client systems without losing quality or governance.
Change Log
v1.0 — Initial Draft
Created the MWMS AI Brain Build Sequence Framework as the end-to-end operating sequence for building AI Brains, offer context libraries, client intelligence layers, AI Employee context bases, and future AIBS client systems.
This framework defines the Prepare, Excavate, Construct, Activate, Build, and Audit sequence, including stage purposes, inputs, outputs, rules, build modes, minimum viable builds, full build requirements, failure modes, governance role, drift protection, and architectural intent.
Change Impact Declaration
Pages Created:
MWMS AI Brain Build Sequence Framework
Pages Updated:
None
Pages Deprecated:
None
Registries Requiring Update:
MWMS Architecture Registry
HeadOffice Page Registry
AI Business Systems Brain Page Registry
Offer Brain Page Registry
Content 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
Client IP Excavator
Skill Auditor
Offer Strategist Employee
Content Planner Employee
Creative Strategist Employee
Sales Strategist Employee
Research Analyst Employee
AI Business Systems Architect Employee
Required behaviour updates:
AI Employees must follow the Prepare, Excavate, Construct, Activate, Build, and Audit sequence when building serious AI Brains, context libraries, client systems, or major business assets.
AI Employees must not jump from raw source material directly to asset creation when the task requires reusable context.
AI Employees must identify whether work is internal Brain build, offer Brain build, client Brain build, campaign Brain build, or skill build.
AI Employees must treat audit as part of the build sequence, not optional cleanup.
AI Employees must flag missing source material, missing context, or skipped stages before producing high-value outputs.
END MWMS AI BRAIN BUILD SEQUENCE FRAMEWORK v1.0