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, Content Brain, Offer Brain, Sales Brain, Creative Brain, Conversion Brain, Customer Brain, Compliance Brain, AI Manager, AI Employee Router, 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 Library Hygiene And Retired Language Rule.
This rule establishes how MWMS keeps context libraries clean, current, usable, and safe by managing old files, stale language, retired positioning, outdated claims, duplicate context, draft material, archived material, and language that must no longer be used.
MWMS must not allow context libraries to become dumping grounds.
A context library is only useful if AI Employees can trust what is inside it.
If old context, retired language, draft notes, obsolete claims, and duplicate files remain active, AI Employees may produce outputs that are:
outdated
off-brand
legally risky
strategically wrong
inconsistent
overloaded with old positioning
based on stale offer information
mixed with draft material
using claims that should no longer appear
This rule exists to protect MWMS from context decay.
Context hygiene is not a cosmetic cleanup task.
It is a governance requirement.
Scope
This rule applies to all MWMS context libraries, offer libraries, client libraries, Brain libraries, AI Employee context packs, source files, working folders, skill folders, output folders, and future AIBS client context systems.
This includes:
HeadOffice Brain
AI Business Systems Brain
Offer Brain
Content Brain
Creative Brain
Sales Brain
Conversion Brain
Customer Brain
Research Brain
Affiliate Brain
Ads Brain
Compliance Brain
AI Manager
AI Employee Router
Brain Room
Course Absorption System
future AIBS client systems
This rule applies to:
Retired Language files
Voice Architecture files
Offer Profile files
Proof Libraries
Objection Libraries
Customer Language Banks
Differentiation Profiles
Compliance Notes
project folders
draft folders
archive folders
client folders
output folders
skill files
This rule 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 Library Hygiene is the process of keeping reusable AI context clean, current, structured, reviewed, and safe to use.
Retired Language is language that was once used or considered but should no longer appear in active outputs.
Retired language may include:
old slogans
old campaign angles
old offer descriptions
old pricing references
old CTA wording
old taglines
banned phrases
outdated claims
compliance-sensitive wording
words that caused ad disapproval
language the founder dislikes
language that no longer matches strategy
old positioning
old product descriptions
old affiliate claims
Core Principle
The core principle of this rule is:
AI can only follow the current strategy if old strategy is clearly removed, retired, archived, or marked inactive.
MWMS must make it easy for AI Employees to know:
what is active
what is draft
what is archived
what is retired
what is banned
what is uncertain
what requires review
what should never be used
If AI Employees cannot tell the difference, context drift will occur.
Hygiene Rule
Every active context library must separate:
active context
draft context
archived context
retired language
raw material
output assets
working files
review notes
client-specific material
Do not allow all files to live together without status.
A folder full of mixed documents is not a governed context library.
Retired Language Rule
Every active offer, brand, client, or campaign library should maintain a Retired Language file when language changes over time.
Retired Language is not an archive-only file.
It is active protection.
AI Employees must check Retired Language before creating public-facing, client-facing, content, sales, ad, affiliate, webinar, lead magnet, or landing page outputs.
Retired Language File Structure
A Retired Language file should include the following sections where relevant.
Retired Phrase
The word, phrase, tagline, claim, or framing that must no longer be used.
Previous Use
Where or how it was previously used.
Reason Retired
Why it must no longer be used.
Possible reasons:
outdated
off-brand
too generic
compliance risk
caused ad issue
old positioning
wrong offer promise
vendor claim risk
too hype-heavy
no proof
founder rejected
better language replaced it
Replacement Language
Preferred alternative wording where available.
Risk Level
Low, medium, high, compliance-sensitive, paid traffic sensitive, client-sensitive, or affiliate-sensitive.
Applies To
Where the retired language applies.
Examples:
all outputs
ads only
sales pages
emails
client reports
affiliate content
VEO3 scripts
landing pages
Notes
Any context required.
Retired Language Example
Retired Phrase:
revolutionary AI system
Reason Retired:
Too generic, hype-heavy, and not specific to MWMS.
Replacement Language:
governed AI business system
Applies To:
MCR pages, client-facing AIBS descriptions, content, sales material
Risk Level:
Medium
Active Context Rules
Active context must be:
current
approved
clearly named
source-truth aligned
usable by AI Employees
located in the approved folder
not duplicated across folders
reviewed where required
Active context may include:
Offer Profile
Right-Fit Client Profile
Voice Architecture
Differentiation Profile
Objection Library
Proof Library
Customer Language Bank
Methodology Map
Expert Thinking Rules
Compliance Notes
Retired Language
Draft Context Rules
Draft context must be clearly marked.
Draft files may be used for exploration, but they must not be treated as approved source truth.
Draft files should include labels such as:
Draft
Under Review
Needs Review
Needs Source
Needs Human Confirmation
Draft context requires human review before operational use.
AI Employees must state when output is based on draft context.
Archived Context Rules
Archived context is preserved for history, reference, or comparison.
Archived context should not be used for active output creation unless the task specifically requires historical review.
Archive folders may include:
old offer versions
old campaign files
old drafts
retired project files
completed client sprints
outdated context files
previous voice versions
old proof
old sales pages
AI Employees must not treat archive files as active context.
Raw Material Rules
Raw material is source evidence.
It is not automatically active context.
Raw material may include:
emails
sales pages
screenshots
client notes
voice memos
course transcripts
survey data
call notes
support replies
testimonials
Raw material must be extracted, structured, reviewed, and promoted before becoming active context.
Output Asset Rules
Output assets are created deliverables.
They may include:
emails
landing pages
lead magnets
webinar outlines
ad scripts
VEO3 scripts
sales pages
client reports
Output assets are not automatically source truth.
If an output contains reusable insight, extract that insight into the context library after review.
Do not treat every good output as a new context file.
Duplicate Context Rules
MWMS must avoid duplicate active context files.
Duplicate active files create conflict.
Before creating a new context file, check whether one already exists.
Possible duplicate outcomes:
update existing file
merge files
archive old file
retire outdated file
create new file only if scope is genuinely different
mark one file as source truth
AI Employees must not use multiple conflicting context files without review.
Context File Status Labels
MWMS should use clear status labels.
Approved
Active source truth.
Draft
Working version, not approved.
Under Review
Being checked.
Needs Source
Missing supporting evidence.
Needs Human Confirmation
Requires Martyn, founder, or client review.
Retired
No longer used.
Archived
Preserved but inactive.
Rejected
Should not be used.
Stale
Potentially outdated and requires review.
Restricted
Can be used only under specific conditions.
Context Library Hygiene Checks
MWMS should run hygiene checks regularly.
Monthly Light Hygiene Check
Checks:
Are files in correct folders?
Are draft files clearly marked?
Are old files archived?
Are duplicate files present?
Is Retired Language visible?
Are stale files marked?
Are client files isolated?
Are outputs separated from context?
Quarterly Deep Hygiene Check
Checks:
Is the active context still true?
Are retired phrases still being avoided?
Are proof items still approved?
Are offer details current?
Is voice still current?
Are objections still current?
Is buyer language still current?
Are archives clean?
Are duplicates removed?
Are AI Employees using the right files?
Event-Based Hygiene Check
Triggered when:
offer changes
voice changes
campaign changes
proof changes
pricing changes
compliance changes
client changes direction
ad disapproval occurs
affiliate vendor updates claims
AI output uses old language
human reviewer keeps correcting the same phrase
Retired Language Triggers
Add language to Retired Language when:
a phrase becomes outdated
a claim is no longer supported
a campaign angle is no longer active
a tagline changes
a product description changes
a compliance concern appears
Google Ads or another platform flags wording
a founder rejects wording
a client rejects wording
a phrase sounds too generic
a phrase creates wrong expectations
a better replacement is approved
AI keeps reusing unwanted language
Context Promotion Rules
A file or insight may be promoted into active context only when:
source is known
purpose is clear
status is assigned
duplicate risk checked
human review complete where needed
folder destination clear
related files updated where needed
Retired Language checked where relevant
proof status checked where relevant
Do not promote messy notes directly into active context.
Context Demotion Rules
A file or phrase should be demoted when:
it is outdated
it is duplicated
it conflicts with current strategy
it lacks source support
it creates compliance risk
it belongs to old positioning
it belongs in archive
it belongs in Retired Language
it is no longer useful
Demotion outcomes:
move to Archive
move to Retired Language
mark Stale
mark Restricted
merge into active file
delete only if safe and approved
Client Context Hygiene Rules
Future AIBS client libraries require strict hygiene.
Client context must:
stay isolated
have clear status labels
separate raw material from active context
separate output assets from context
maintain Retired Language where relevant
separate approved proof from unapproved proof
be reviewed before use in client-facing output
not mix with MWMS internal context
Client-specific retired language must not become general MWMS retired language unless deliberately generalized and approved.
Affiliate Context Hygiene Rules
Affiliate campaigns require careful hygiene because vendor claims, compliance rules, and platform policies can change.
Affiliate context libraries should track:
active vendor claims
restricted vendor claims
retired claims
risky words
ad disapproval language
allowed CTAs
prohibited angles
current landing page rules
vendor page changes
Affiliate Brain and Compliance Brain should review retired language for affiliate offers.
Paid Traffic Hygiene Rules
Paid traffic assets require stronger retired language control.
If wording causes platform issues, it should be added to Retired Language or Restricted Language.
Paid traffic hygiene must track:
disapproved phrases
restricted claims
unsafe urgency
misleading implications
unsupported proof
clickbait framing
policy-sensitive wording
landing-page mismatch
Ads Brain and Compliance Brain should review paid traffic retired language.
AI Employee Usage Rules
AI Employees must:
check active context before output
check Retired Language for messaging tasks
avoid archived context unless requested
avoid draft context unless marked
avoid duplicate context conflicts
flag stale context
flag missing context
avoid unapproved proof
preserve client isolation
route hygiene issues to review
AI Employees must not:
use retired phrases
treat raw material as approved context
treat output assets as source truth
use archived files as active context
ignore status labels
merge client context
invent replacement language for risky claims without review
Common Failure Modes
MWMS must prevent:
old language returning
stale offer details remaining active
draft files used as approved context
archive files used as current truth
raw files treated as context
output assets treated as source truth
duplicate active files
client context mixed with MWMS context
affiliate claims reused after vendor changes
ad-disapproved language appearing again
AI Employees ignoring Retired Language
context libraries becoming bloated
context libraries becoming unclear
Hygiene Decision Template
Use this template when reviewing a context item.
Item Name:
Item Type:
Current Location:
Current Status:
Owning Brain:
Active Use:
Issue Found:
Duplicate Risk:
Retired Language Risk:
Proof Risk:
Client Risk:
Compliance Risk:
Recommended Action:
Reason:
Human Review Required:
Next Step:
Minimum Hygiene Decision
For quick review, use:
Item:
Status:
Issue:
Action:
Review Required:
Governance Role
HeadOffice owns the MWMS Context Library Hygiene And Retired Language Rule.
HeadOffice is responsible for:
ensuring active context remains clean
preventing duplicate context
ensuring Retired Language is maintained
ensuring archive and draft material are separated
ensuring client context remains isolated
ensuring stale context is flagged
ensuring AI Employees do not use retired or restricted language
ensuring hygiene checks occur
Individual Brains are responsible for maintaining hygiene inside their own context areas.
Offer Brain governs offer context hygiene.
Content Brain governs voice and content language hygiene.
Sales Brain governs sales language hygiene.
Creative Brain governs creative language hygiene.
Affiliate Brain governs affiliate claim hygiene.
Ads Brain governs paid traffic wording hygiene.
Compliance Brain governs claim-sensitive language hygiene.
AI Business Systems Brain governs future client library hygiene.
Relationship To Other MWMS Standards
This rule supports and must align with:
MWMS Document Structure Standard
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 AI Brain Audit And Decay Prevention Framework
MWMS AI Brain Readiness Review Checklist
MWMS Context-Driven Asset Builder Framework
MWMS Tool-Agnostic Context Portability Protocol
MWMS AI Output Validation Standard
MWMS Brain Routing Rule
MWMS MCR Promotion To Brain Protocol
MWMS Architecture Registry
AI Business Systems Brain Canon
This rule provides the hygiene and retired-language protection layer for context libraries and AI output.
Drift Protection
This rule protects MWMS from:
context bloat
stale language
old claims returning
outdated offer details
duplicate source truth
draft files becoming active
archive files becoming active
client context leakage
affiliate claim drift
paid traffic wording risk
AI Employees using retired language
AI outputs based on stale context
Any context library without active, draft, archive, and retired-language separation should be treated as a hygiene drift risk.
Architectural Intent
The architectural intent of the MWMS Context Library Hygiene And Retired Language Rule is to keep MWMS context clean enough for AI Employees to trust.
MWMS will continue creating more Brains, offers, clients, skills, files, assets, and context libraries.
Without hygiene rules, the system will become noisy.
The long-term goal is that every active context library can answer:
What is active?
What is draft?
What is archived?
What is retired?
What is restricted?
What must not be used?
What is stale?
What has been replaced?
What belongs to a client?
What belongs to MWMS?
What should AI read?
What should AI ignore?
When MWMS can answer these questions consistently, AI Employees can create cleaner, safer, more current, and more strategically aligned outputs.
Change Log
v1.0 — Initial Draft
Created the MWMS Context Library Hygiene And Retired Language Rule as the rule for maintaining clean context libraries, managing retired language, separating active, draft, archived, raw, and output files, preventing duplicate context, and protecting AI Employees from using stale, unsafe, or outdated language.
This rule defines hygiene rules, retired language file structure, active context rules, draft rules, archive rules, raw material rules, output asset rules, duplicate rules, status labels, hygiene checks, triggers, promotion and demotion rules, client hygiene, affiliate hygiene, paid traffic hygiene, AI Employee usage rules, failure modes, governance role, drift protection, and architectural intent.
Change Impact Declaration
Pages Created:
MWMS Context Library Hygiene And Retired Language 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
Creative Brain Page Registry
Sales Brain Page Registry
Affiliate Brain Page Registry
Ads 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
Context Library Builder
Client IP Excavator
Offer Strategist Employee
Content Planner Employee
Creative Strategist Employee
Sales Strategist Employee
Affiliate Offer Evaluator Employee
Ads Strategist Employee
Compliance Reviewer Employee
AI Business Systems Architect Employee
Required behaviour updates:
AI Employees must check Retired Language before creating public-facing, client-facing, content, sales, ad, affiliate, webinar, lead magnet, or landing page outputs.
AI Employees must not treat draft, archived, raw, stale, restricted, or output files as approved active context.
AI Employees must flag duplicate context, stale language, retired phrases, unsupported claims, client context leakage, and hygiene drift before producing high-value outputs.
AI Employees must route context hygiene issues to the appropriate Brain or HeadOffice review path.
END MWMS CONTEXT LIBRARY HYGIENE AND RETIRED LANGUAGE RULE v1.0