System: MWMS
Document Type: Protocol
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 Context File Promotion And Approval Protocol.
This protocol establishes how MWMS decides when raw material, draft notes, extracted insights, course findings, client documents, AI outputs, skill drafts, or asset learnings may be promoted into active context.
MWMS must not treat every useful note as source truth.
A file becomes active context only after it has been reviewed, classified, structured, and approved for use.
This protocol exists because MWMS will constantly produce and receive material from:
course absorption
client intake
content scanning
newsletter analysis
offer research
sales asset creation
lead magnet creation
webinar creation
AI skill creation
Brain Room discussions
AI Employee output
client documents
workflow testing
Not all of that material should become active context.
Some material should remain raw.
Some should remain draft.
Some should be parked.
Some should be archived.
Some should be rejected.
Some should update an existing context file.
Some should become a new context file.
The Context File Promotion And Approval Protocol prevents weak, duplicated, unsupported, stale, or unreviewed material from entering the MWMS source-of-truth layer.
Scope
This protocol applies to all MWMS context promotion, demotion, approval, rejection, parking, archive, and source-of-truth update decisions.
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 protocol applies when MWMS needs to decide whether material should become:
active context
draft context
MCR page
context library file
skill record
AI Employee instruction
proof item
voice rule
retired language
offer profile update
buyer profile update
objection library update
methodology update
expert thinking rule
client context
archive item
parked item
rejected item
This protocol does not authorize development work, plugin changes, Supabase changes, WordPress changes, automation wiring, publishing, file deletion, client implementation, or M developer action.
Core Definition
Context File Promotion is the process of moving material from a lower authority state into a higher authority state.
Examples:
raw material becomes extracted insight
extracted insight becomes draft context
draft context becomes approved context
approved context becomes active source truth
course insight becomes MCR page
asset learning updates a context file
client material becomes client-approved context
Context File Approval is the human or governance decision that confirms a file or insight is safe to use as source truth for AI Employees.
Core Principle
The core principle of this protocol is:
Useful material is not automatically approved context.
Promotion requires evidence, structure, review, and destination.
MWMS must protect the difference between:
raw material
working notes
AI drafts
extracted insights
draft context
approved context
active source truth
archived reference
retired material
If this distinction collapses, AI Employees will not know what to trust.
Context Authority Levels
MWMS uses the following context authority levels.
Level 0: Raw Material
Unprocessed source material.
Examples:
transcripts
screenshots
emails
sales pages
client notes
course PDFs
voice memos
Raw material may contain useful evidence, but it is not active context.
Level 1: Extracted Insight
A useful point has been pulled from raw material.
Examples:
buyer phrase
objection
methodology step
founder belief
proof candidate
voice phrase
Extracted insight still requires review before active use.
Level 2: Draft Context
The insight has been structured into a context format but is not approved.
Examples:
draft Offer Profile
draft Voice Architecture
draft Objection Library
draft Proof Library
Draft context can support internal exploration but not final use.
Level 3: Reviewed Context
A human operator, Brain owner, or relevant reviewer has checked the context.
Reviewed context may still need final approval depending on risk.
Level 4: Approved Context
The file or insight is approved for defined use.
Examples:
approved buyer profile
approved offer profile
approved proof item
approved retired language
Approved context may be used according to its restrictions.
Level 5: Active Source Truth
The context is the current authoritative source for the relevant Brain, offer, client, workflow, or system.
AI Employees may use it as active context.
Level 6: Canon Context
The context has MCR or canon-level authority.
This applies to standards, protocols, frameworks, rules, and permanent governance pages.
Promotion Path
The standard promotion path is:
Raw Material
Extracted Insight
Draft Context
Reviewed Context
Approved Context
Active Source Truth
Canon Context where applicable
Not every item needs to reach Canon Context.
Most material should not.
Promotion should match the material’s role.
Promotion Decision Questions
Before promoting material, ask:
What is this material?
Where did it come from?
What does it support?
What does it not support?
Is it specific?
Is it current?
Is it source-grounded?
Is it duplicated elsewhere?
Does it belong in an existing file?
Does it require a new file?
Does it require human review?
Does it require client review?
Does it require compliance review?
Does it affect public-facing output?
Does it affect client-facing output?
Does it affect paid traffic?
Does it affect MCR governance?
Is it strong enough to become active context?
Promotion Outcomes
MWMS uses the following promotion outcomes.
Promote To Existing Context File
Use when the material improves an existing context file.
Examples:
new objection
new buyer phrase
new retired language
new proof item
new voice example
Create New Context File
Use when the material introduces a new required context area.
Examples:
new Voice Architecture
new Proof Library
new Client Approval Rules
Create MCR Page
Use when the material creates durable MWMS governance, framework, protocol, rule, standard, or checklist value.
Create Skill Record
Use when the material defines repeatable procedure.
Create Checklist
Use when the material defines review criteria.
Park For Later
Use when the material may be useful but timing, context, or ownership is not ready.
Archive
Use when the material should be preserved but not active.
Reject
Use when the material is weak, duplicated, unsupported, risky, or not useful.
Needs More Evidence
Use when the material may be valuable but lacks enough support.
Needs Human Review
Use when human judgment is needed before promotion.
Needs Client Review
Use when client-owned context requires approval.
Needs Compliance Review
Use when claims, proof, ads, health, finance, affiliate, privacy, or risk-sensitive material is involved.
Promotion Criteria
Material may be promoted when it meets the correct criteria.
Specificity
The material must be specific enough to guide AI Employees.
Source Grounding
The material must be tied to source evidence or approved human judgment.
Relevance
The material must support a real MWMS Brain, offer, client, skill, workflow, or asset.
Non-Duplication
The material must not duplicate existing active context unless it is an update.
Currentness
The material must not be stale or outdated.
Governance Fit
The material must belong in the correct Brain, file, folder, or registry.
Risk Review
High-risk material must be reviewed before promotion.
Operational Usefulness
The material should improve future AI output, decision-making, validation, or workflow quality.
Promotion Blockers
Material must not be promoted when:
source is unclear
proof is missing
buyer is assumed
offer is unclear
client approval is missing
compliance risk is unresolved
technical state is unknown
material duplicates an existing file
material is too generic
material is weak
material is stale
material belongs in archive
material belongs in Retired Language, not active messaging
material should update an existing file instead of creating a new one
material is interesting but not useful
Draft Context Approval Rules
Draft context may become approved context only when:
source is known
purpose is clear
owning Brain is clear
file destination is clear
missing evidence is labelled
proof status is clear
client boundary is clear where relevant
review requirement is satisfied
duplicate risk is checked
retired language is checked where relevant
human review is complete where required
Draft context cannot become active source truth just because it was well written.
AI output quality is not the same as approval.
MCR Page Promotion Rules
A draft page may be promoted toward MCR only when:
document type is clear
parent page is clear
authority level is clear
status is clear
purpose is clear
scope is clear
governance role is clear
drift protection is clear
architectural intent is clear
change log is included
change impact declaration is included
employee impact check is included
registry update requirement is identified
duplicate page risk is checked
A page drafted in chat is not the same as a saved MCR page.
Client Context Promotion Rules
Client material may become client context only when:
client source is identified
client ownership is clear
client approval requirement is known
client privacy boundary is clear
client context is isolated
client proof is approved or marked unapproved
client voice is reviewed
client offer details are confirmed
client workflow details are confirmed
client review path is defined
Client material must not be promoted into general MWMS context unless deliberately generalized and approved.
Proof Promotion Rules
Proof may be promoted only when:
source is known
claim supported is defined
claim not supported is defined
approval status is assigned
usage permission is clear
privacy risk is checked
client approval is checked where relevant
compliance risk is checked
paid traffic restriction is checked where relevant
No proof item should become active proof without classification.
Voice Promotion Rules
Voice material may be promoted only when:
source voice sample exists
founder voice is separated from customer language
preferred phrases are identified
banned phrases are identified
retired language candidates are identified
examples are included where useful
human review is completed
Voice is subjective.
Human review is required before voice becomes active context.
Objection Promotion Rules
An objection may be promoted when:
buyer source exists or assumption is marked
objection category is clear
underlying fear is identified where possible
best response is grounded
proof needed is clear
asset use is clear
bad-fit signal is considered
Objections should not be invented and treated as buyer truth.
Retired Language Promotion Rules
Language should be promoted to Retired Language when:
it is outdated
it caused risk
it no longer matches strategy
it is too generic
it is banned by founder or client
it caused platform issue
it has been replaced
it creates unsupported claim risk
Retired Language is active protection and should not be hidden only in archive.
Demotion Rules
Context may need to move down in authority.
Demotion may occur when:
context becomes stale
proof expires
offer changes
buyer changes
voice changes
client approval is withdrawn
compliance risk appears
duplicate context is discovered
better context replaces it
AI output reveals mismatch
Demotion outcomes:
Active to Draft
Active to Restricted
Active to Retired
Active to Archived
Approved to Needs Review
Approved to Rejected
Canon update required
Context demotion must be recorded when it affects active use.
Promotion Record Template
Use the following template.
Item Name:
Item Type:
Source:
Current Authority Level:
Proposed Authority Level:
Owning Brain:
Destination File Or Page:
What It Supports:
What It Does Not Support:
Evidence Strength:
Duplicate Risk Checked:
Client-Specific:
Proof Risk:
Compliance Risk:
Paid Traffic Risk:
Human Review Required:
Approval Decision:
Reason:
Next Action:
Registry Impact:
Notes:
Minimum Promotion Record
For quick decisions, use:
Item:
Source:
Promote To:
Reason:
Review Required:
Next Action:
Promotion Review Roles
Different material requires different reviewers.
HeadOffice Review
Required for cross-Brain, MCR, governance, or system-level material.
Offer Brain Review
Required for offer profile, differentiation, objections, methodology, and promise.
Content Brain Review
Required for voice, content patterns, content intelligence, and brand language.
Sales Brain Review
Required for sales scripts, objection handling, CTA logic, and buyer progression.
Research Brain Review
Required for evidence quality, market facts, external claims, and source validation.
Compliance Brain Review
Required for risky claims, ads, affiliate, health, finance, privacy, and platform-sensitive wording.
AI Business Systems Brain Review
Required for client systems, client context, client workflows, and future AIBS packaging.
Client Review
Required for client-owned context, client proof, client voice, and client-facing outputs.
Common Failure Modes
MWMS must prevent:
raw material becoming active context
AI drafts becoming source truth
draft context treated as approved
weak course material promoted too far
client material promoted into MWMS general context
proof promoted without claim boundaries
voice promoted without review
duplicate context promoted
retired language left in active messaging
archive material reused as current truth
page drafts treated as saved MCR pages
material promoted without registry impact
Governance Role
HeadOffice owns the MWMS Context File Promotion And Approval Protocol.
HeadOffice is responsible for:
defining promotion authority levels
preventing weak material from becoming source truth
ensuring review occurs before promotion
ensuring duplicate risk is checked
ensuring client context remains isolated
ensuring proof and claims are reviewed
ensuring MCR promotion requirements are met
ensuring demotion occurs when context becomes stale or risky
Individual Brains may approve domain-specific context within their authority, but HeadOffice governs cross-Brain, MCR, high-risk, and client-system promotion.
Relationship To Other MWMS Standards
This protocol supports and must align with:
MWMS Document Structure Standard
MWMS Source Material Intake And Evidence Inventory Checklist
MWMS Missing Context And Evidence Gap Handling Rule
MWMS Minimum Viable Context Library Rule
MWMS Context Library Hygiene And Retired Language Rule
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 Right-Fit Client And Offer Profile Standard
MWMS Voice Architecture And Brand Language Standard
MWMS Differentiation And Objection Library Standard
MWMS Proof Library And Claims Control Standard
MWMS AI Brain Readiness Review Checklist
MWMS AI Brain Audit And Decay Prevention Framework
MWMS Course Absorption Operating Rule
MWMS MCR Promotion To Brain Protocol
MWMS Page Naming Standard
MWMS Architecture Registry
AI Business Systems Brain Canon
This protocol defines the approval gate between raw material, draft context, and active source truth.
Drift Protection
This protocol protects MWMS from:
unreviewed source truth
raw material misuse
AI draft over-promotion
weak context activation
client context leakage
unsupported proof promotion
duplicate context files
stale files staying active
retired language remaining active
MCR draft confusion
high-risk material promoted without review
Any context file, page, proof item, or skill promoted without authority level, source, destination, review, and duplicate check should be treated as a promotion drift risk.
Architectural Intent
The architectural intent of the MWMS Context File Promotion And Approval Protocol is to keep MWMS source truth clean, trustworthy, and governed.
MWMS will continue producing a large amount of useful material.
The system must know what deserves promotion and what does not.
The long-term goal is that every promotion decision can answer:
What is being promoted?
Where did it come from?
What does it support?
What does it not support?
Who owns it?
Where will it live?
What authority level does it have?
What review is required?
Is it client-specific?
Is it duplicate?
Is it risky?
Should it be promoted, parked, archived, rejected, or demoted?
When MWMS can answer these questions consistently, the ecosystem can grow without polluting its own source-of-truth layer.
Change Log
v1.0 — Initial Draft
Created the MWMS Context File Promotion And Approval Protocol as the protocol for moving raw material, extracted insights, draft context, AI outputs, course findings, client material, proof items, voice rules, skill records, and MCR page drafts into approved context or active source truth.
This protocol defines context authority levels, promotion path, decision questions, promotion outcomes, criteria, blockers, approval rules, MCR page promotion rules, client context rules, proof rules, voice rules, objection rules, retired language rules, demotion rules, promotion templates, review roles, failure modes, governance role, drift protection, and architectural intent.
Change Impact Declaration
Pages Created:
MWMS Context File Promotion And Approval Protocol
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
Research Brain Page Registry
Compliance Brain Page Registry
Course Absorption 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
Skill Auditor
Offer Strategist Employee
Content Planner Employee
Creative Strategist Employee
Sales Strategist Employee
Research Analyst Employee
Compliance Reviewer Employee
AI Business Systems Architect Employee
Required behaviour updates:
AI Employees must not treat raw material, extracted insights, AI drafts, course notes, client material, or output assets as active context without promotion review.
AI Employees must identify current authority level, proposed authority level, owning Brain, destination, evidence strength, duplicate risk, review requirement, and registry impact before promoting material.
AI Employees must route client material, proof, compliance-sensitive claims, MCR pages, and cross-Brain context through the correct approval path.
AI Employees must demote, restrict, archive, retire, or reject context when it becomes stale, duplicated, risky, unsupported, or replaced.
END MWMS CONTEXT FILE PROMOTION AND APPROVAL PROTOCOL v1.0