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, Conversion 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 Minimum Viable Context Library Rule.
This rule establishes the minimum context required before MWMS allows AI Employees, Brains, skills, tools, or manual workflows to create meaningful business outputs.
MWMS must not wait for perfect context before doing useful work.
But MWMS must also not create serious outputs from empty context.
This rule defines the difference between:
no context
minimum draft context
manual-use context
assisted-use context
operational context
client-ready context
The goal is to give MWMS a practical threshold system so AI work can begin safely without pretending incomplete context is complete.
Without this rule, MWMS risks two opposite problems:
waiting too long before creating useful drafts
creating business assets too early from weak context
The Minimum Viable Context Library Rule creates a clear middle path.
Scope
This rule applies to all MWMS work where AI requires business, offer, client, buyer, voice, proof, methodology, or workflow context before creating output.
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 rule applies before creating:
MCR pages
context libraries
AI Employee tasks
skills
content assets
sales assets
lead magnets
webinars
landing pages
sales pages
emails
VEO3 scripts
ad scripts
affiliate bridge pages
client reports
client Brain systems
future AIBS deliverables
This rule does not authorize development work, plugin changes, Supabase changes, WordPress changes, automation wiring, client implementation, publishing, paid traffic deployment, or M developer action.
Core Definition
A Minimum Viable Context Library is the smallest usable set of context files or context notes required for a specific level of AI work.
It is not the full context library.
It is not perfect.
It is the minimum safe foundation for controlled work.
A Minimum Viable Context Library may include:
buyer summary
offer summary
voice notes
core methodology
main objections
approved or missing proof status
differentiation notes
forbidden language
risk notes
human review requirement
The exact minimum depends on the output risk.
Core Principle
The core principle of this rule is:
Use enough context to do the work safely, and clearly mark what level of use the context supports.
MWMS can create drafts from partial context.
MWMS cannot treat partial context as operational truth.
The context level must match the output level.
Context Readiness Levels
MWMS uses six context readiness levels.
Level 0: No Usable Context
Level 1: Discovery Context
Level 2: Draft Context
Level 3: Manual-Use Context
Level 4: Assisted-Use Context
Level 5: Operational Context
Level 6: Client-Ready Context
Each level defines what work is allowed.
Level 0: No Usable Context
Definition
No reliable buyer, offer, voice, proof, methodology, or source material exists.
Allowed Use
general discussion
clarifying questions
source material request
idea parking
early discovery only
Not Allowed
asset creation
MCR page creation
client-facing output
public-facing output
paid traffic output
automation
skill installation
operational use
Required Action
Gather source material or ask clarifying questions.
Level 1: Discovery Context
Definition
Some rough source material or user explanation exists, but it has not been structured.
Allowed Use
brainstorming
gap identification
source review
intake questions
rough direction
early opportunity spotting
Not Allowed
approved assets
public copy
client output
paid traffic assets
formal skill creation
operational context use
Required Action
Run IP Excavation, source review, or intake.
Level 2: Draft Context
Definition
A rough buyer, offer, voice, methodology, or workflow understanding exists, but it is incomplete or unapproved.
Allowed Use
draft outlines
internal brainstorming
early page drafts
rough asset drafts
manual exploration
gap mapping
Not Allowed
canon promotion
client-facing output
public-facing output
paid traffic use
automation
claims-heavy output
Required Action
Mark output as Draft Only and identify gaps.
Level 3: Manual-Use Context
Definition
The core context is clear enough for human-reviewed manual work.
Minimum Requirements
buyer summary
offer summary
basic voice notes
main problem
main outcome
main objections
known proof status
human review requirement
Allowed Use
manual asset drafts
MCR draft pages
internal reports
manual content planning
manual lead magnet drafts
manual webinar drafts
manual offer review
Not Allowed
unreviewed public use
unreviewed client delivery
automation
paid traffic deployment
final claims-heavy sales assets
Required Action
Human review before use beyond draft.
Level 4: Assisted-Use Context
Definition
The context library is structured enough for repeated AI-assisted workflows with validation.
Minimum Requirements
Right-Fit Client Profile
Offer Profile
Voice Architecture
Differentiation Profile
Objection Library
Proof status
Retired Language where relevant
relevant standards
validation rules
Allowed Use
AI-assisted content creation
AI-assisted sales asset drafts
AI-assisted lead magnet creation
AI-assisted webinar creation
AI-assisted offer evaluation
AI-assisted client report drafts
skill-supported workflows
Not Allowed
unsupervised automation
unreviewed high-risk public assets
unreviewed client-facing final outputs
unsupported claims
Required Action
Validate output against context and route for review where needed.
Level 5: Operational Context
Definition
The context library is approved, structured, current, and usable for active internal MWMS workflows.
Minimum Requirements
approved Right-Fit Client Profile
approved Offer Profile
approved Voice Architecture
approved Differentiation Profile
approved Objection Library
approved Methodology Map
approved Expert Thinking Rules where needed
approved or clearly limited Proof Library
Retired Language
Compliance Notes where needed
known update triggers
audit path
Allowed Use
active internal AI Employee workflows
approved context-driven asset creation
active skill usage
repeatable internal outputs
operational Brain workflows
Not Allowed
client-facing use unless client-ready
automation without separate readiness review
paid traffic deployment without Ads and Compliance review
Required Action
Use active context, validate outputs, and audit over time.
Level 6: Client-Ready Context
Definition
The context library is approved for future client-facing or AIBS client system use.
Minimum Requirements
client-approved business context
client-approved buyer profile
client-approved offer profile
client-approved voice architecture
client-approved methodology
client-approved proof library or proof limits
client-approved approval rules
client workflow map
client risk notes
client privacy boundary
client review pathway
audit schedule
Allowed Use
client-facing drafts
client reports
client AI-assisted workflows
future AIBS deliverables
client context-driven assets
Not Allowed
unreviewed automation
tool access without permission
cross-client reuse
public claims without compliance review
Required Action
Maintain client isolation, review output, and audit regularly.
Minimum Context By Output Type
Different outputs require different minimum context.
MCR Page Draft
Minimum:
source material
MWMS document structure
owning Brain
purpose
scope
rules
governance role
drift protection
architectural intent
change log
Allowed Level:
Manual-Use Context or higher
Lead Magnet Draft
Minimum:
buyer
problem
quick win
offer bridge
voice notes
next step
Allowed Level:
Manual-Use Context or higher
Evergreen Webinar Draft
Minimum:
buyer
offer
current belief
new belief
methodology
objections
CTA
Allowed Level:
Manual-Use Context or higher
Sales Page Draft
Minimum:
buyer
offer
differentiation
objections
proof status
voice
compliance notes where relevant
Allowed Level:
Assisted-Use Context or higher
Paid Ad Script
Minimum:
buyer
offer
angle
proof limits
retired language
compliance notes
platform constraints
Allowed Level:
Assisted-Use Context with Ads and Compliance review
Client Report Draft
Minimum:
client context
client approval rules
report objective
source data
proof or performance data status
privacy boundary
Allowed Level:
Client-Ready Context or reviewed draft context
Developer Handoff
Minimum:
current file path
current file contents or screenshot
exact issue
exact desired outcome
what not to touch
test steps
rollback or safety note where relevant
Allowed Level:
Technical evidence required
General context is not enough.
AI Skill Draft
Minimum:
task
trigger
input
context
procedure
output
validation
handoff
forbidden actions
Allowed Level:
Manual-Use Context or higher
AI Skill Installation
Minimum:
skill record
owning Brain
assigned AI Employee
trigger conditions
input
context
validation
review requirement
handoff destination
Allowed Level:
Assisted-Use Context or higher
Context Level Decision Workflow
MWMS uses the following workflow to determine context level.
Step 1: Identify The Output
Define what is being created.
Step 2: Identify The Risk
Determine whether the work is internal, public, client-facing, compliance-sensitive, paid traffic, finance-related, or developer-related.
Step 3: Identify Existing Context
Check which context files or notes exist.
Step 4: Assign Context Level
Choose Level 0 through Level 6.
Step 5: Decide Allowed Work
Determine what can safely proceed.
Step 6: Mark Missing Context
Use the Missing Context And Evidence Gap Handling Rule.
Step 7: Proceed, Pause, Park, Or Stop
Choose the correct action path.
Step 8: Record Upgrade Needs
Identify what context must be added to reach the next level.
Context Upgrade Paths
Context can be upgraded over time.
Level 0 To Level 1
Gather source material or initial explanation.
Level 1 To Level 2
Extract rough buyer, offer, voice, and problem notes.
Level 2 To Level 3
Create enough structure for human-reviewed manual work.
Level 3 To Level 4
Build core context files and validation rules.
Level 4 To Level 5
Approve files, add proof limits, retired language, compliance notes, and audit path.
Level 5 To Level 6
Add client approval, client isolation, client workflow map, client review rules, and client audit schedule.
Minimum Viable Context Template
Use this template for early-stage context.
Context Name:
Context Level:
Owning Brain:
Offer Or System:
Buyer Summary:
Offer Summary:
Main Problem:
Desired Outcome:
Core Methodology:
Differentiation Notes:
Top Objections:
Voice Notes:
Proof Status:
Retired Language:
Compliance Notes:
Missing Context:
Allowed Use:
Not Allowed:
Human Review Required:
Next Upgrade Needed:
Notes:
Quick Context Level Template
Use this for fast decisions.
Task:
Current Context Level:
Allowed Use:
Missing Context:
Risk:
Decision:
Next Action:
Context Level Rules
Rule 1: Do Not Pretend Draft Context Is Operational
Draft context must remain draft.
Rule 2: Match Context Level To Output Risk
Higher-risk output requires stronger context.
Rule 3: Use Manual Work Before Assisted Work
Manual-reviewed output helps refine context.
Rule 4: Do Not Automate From Minimum Context
Automation requires separate readiness review.
Rule 5: Client Use Requires Client Context
Internal MWMS context cannot substitute for client-approved context.
Rule 6: Proof Limits Must Be Clear Before Public Claims
If proof is missing, claims must be limited or removed.
Rule 7: Context Can Improve Through Use
Manual outputs may reveal missing context that should update the library.
Rule 8: Context Level Must Be Visible
AI Employees should state context level where it affects output reliability.
Common Failure Modes
MWMS must prevent:
building from no context
using draft context as approved
waiting for perfect context when a draft would be useful
creating public assets from discovery context
using internal context for client outputs
using buyer assumptions as buyer evidence
making claims before proof exists
creating skills before context exists
automating from partial context
forgetting to upgrade context after repeated use
Governance Role
HeadOffice owns the MWMS Minimum Viable Context Library Rule.
HeadOffice is responsible for:
defining context readiness levels
preventing premature context activation
allowing useful draft work without false approval
ensuring context level matches output risk
ensuring missing context is labelled
ensuring client-ready context remains separate
ensuring automation is not implied by context readiness
Individual Brains are responsible for applying the rule inside their domain.
Offer Brain governs offer context readiness.
Content Brain governs content context readiness.
Sales Brain governs sales context readiness.
Creative Brain governs creative context readiness.
Compliance Brain governs claims-sensitive readiness.
AI Business Systems Brain governs future client context readiness.
Relationship To Other MWMS Standards
This rule supports and must align with:
MWMS Document Structure Standard
MWMS Missing Context And Evidence Gap Handling Rule
MWMS AI Brain Readiness Review Checklist
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 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 AI Skill Builder And Audit Protocol
MWMS AI Skill Installation And Usage Protocol
MWMS AI Brain Audit And Decay Prevention Framework
MWMS Brain Routing Rule
MWMS MCR Promotion To Brain Protocol
MWMS Architecture Registry
AI Business Systems Brain Canon
This rule defines the minimum context threshold that sits before activation, asset creation, skill use, and client deployment.
Drift Protection
This rule protects MWMS from:
empty-context output
draft-context overreach
premature activation
public output from weak source
client output from internal assumptions
automation from partial context
claims without proof
skills without context
AI Employees overstating readiness
Any AI output created without a context level matching its risk should be treated as a readiness drift risk.
Architectural Intent
The architectural intent of the MWMS Minimum Viable Context Library Rule is to let MWMS move quickly without sacrificing governance.
MWMS does not need perfect context to begin useful draft work.
But MWMS does need clear context levels to prevent weak context from becoming active truth.
The long-term goal is that every context-dependent AI task can answer:
What context level exists?
What work is allowed?
What work is not allowed?
What context is missing?
What review is required?
What risk exists?
What must be upgraded next?
When MWMS can answer these questions consistently, it can build faster while still protecting quality, source truth, and future client safety.
Change Log
v1.0 — Initial Draft
Created the MWMS Minimum Viable Context Library Rule as the rule for defining context readiness levels and minimum context thresholds before AI Employees create draft, manual-use, assisted-use, operational, or client-ready outputs.
This rule defines context readiness levels, allowed uses, minimum requirements, output-specific minimum context, decision workflow, upgrade paths, templates, rules, failure modes, governance role, drift protection, and architectural intent.
Change Impact Declaration
Pages Created:
MWMS Minimum Viable Context Library Rule
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
Sales Brain Page Registry
Creative 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
Client IP Excavator
Course Absorption Agent
Offer Strategist Employee
Content Planner Employee
Creative Strategist Employee
Sales Strategist Employee
Conversion Strategist Employee
Compliance Reviewer Employee
AI Business Systems Architect Employee
Required behaviour updates:
AI Employees must identify whether available context is no usable context, discovery context, draft context, manual-use context, assisted-use context, operational context, or client-ready context.
AI Employees must match output risk to required context level before producing high-value outputs.
AI Employees must not treat draft context as operational source truth or client-ready context.
AI Employees must flag missing context and define what must be upgraded before stronger use is allowed.
AI Employees must support useful draft work while preventing premature public-facing, client-facing, paid traffic, automation, or canon-level use.
END MWMS MINIMUM VIABLE CONTEXT LIBRARY RULE v1.0