System: MWMS
Document Type: Checklist
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, Research 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 Source Material Intake And Evidence Inventory Checklist.
This checklist establishes what source material MWMS should gather, classify, and inventory before building an AI Brain, client Brain, offer context library, skill, asset, course absorption page, or future AIBS client system.
MWMS must not begin serious AI system work from memory alone.
The first step is to identify what source evidence exists.
This checklist exists because AI systems become stronger when they are built from real source material instead of assumptions.
Source material may include:
founder thinking
buyer language
offer documents
sales pages
emails
course transcripts
client notes
customer objections
proof assets
methodology notes
voice samples
workflow documents
support replies
reports
screenshots
campaign results
Without a source material intake process, MWMS risks:
missing valuable evidence
inventing missing context
building weak profiles
creating generic assets
over-absorbing thin material
failing to preserve founder voice
missing buyer objections
using unapproved proof
mixing raw material with active context
building client systems from incomplete input
The Source Material Intake And Evidence Inventory Checklist ensures MWMS begins with a clear evidence base.
Scope
This checklist applies to all MWMS workflows where source material is needed before extraction, context building, skill creation, asset creation, or review.
This includes:
HeadOffice Brain
AI Business Systems Brain
AI Manager
AI Employee Router
Brain Room
Course Absorption System
Newsletter Intelligence
Opportunity System
Offer Brain
Content Brain
Creative Brain
Sales Brain
Conversion Brain
Customer Brain
Research Brain
Affiliate Brain
Ads Brain
Compliance Brain
future AIBS client systems
This checklist applies before:
Client IP Excavation
Offer Context Library construction
Right-Fit Client Profile creation
Offer Profile creation
Voice Architecture creation
Differentiation Profile creation
Objection Library creation
Proof Library creation
Content Intelligence scanning
AI skill conversion
lead magnet creation
webinar creation
sales page drafting
client Brain onboarding
course absorption
developer handoff preparation where current technical evidence is required
This checklist does not authorize development work, plugin changes, Supabase changes, WordPress changes, automation wiring, publishing, file deletion, client implementation, or M developer action.
Core Definition
Source Material Intake is the process of gathering and classifying the raw material needed before MWMS extracts intelligence or builds AI context.
Evidence Inventory is the structured record of what source material exists, where it came from, what it can support, what is missing, and what requires review.
Source material is not automatically approved context.
Source material must be:
collected
classified
reviewed
extracted
structured
validated
promoted where appropriate
Core Principle
The core principle of this checklist is:
Source evidence comes before structured context.
MWMS must know what it is building from before it builds.
Raw material may be messy.
Messy is acceptable.
Missing source truth is the bigger risk.
Source Material Categories
MWMS classifies source material into the following categories.
Opinion Material
Used to extract founder beliefs, contrarian stances, category POV, and market criticism.
Examples:
opinion emails
newsletter commentary
social posts
founder notes
podcast transcripts
interviews
workshop rants
Brain Room comments
sales page belief sections
Process Material
Used to extract methodology, delivery logic, workflows, and repeatable systems.
Examples:
SOPs
course outlines
delivery documents
onboarding steps
implementation checklists
client process notes
workshop agendas
training manuals
framework documents
Reasoning Material
Used to extract expert thinking, diagnostic logic, decision rules, and judgment.
Examples:
audit notes
strategy notes
client review comments
Loom reviews
sales call debriefs
support analysis
troubleshooting notes
before-and-after evaluations
decision explanations
Buyer Material
Used to extract buyer pain, desires, false beliefs, objections, questions, and language.
Examples:
customer emails
DMs
comments
survey responses
sales call transcripts
support tickets
reviews
FAQ questions
refund reasons
objection notes
Proof Material
Used to support claims, credibility, case studies, examples, and trust assets.
Examples:
testimonials
screenshots
case studies
campaign data
analytics reports
client feedback
before-and-after examples
certifications
vendor-approved claims
Voice Material
Used to create Voice Architecture and brand language rules.
Examples:
emails
social posts
scripts
video transcripts
sales pages
voice notes
client reports
founder writing
presentation transcripts
message replies
Offer Material
Used to create Offer Profile and offer context.
Examples:
sales pages
offer pages
pricing documents
proposal documents
checkout pages
VSL scripts
product pages
course outlines
service descriptions
delivery notes
Workflow Material
Used to identify skills, AI Employee tasks, and operational workflows.
Examples:
SOPs
task lists
project notes
automation maps
Make.com notes
Zapier notes
manual process steps
team instructions
reporting workflows
Technical Evidence
Used for developer handoffs, system diagnosis, and exact technical guidance.
Examples:
screenshots
file contents
plugin files
database schema
error logs
current settings
Make.com module screenshots
Supabase table structure
WordPress admin screenshots
Course Material
Used for course absorption and MWMS Blueprint expansion.
Examples:
PDFs
HTML lessons
video transcripts
worksheets
templates
prompts
course notes
tool lists
implementation examples
Source Material Intake Checklist
Use this checklist before beginning major context or Brain work.
General Intake
Is the source material tied to one offer, client, Brain, workflow, or course?
Is the purpose of the intake clear?
Is the owning Brain clear?
Is the material current?
Is the material complete enough for the task?
Are files clearly named?
Are duplicates obvious?
Are old files separated?
Are draft files marked?
Are client-specific files isolated?
Are sensitive files identified?
Opinion Material Check
Do we have founder beliefs?
Do we have market criticism?
Do we have contrarian stances?
Do we have rejected industry advice?
Do we have category POV?
Do we have founder phrases worth preserving?
Do we have enough to extract real positioning?
Process Material Check
Do we have the actual process?
Do we know the first step?
Do we know the sequence?
Do we know what must not be skipped?
Do we know the delivery method?
Do we know the transformation path?
Do we know whether the process is repeatable?
Reasoning Material Check
Do we know how the expert diagnoses?
Do we know what signals they look for?
Do we know when they change approach?
Do we know what makes them reject an output?
Do we know what beginners usually miss?
Do we have examples of judgment in action?
Buyer Material Check
Do we have buyer language?
Do we have objections?
Do we have questions buyers ask?
Do we have reasons buyers hesitate?
Do we have desired outcomes?
Do we have false beliefs?
Do we have trust barriers?
Do we have evidence of buyer sophistication?
Proof Material Check
Do we have approved proof?
Do we know where the proof came from?
Do we know what claim each proof supports?
Do we know what claim each proof does not support?
Do we know whether proof is public-use approved?
Do we know whether proof requires client approval?
Do we know whether proof is current?
Voice Material Check
Do we have natural voice samples?
Do we have polished voice samples?
Do we have examples of strong voice?
Do we have examples of wrong voice?
Do we have preferred phrases?
Do we have banned phrases?
Do we have retired language candidates?
Offer Material Check
Do we know the offer name?
Do we know the offer type?
Do we know what is included?
Do we know what is not included?
Do we know the promise?
Do we know the mechanism?
Do we know the delivery model?
Do we know the next step?
Workflow Material Check
Do we know what tasks repeat?
Do we know what tasks are slow?
Do we know what tasks need human review?
Do we know what tasks may become skills?
Do we know what tasks should not be automated?
Do we know tool boundaries?
Do we know handoff points?
Technical Evidence Check
Do we have current file contents?
Do we have current screenshots?
Do we have current errors?
Do we know the exact file path?
Do we know the exact current state?
Do we know what not to touch?
Do we know the test step?
Do we know the rollback or safety requirement?
If not, do not give exact developer instructions.
Course Material Check
Do we have the course files?
Do we have transcripts where needed?
Do we know whether videos contain unique value?
Do we know whether PDFs are enough?
Do we know whether material is superior to existing MWMS logic?
Do we know whether material should be absorbed, merged, parked, or ignored?
Evidence Inventory Template
Use this template when recording source material.
Project Or Offer Name:
Owning Brain:
Source Material Set:
Source Type:
File Or Asset Name:
Source Location:
Date Or Version:
Material Category:
Current Status:
Evidence Strength:
Can Support:
Cannot Support:
Sensitive Or Restricted:
Client-Specific:
Needs Review:
Missing Material:
Recommended Use:
Next Action:
Notes:
Minimum Evidence Inventory
For quick intake, use:
Source:
Category:
Useful For:
Status:
Missing:
Next Action:
Evidence Strength Levels
MWMS uses the following evidence strength levels.
Strong Evidence
Direct source material clearly supports extraction or use.
Examples:
real customer quote
approved testimonial
current sales page
clear SOP
full transcript
Moderate Evidence
Useful source exists but may need review or clarification.
Examples:
partial notes
rough transcript
older page
founder memory
draft worksheet
Weak Evidence
Material suggests direction but is not strong enough for confident use.
Examples:
sales page hype
thin summary
vague notes
incomplete screenshots
generic worksheet
No Evidence
No usable source exists.
Action:
mark missing context.
Evidence Status Labels
Use the following labels.
Raw
Collected but not processed.
Under Review
Being reviewed.
Extracted
Useful intelligence has been pulled out.
Structured
Converted into context file format.
Approved
Reviewed and usable.
Draft
Usable only for draft work.
Restricted
Usable only under limits.
Archived
Not active.
Rejected
Should not be used.
Missing
Required material not available.
Source Material Handling Rules
Rule 1: Raw Material Is Not Active Context
Do not treat raw files as approved context.
Rule 2: Source Material Must Be Classified
Every source should have a category and likely use.
Rule 3: Strong Language Should Be Preserved
Do not over-polish founder or buyer language during intake.
Rule 4: Weak Evidence Must Be Labelled
Do not hide weak support inside strong output.
Rule 5: Client Material Must Stay Isolated
Client source material belongs in client-specific folders.
Rule 6: Proof Requires Separate Approval
Proof is not approved just because it appears in source material.
Rule 7: Technical Guidance Requires Current Technical Evidence
Do not provide exact technical instructions from stale memory.
Rule 8: Course Material Must Pass Value Tests
Do not absorb course material simply because it exists.
Rule 9: Duplicates Must Be Marked
Duplicate or conflicting source files must be flagged.
Rule 10: Missing Material Must Be Listed
Do not continue as if missing material does not matter.
Intake Outcomes
After source material intake, assign one or more outcomes.
Ready For IP Excavation
Enough source exists to extract beliefs, methodology, and expert thinking.
Ready For Context Library Draft
Enough extracted or source material exists to begin structured context files.
Ready For Manual Draft Work
Enough context exists for human-reviewed drafting.
Needs More Source Material
Important source is missing.
Needs Transcription
Video or audio likely contains the real value.
Needs Human Review
Material requires Martyn, founder, client, or expert review.
Needs Client Approval
Client-owned material requires approval.
Needs Technical Confirmation
Technical state is not known enough for instructions.
Park For Later
Useful but not now.
Ignore
Weak, duplicated, irrelevant, or not superior.
Intake Workflow
MWMS uses the following workflow.
Step 1: Define Intake Purpose
Identify why source material is being gathered.
Step 2: Identify Owning Brain
Assign responsibility.
Step 3: Collect Material
Gather available files, notes, transcripts, screenshots, and documents.
Step 4: Classify Material
Assign each source to a category.
Step 5: Assess Evidence Strength
Strong, moderate, weak, or no evidence.
Step 6: Identify Missing Material
Mark gaps.
Step 7: Decide Readiness
Choose the correct intake outcome.
Step 8: Route Material
Send to IP Excavation, Context Library Build, Course Absorption, Skill Conversion, Asset Build, Parking, or Ignore.
Step 9: Record Inventory
Capture enough detail for future sessions.
Step 10: Protect Boundaries
Ensure client, technical, and development boundaries are respected.
Common Failure Modes
MWMS must prevent:
starting from memory only
mixing raw material with active context
treating weak evidence as strong evidence
losing useful founder language
losing useful buyer language
inventing proof
over-absorbing thin course material
using client material in general MWMS context
giving technical instructions without current technical evidence
failing to record what material exists
forgetting what material is missing
Governance Role
HeadOffice owns the MWMS Source Material Intake And Evidence Inventory Checklist.
HeadOffice is responsible for:
requiring source intake before major build work
ensuring source material is classified
ensuring evidence strength is marked
ensuring missing material is identified
ensuring weak evidence is not overused
ensuring client material is isolated
ensuring course material is evaluated selectively
ensuring technical evidence is current before developer guidance
Individual Brains may maintain their own source intake records, but they must align with this checklist.
AI Business Systems Brain governs future client intake evidence.
Course Absorption System governs course material intake.
Research Brain governs evidence quality where external support is needed.
Compliance Brain governs sensitive proof and claims evidence.
Relationship To Other MWMS Standards
This checklist supports and must align with:
MWMS Document Structure Standard
MWMS Missing Context And Evidence Gap Handling Rule
MWMS Minimum Viable Context Library 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 AI Context Pack Template Standard
MWMS Voice Architecture And Brand Language Standard
MWMS Right-Fit Client And Offer Profile Standard
MWMS Differentiation And Objection Library Standard
MWMS Proof Library And Claims Control Standard
MWMS Content Intelligence Scanner Framework
MWMS Source Material To AI Skill Conversion Framework
MWMS Course Absorption Operating Rule
MWMS AI Brain Readiness Review Checklist
MWMS AI Output Validation Standard
MWMS Brain Routing Rule
MWMS MCR Promotion To Brain Protocol
MWMS Architecture Registry
AI Business Systems Brain Canon
This checklist provides the source-evidence intake layer before extraction, context construction, skill conversion, and asset creation.
Drift Protection
This checklist protects MWMS from:
empty-context builds
hidden evidence gaps
raw material misuse
weak source overreach
client material leakage
unsupported proof
course over-absorption
technical guessing
AI Employees building from assumptions
context libraries built from incomplete evidence
Any major build that begins without source material intake should be treated as an evidence drift risk.
Architectural Intent
The architectural intent of the MWMS Source Material Intake And Evidence Inventory Checklist is to make source truth visible before AI work begins.
MWMS is not building from vague prompts.
MWMS is building from evidence, context, and structured intelligence.
The long-term goal is that every serious build can answer:
What source material exists?
Where did it come from?
What category is it?
How strong is the evidence?
What can it support?
What can it not support?
What is missing?
What needs review?
What should be extracted?
What should be ignored?
What should be parked?
When MWMS can answer these questions consistently, AI work becomes more grounded, more accurate, easier to govern, and safer to scale.
Change Log
v1.0 — Initial Draft
Created the MWMS Source Material Intake And Evidence Inventory Checklist as the checklist for gathering, classifying, assessing, and inventorying source material before IP excavation, context library construction, skill creation, asset creation, course absorption, client Brain onboarding, and future AIBS system work.
This checklist defines source material categories, intake checks, evidence inventory templates, evidence strength levels, evidence status labels, source handling rules, intake outcomes, intake workflow, failure modes, governance role, drift protection, and architectural intent.
Change Impact Declaration
Pages Created:
MWMS Source Material Intake And Evidence Inventory Checklist
Pages Updated:
None
Pages Deprecated:
None
Registries Requiring Update:
MWMS Architecture Registry
HeadOffice Page Registry
AI Business Systems Brain Page Registry
Course Absorption Page Registry
Research Brain Page Registry
Compliance 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
Course Absorption Agent
Context Library Builder
Client IP Excavator
Content Planner Employee
Offer Strategist Employee
Creative Strategist Employee
Sales Strategist Employee
Research Analyst Employee
Compliance Reviewer Employee
AI Business Systems Architect Employee
Developer Support Agent
Required behaviour updates:
AI Employees must identify and classify source material before major extraction, context construction, skill conversion, asset creation, course absorption, or client Brain build work.
AI Employees must distinguish raw source material from approved active context.
AI Employees must mark evidence strength and identify what each source can and cannot support.
AI Employees must flag missing source material, weak evidence, client approval requirements, proof gaps, technical evidence gaps, and course transcription needs before producing high-value outputs.
AI Employees must route source material to the correct next step: IP Excavation, Context Library Build, Course Absorption, Skill Conversion, Asset Build, Parking, Ignore, or Review.
END MWMS SOURCE MATERIAL INTAKE AND EVIDENCE INVENTORY CHECKLIST v1.0