System: MWMS
Document Type: Rule
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, Compliance 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 Missing Context And Evidence Gap Handling Rule.
This rule establishes how MWMS AI Employees must behave when required context, source material, proof, buyer language, offer detail, methodology, client approval, or evidence is missing.
MWMS must not allow AI Employees to fill gaps with confident-sounding assumptions.
A missing context gap is not an invitation to invent.
A missing evidence gap is a signal to pause, label, ask, park, or continue only in draft mode.
This rule exists because AI systems often produce polished output even when the underlying source is incomplete.
That is dangerous for MWMS.
When context is missing, AI may invent:
buyer pain
proof
offer promises
customer language
testimonials
client preferences
methodology
expert judgment
financial assumptions
compliance safety
technical state
developer instructions
This rule prevents MWMS from scaling unsupported assumptions into pages, assets, client systems, ads, reports, skills, or future AI Employee behaviour.
Scope
This rule applies to all MWMS work where AI uses context, source material, evidence, memory, user instruction, uploaded files, client data, course material, or prior system knowledge.
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
Finance Brain
Operations Brain
future AIBS client systems
This rule applies before creating or reviewing:
MCR pages
context libraries
skills
AI Employee instructions
content assets
sales assets
lead magnets
webinars
ads
VEO3 scripts
affiliate bridge pages
client reports
developer handoffs
financial summaries
compliance-sensitive outputs
public-facing assets
client-facing systems
This rule does not authorize development work, plugin changes, Supabase changes, WordPress changes, automation wiring, publishing, client implementation, or M developer action.
Core Definition
A Missing Context Gap occurs when required information is not available, not approved, not current, not specific enough, or not clearly tied to source material.
An Evidence Gap occurs when a claim, decision, recommendation, output, proof point, or business conclusion lacks enough support from approved source material.
A gap may appear in:
buyer profile
offer profile
voice architecture
methodology
expert thinking
proof library
customer language
objections
differentiation
retired language
compliance notes
technical state
client approval
financial assumptions
course absorption value
developer instructions
A gap must be marked, not hidden.
Core Principle
The core principle of this rule is:
When context is missing, mark the gap. Do not invent the answer.
AI Employees must prefer honest incompleteness over polished fiction.
MWMS can work with gaps if they are visible.
MWMS cannot govern hidden assumptions.
Gap Types
MWMS recognizes several types of missing context and evidence gaps.
- Source Material Gap
Required source material is missing.
Examples:
no transcript
no sales page
no client notes
no offer document
no customer language
no screenshots
no current file contents
- Buyer Gap
The buyer is unclear.
Examples:
no defined audience
too many buyer types mixed
buyer sophistication unknown
no customer language
no known objections
- Offer Gap
The offer is unclear.
Examples:
unclear promise
unclear delivery model
unclear inclusions
unclear pricing
unclear next step
unclear limitations
- Proof Gap
The claim has no approved proof.
Examples:
no testimonial
no case study
no verified result
no approved data
no vendor-approved claim
- Voice Gap
The brand or founder voice is unclear.
Examples:
no writing samples
no voice architecture
no preferred phrases
no banned phrases
no examples of wrong voice
- Methodology Gap
The process is unclear.
Examples:
no step sequence
no named method
no delivery logic
no transformation path
no first move
- Expert Thinking Gap
The judgment logic is missing.
Examples:
no diagnostic rules
no decision branches
no if/then logic
no escalation rules
no quality thresholds
- Compliance Gap
Risk constraints are unknown.
Examples:
unknown claim restrictions
unknown platform rules
unknown affiliate limitations
unknown health, finance, or income sensitivity
- Client Approval Gap
Client-owned material has not been approved.
Examples:
client proof not approved
client voice not approved
client report not reviewed
client context not confirmed
- Technical State Gap
The actual system state is unknown.
Examples:
unknown file contents
unknown plugin state
unknown database schema
unknown current code
unknown Make.com setup
unknown WordPress page state
- Course Value Gap
Course material is incomplete or not strong enough to justify absorption.
Examples:
sales page hype only
missing videos
missing transcripts
weak worksheet
no unique system value
- Timing Gap
The material may be useful later but not now.
Examples:
future AIBS feature
future client workflow
future automation candidate
future tool integration
Gap Handling Labels
MWMS uses clear labels when context is missing.
Missing Context
Required context does not exist or has not been provided.
Missing Evidence
A claim or recommendation lacks source support.
Needs Source Material
More source material is needed before proceeding.
Needs Human Review
Human review is required before using the output.
Needs Client Review
Client-owned context or output requires client approval.
Needs Compliance Review
The output or claim may be compliance-sensitive.
Needs Technical Confirmation
The current technical state must be confirmed before giving instructions.
Needs Offer Clarification
The offer is not clear enough.
Needs Buyer Clarification
The buyer is not clear enough.
Needs Proof
Proof is required before using the claim.
Draft Only
Output may be created for exploration but must not be treated as approved.
Park For Later
The idea may be useful later but should not be acted on now.
Gap Handling Rules
Rule 1: Do Not Invent
If the information is missing, do not create it.
Rule 2: Label The Gap Clearly
Use the correct gap label.
Rule 3: Continue Only In The Correct Mode
Some gaps allow draft work.
Some gaps require stopping.
Some gaps require review.
Rule 4: Ask Only When Needed
If the missing context blocks the task, ask for clarification.
If the gap can be marked and the work can continue as draft, continue with clear limits.
Rule 5: Do Not Upgrade Draft Work
Draft output created with missing context cannot become active until the gap is resolved.
Rule 6: Do Not Hide Assumptions
If an assumption is made, state it clearly.
Rule 7: Do Not Use Missing Proof As Soft Proof
Absence of proof must not become vague credibility language.
Rule 8: Do Not Treat Memory As Evidence
Memory may guide, but approved source context beats memory.
Rule 9: Do Not Build Client Systems On Unapproved Context
Client systems require client review where relevant.
Rule 10: Do Not Give Developer Instructions From Unknown State
If current file contents or system state are unknown, ask for the file, screenshot, or current code before giving exact instructions.
Proceed, Pause, Park, Or Stop
MWMS uses four action paths when context is missing.
Proceed In Draft Mode
Use when enough context exists to create a useful draft, but not enough for approval.
Example:
A lead magnet idea can be drafted from partial buyer context, but must be marked Draft Only.
Pause And Ask
Use when the missing context blocks the task.
Example:
Cannot create exact developer instructions without the current file contents.
Park For Later
Use when the idea may be useful but is premature.
Example:
A future client skill idea with no active client workflow yet.
Stop And Reject
Use when continuing would create false, unsafe, or low-value output.
Example:
Creating testimonials, income claims, or client results without proof.
Draft Mode Rules
Draft Mode allows MWMS to explore ideas while protecting source truth.
Draft Mode is acceptable when:
context is partial
the output is internal
the task is exploratory
human review is expected
no public or client-facing use is implied
risk is low or controlled
Draft Mode is not acceptable for:
paid traffic claims
client-facing reports
public sales pages
developer instructions
financial recommendations
compliance-sensitive claims
MCR canon promotion
automation decisions
Draft Mode outputs must be clearly marked.
Use:
Status: Draft Only
Reason: Missing Context
Human Review Required: Yes
Evidence Gap Examples
Example 1: Proof Gap
Unsupported output:
This system has helped dozens of businesses improve AI output.
Correct handling:
Missing Evidence: no approved proof currently supports the claim that dozens of businesses improved AI output. Use process-based wording or provide proof before use.
Example 2: Buyer Gap
Unsupported output:
This is perfect for coaches, consultants, agencies, and ecommerce brands.
Correct handling:
Needs Buyer Clarification: buyer segments may differ. Define the primary buyer before creating high-value messaging.
Example 3: Technical State Gap
Unsupported output:
Replace this function in the plugin file.
Correct handling:
Needs Technical Confirmation: current file contents are required before giving exact replacement instructions.
Example 4: Client Approval Gap
Unsupported output:
Use this client testimonial on the landing page.
Correct handling:
Needs Client Review: testimonial usage requires client approval before public use.
Example 5: Course Value Gap
Unsupported output:
This course should create a new MWMS page.
Correct handling:
Course Value Gap: material appears useful but not yet superior. Park until transcripts or stronger templates are available.
Missing Context In Course Absorption
During course absorption, AI Employees must not assume every course file is valuable.
If course material is weak, shallow, duplicated, or incomplete, mark it.
Possible outcomes:
Absorb Now
Merge Into Existing Page
Update Existing Standard
Park For Later
Ignore
Needs Video Transcript
Needs More Source Material
If a PDF or sales page suggests value but the videos likely contain the real substance, mark:
Needs Video Transcript
Do not over-absorb from thin sales material.
Missing Context In Client Systems
Future AIBS client systems must handle gaps carefully.
If client source material is missing, mark it.
If client voice is unclear, ask for samples.
If proof is unapproved, do not use it.
If client workflows are unclear, do not automate.
If approval rules are unknown, require review.
Client gap labels may include:
Needs Client Source Material
Needs Client Voice Samples
Needs Client Offer Clarification
Needs Client Proof Approval
Needs Client Workflow Mapping
Needs Client Review
Needs Client Permission Boundary
Missing Context In Asset Creation
Before creating business assets, check for missing context.
Lead Magnet
Needs:
buyer
problem
quick win
offer bridge
voice
next step
Webinar
Needs:
buyer
current belief
new belief
methodology
objections
proof
CTA
Sales Page
Needs:
offer
buyer
differentiation
objections
proof
voice
compliance notes
Ad Script
Needs:
buyer
angle
offer promise
proof limits
compliance notes
retired language
If key context is missing, proceed only in Draft Mode or ask for clarification.
Missing Context In Developer Handoffs
Developer instructions require current evidence.
AI Employees must not give exact code-edit instructions unless they have:
current file path
current file contents or screenshot
exact target section
desired outcome
what not to touch
test steps
rollback or safety note where relevant
If those are missing, mark:
Needs Technical Confirmation
Do not guess.
Missing Context In Proof And Claims
If proof is missing, AI Employees must use one of the following actions:
remove claim
soften claim
mark proof needed
use process-based wording
request proof
route to Compliance Brain
park output
No AI Employee may invent proof to make copy stronger.
Missing Context In Voice
If voice is unclear, AI Employees may draft neutral operational output, but must not claim it matches founder voice.
Use:
Needs Voice Samples
Needs Voice Architecture
Draft Only
Human Review Required
For MCR pages, operational clarity is preferred over stylized voice.
For client-facing or public-facing work, voice must be reviewed.
Missing Context In Research
If facts may have changed, or if a claim requires current evidence, Research Brain must verify.
If verification is not possible inside the current workflow, mark:
Needs Research Verification
Do not present unstable facts as final.
Missing Context In Compliance
If an output touches claims, ads, affiliate, health, finance, privacy, income, testimonials, or regulated topics, and compliance context is missing, mark:
Needs Compliance Review
Do not proceed as final.
Missing Context Decision Template
Use the following template.
Task:
Missing Context Type:
Missing Item:
Why It Matters:
Risk If Invented:
Can Proceed In Draft Mode:
Required Action:
Human Review Required:
Recommended Next Step:
Notes:
Minimum Gap Template
For quick use:
Gap:
Why It Matters:
Action:
Status:
Review Required:
Gap Severity Levels
Low Gap
Minor missing detail.
Can proceed in draft mode.
Medium Gap
Important missing context but not high-risk.
Proceed only with clear label or ask for clarification.
High Gap
Missing context affects accuracy, client output, public output, paid traffic, compliance, or source truth.
Pause or require review.
Critical Gap
Continuing would likely create false, risky, harmful, misleading, or technically wrong output.
Stop.
Gap Resolution Outcomes
A gap may be resolved by:
source material provided
human answer received
client approval received
proof added
context library updated
voice file created
offer clarified
buyer clarified
technical file confirmed
compliance reviewed
research verified
task parked
task rejected
Gap Resolution Rule
Once a gap is resolved, update the relevant context library, standard, skill, or registry where appropriate.
Do not resolve gaps only inside chat if the learning should become reusable.
Common Failure Modes
MWMS must prevent:
AI inventing missing proof
AI inventing buyer language
AI inventing client preferences
AI inventing methodology
AI assuming technical state
AI creating confident copy from weak context
draft outputs becoming canon
course material over-absorbed from thin source
client systems built before client approval
ads created without proof or compliance context
developer instructions guessed from memory
gaps being hidden inside polished output
Governance Role
HeadOffice owns the MWMS Missing Context And Evidence Gap Handling Rule.
HeadOffice is responsible for:
requiring gaps to be labelled
preventing invention
preventing draft outputs from becoming active
ensuring high-risk gaps pause work
ensuring missing context routes to the correct Brain
ensuring resolved gaps update source truth where appropriate
Individual Brains are responsible for handling missing context inside their own domain.
Offer Brain handles offer gaps.
Content Brain handles content and voice gaps.
Sales Brain handles objection and sales gaps.
Creative Brain handles creative context gaps.
Research Brain handles evidence and current-fact gaps.
Compliance Brain handles claim and policy gaps.
AI Business Systems Brain handles client system gaps.
Dev-related gaps require current technical evidence before instruction.
Relationship To Other MWMS Standards
This rule 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 Context Pack Template Standard
MWMS Context-Driven Asset Builder Framework
MWMS Right-Fit Client And Offer Profile Standard
MWMS Differentiation And Objection Library Standard
MWMS Proof Library And Claims Control Standard
MWMS Voice Architecture And Brand Language Standard
MWMS Context Library Hygiene And Retired Language Rule
MWMS AI Brain Readiness Review Checklist
MWMS AI Brain Audit And Decay Prevention Framework
MWMS AI Output Validation Standard
MWMS Course Absorption Operating Rule
MWMS Brain Routing Rule
MWMS MCR Promotion To Brain Protocol
MWMS Architecture Registry
AI Business Systems Brain Canon
This rule provides the gap-handling layer that prevents AI Employees from turning missing information into false certainty.
Drift Protection
This rule protects MWMS from:
hidden assumptions
invented proof
invented buyer language
invented client context
invented methodology
unsupported claims
technical guessing
draft material becoming canon
course over-absorption
client systems built too early
public assets built from incomplete context
AI Employees sounding confident while source truth is missing
Any high-value output that contains unlabelled missing context should be treated as a drift risk.
Architectural Intent
The architectural intent of the MWMS Missing Context And Evidence Gap Handling Rule is to make uncertainty visible and governable.
MWMS does not need every answer immediately.
It does need to know what is missing.
The long-term goal is that every AI Employee can answer:
What context is missing?
Why does it matter?
Can we proceed in draft mode?
Do we need to pause?
Do we need human review?
Do we need source material?
Do we need proof?
Do we need client approval?
Do we need research?
Do we need compliance review?
Should this be parked?
When MWMS can answer these questions consistently, the ecosystem becomes more honest, safer, more accurate, and easier to scale.
Change Log
v1.0 — Initial Draft
Created the MWMS Missing Context And Evidence Gap Handling Rule as the rule for identifying, labelling, routing, and resolving missing context, missing evidence, weak source material, incomplete buyer detail, unclear offer information, unapproved proof, client approval gaps, compliance gaps, technical state gaps, and course value gaps.
This rule defines gap types, gap labels, handling rules, draft mode rules, examples, application to course absorption, client systems, asset creation, developer handoffs, proof, voice, research, compliance, templates, severity levels, resolution outcomes, failure modes, governance role, drift protection, and architectural intent.
Change Impact Declaration
Pages Created:
MWMS Missing Context And Evidence Gap Handling Rule
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
Sales Brain Page Registry
Creative Brain 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
Offer Strategist Employee
Content Planner 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 label missing context and evidence gaps instead of inventing unsupported information.
AI Employees must distinguish between draft mode, pause-and-ask, park-for-later, and stop-and-reject decisions when gaps appear.
AI Employees must not create proof, testimonials, buyer language, client preferences, methodology, technical state, or claims from assumptions.
AI Employees must route high-risk gaps to the correct review path before producing public-facing, client-facing, paid traffic, compliance-sensitive, financial, or developer-related outputs.
AI Employees must update relevant context libraries, standards, skills, or registries when important gaps are resolved.
END MWMS MISSING CONTEXT AND EVIDENCE GAP HANDLING RULE v1.0