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, Offer Brain, Content Brain, Sales Brain, Creative 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 AI Brain Readiness Review Checklist.
This checklist establishes the review gate MWMS uses before an AI Brain, client Brain, offer context library, skill library, AI Employee context base, or future AIBS client system is considered ready for use.
MWMS must not treat a Brain as ready just because files have been created.
A Brain is ready only when the required source material, context files, skills, boundaries, validation rules, and review pathways are clear enough for AI Employees to use safely.
This checklist exists to prevent MWMS from moving too early from draft context into operational use.
Without a readiness review, MWMS risks:
using incomplete context
building from draft files
allowing AI Employees to act on assumptions
creating inconsistent output
mixing client context
missing proof boundaries
using stale buyer language
using wrong offer details
activating skills before procedures are tested
deploying future AIBS client systems before they are safe
The AI Brain Readiness Review Checklist creates a clear gate between draft intelligence and usable operating context.
Scope
This checklist applies to all MWMS Brain, offer, client, skill, and context readiness decisions.
This includes:
HeadOffice Brain
AI Business Systems Brain
AI Manager
AI Employee Router
Brain Room
Offer Brain
Content Brain
Creative Brain
Sales Brain
Conversion Brain
Customer Brain
Research Brain
Affiliate Brain
Ads Brain
Product Brain
Strategy Brain
Course Absorption System
Newsletter Intelligence
Opportunity System
future AIBS client systems
This checklist applies before:
context library activation
AI Employee usage
skill usage
asset building
lead magnet creation
webinar creation
sales asset creation
content generation
client report generation
automation consideration
client-facing deployment
This checklist does not authorize development work, plugin changes, Supabase changes, WordPress changes, automation wiring, client access setup, or M developer action.
Core Definition
AI Brain Readiness refers to the state where an AI Brain or context system has enough approved, structured, current, and governed context to support useful AI work.
Readiness does not mean the system is perfect.
Readiness means the system is safe and clear enough for the next level of use.
Possible readiness levels include:
Not Ready
Draft Use Only
Manual Use Ready
Assisted Use Ready
Client Review Ready
Operational Use Ready
Audit Required Before Use
Core Principle
The core principle of this checklist is:
A Brain must pass readiness review before it becomes active working context.
Draft context may be useful.
But draft context is not operational truth.
A readiness gate protects MWMS from scaling weak, incomplete, or unreviewed context into business outputs.
Readiness Review Stages
The MWMS AI Brain Readiness Review uses nine review stages.
Stage 1: Source Material Readiness
Stage 2: IP Excavation Readiness
Stage 3: Context Library Readiness
Stage 4: Voice And Language Readiness
Stage 5: Offer And Buyer Readiness
Stage 6: Skill And Workflow Readiness
Stage 7: Risk And Permission Readiness
Stage 8: Output And Handoff Readiness
Stage 9: Audit And Maintenance Readiness
Each stage should be checked before activation.
Stage 1: Source Material Readiness
Purpose
This stage confirms that the Brain has enough source material to support reliable context.
Checklist
Has the relevant source material been collected?
Is the source material stored in the correct folder?
Is the source material tied to one offer, client, Brain, or system?
Are raw files separated from processed context files?
Are source files clearly named?
Are old or irrelevant files separated?
Is missing source material listed?
Is the source material current enough for the task?
Is sensitive or client-specific material isolated?
Is the source material sufficient for the next stage?
Possible Outcomes
Ready
Needs More Source Material
Source Too Messy
Source Too Thin
Client Review Required
Park For Later
Stage 2: IP Excavation Readiness
Purpose
This stage confirms that the core intelligence has been extracted from the source material.
Checklist
Have Contrarian Stances been extracted?
Has Methodology And Process been extracted?
Has Expert Thinking been extracted?
Are customer language signals captured where available?
Are objections captured where available?
Are proof signals captured where available?
Are voice examples captured where available?
Are missing evidence gaps marked?
Has invented material been removed?
Has the human operator reviewed the extraction?
Possible Outcomes
Ready
Needs Sharpening
Needs Human Review
Needs More Source
Insufficient IP
Park For Later
Stage 3: Context Library Readiness
Purpose
This stage confirms that the extracted intelligence has been converted into usable context files.
Checklist
Does the context library have a clear source-of-truth location?
Are files clearly named?
Are active, draft, archived, and retired files clearly separated?
Are duplicate context files removed or marked?
Does the library contain a Right-Fit Client Profile where needed?
Does the library contain an Offer Profile where needed?
Does the library contain a Voice Architecture where needed?
Does the library contain a Differentiation Profile where needed?
Does the library contain an Objection Library where needed?
Does the library contain a Methodology Map where needed?
Does the library contain Expert Thinking Rules where needed?
Does the library contain a Customer Language Bank where needed?
Does the library contain a Proof Library where needed?
Does the library contain Retired Language where needed?
Does the library contain Compliance Notes where needed?
Has the library been reviewed for bloat?
Possible Outcomes
Ready
Draft Only
Needs Missing Files
Needs Cleanup
Needs Deduplication
Needs Human Review
Stage 4: Voice And Language Readiness
Purpose
This stage confirms that AI Employees know how the business, offer, founder, or client should sound.
Checklist
Is the Voice Architecture clear?
Are preferred phrases captured?
Are banned phrases captured?
Are examples of good voice included?
Are examples of weak or wrong voice included where useful?
Is Retired Language available where relevant?
Is customer language separated from founder voice?
Is client voice isolated from MWMS internal voice?
Is the voice current?
Is the voice specific enough to guide AI output?
Possible Outcomes
Ready
Needs Voice Examples
Needs Retired Language
Needs Founder Review
Needs Client Review
Not Ready
Stage 5: Offer And Buyer Readiness
Purpose
This stage confirms that the offer and buyer are clear enough for AI Employees to create useful outputs.
Checklist
Is the primary offer clear?
Is the offer promise clear?
Is the offer delivery model clear?
Are inclusions and exclusions clear?
Is the buyer profile clear?
Is the buyer’s current state clear?
Is the buyer’s desired outcome clear?
Are objections clear?
Are false beliefs clear?
Are trust barriers clear?
Is approved proof available?
Are unsupported claims removed?
Is the next-step logic clear?
Is the offer suitable for the intended workflow?
Possible Outcomes
Ready
Needs Offer Clarification
Needs Buyer Clarification
Needs Proof
Needs Compliance Review
Not Ready
Stage 6: Skill And Workflow Readiness
Purpose
This stage confirms whether the Brain has the right skills or workflow rules for use.
Checklist
Are repeatable workflows identified?
Are skill candidates listed?
Are active skills clearly named?
Does each skill have an owning Brain?
Does each skill have an assigned AI Employee where relevant?
Does each skill define required input?
Does each skill define required context?
Does each skill define procedure?
Does each skill define forbidden actions?
Does each skill define required output?
Does each skill define validation?
Does each skill define handoff destination?
Are draft skills separated from active skills?
Have skills been tested manually before assisted use?
Possible Outcomes
Ready For Manual Use
Ready For Assisted Use
Needs Skill Definition
Needs Skill Testing
Needs Workflow Mapping
Not Ready
Stage 7: Risk And Permission Readiness
Purpose
This stage confirms that the Brain or system has clear safety, review, and permission boundaries.
Checklist
Are sensitive areas identified?
Are compliance risks identified?
Are financial risks identified?
Are paid traffic risks identified?
Are client privacy risks identified?
Are tool permissions defined where relevant?
Are forbidden actions defined?
Are human review requirements clear?
Are public-facing output rules clear?
Are client-facing output rules clear?
Are developer boundaries clear?
Is M’s active build boundary protected?
Are assumptions marked?
Possible Outcomes
Ready
Needs Risk Review
Needs Compliance Review
Needs Tool Permission Review
Needs Human Review Rules
Not Ready
Stage 8: Output And Handoff Readiness
Purpose
This stage confirms that the Brain or skill knows what output to create and where it goes next.
Checklist
Are expected outputs defined?
Is the output format clear?
Is the owning Brain clear?
Are supporting Brains clear?
Is the destination clear?
Is human review required before use?
Is the handoff destination defined?
Is the parking path defined?
Is the rejection path defined?
Is the archive path defined?
Is the approval path defined?
Are change impact requirements clear?
Possible Outcomes
Ready
Needs Output Format
Needs Handoff Destination
Needs Review Path
Needs Parking Path
Not Ready
Stage 9: Audit And Maintenance Readiness
Purpose
This stage confirms that the Brain or context system has a maintenance path after activation.
Checklist
Is there an audit cadence?
Is there a next review date?
Are update triggers defined?
Are drift signals defined?
Is Retired Language maintained?
Are skill audits planned?
Are context library audits planned?
Are client audits planned where relevant?
Is there a Kaizen learning path?
Is there a way to update stale context?
Is there a way to retire or archive outdated files?
Possible Outcomes
Ready
Needs Audit Cadence
Needs Drift Signals
Needs Maintenance Owner
Needs Review Date
Not Ready
Readiness Levels
MWMS uses the following readiness levels.
Not Ready
The Brain or system lacks required source material, context, clarity, or review.
Allowed use:
none or discovery only.
Draft Use Only
The Brain or system may be used for exploration, but not operational output.
Allowed use:
internal brainstorming
drafting
gap finding
review preparation
Manual Use Ready
The Brain or system may be used manually with close human review.
Allowed use:
internal drafts
manual asset creation
manual reports
manual context building
Assisted Use Ready
The Brain or system may support AI-assisted workflows with validation.
Allowed use:
repeatable assisted tasks
reviewed outputs
skill-supported drafts
Client Review Ready
The Brain or system is ready to show to a client for review, but not yet final.
Allowed use:
client validation
client feedback
context correction
Operational Use Ready
The Brain or system is ready for approved internal or client workflow use with defined review rules.
Allowed use:
approved outputs
active skill use
context-driven asset creation
client system support
Audit Required Before Use
The Brain or system was once active but may now be stale.
Allowed use:
audit only until reviewed.
Readiness Decision Template
Use the following template.
Brain Or System Name:
Review Date:
Reviewer:
Owning Brain:
Supporting Brains:
Current Status:
Source Material Readiness:
IP Excavation Readiness:
Context Library Readiness:
Voice And Language Readiness:
Offer And Buyer Readiness:
Skill And Workflow Readiness:
Risk And Permission Readiness:
Output And Handoff Readiness:
Audit And Maintenance Readiness:
Main Gaps:
Risk Notes:
Required Corrections:
Readiness Decision:
Next Review Date:
Human Approval Required:
Notes:
Minimum Readiness Decision
For quick review, use:
Name:
Status:
Main Gaps:
Risk:
Decision:
Next Action:
Readiness Decision Rules
Rule 1: No Active Use Without Approved Context
If the context library is draft or incomplete, the system cannot be Operational Use Ready.
Rule 2: No Client Use Without Client Review
Client-facing systems require client review before activation.
Rule 3: No Automation Without Proven Manual Use
A workflow should not move toward automation until it works manually.
Rule 4: No Public Output Without Risk Review
Public-facing assets require proof, voice, compliance, and offer checks.
Rule 5: No Paid Traffic Use Without Strong Context
Paid traffic assets require strong offer, buyer, proof, claim, and compliance readiness.
Rule 6: No Developer Action From Readiness Alone
This checklist can identify readiness but does not authorize development work.
Rule 7: No Guessing Missing Readiness
If a section is unknown, mark it as missing.
Do not assume readiness.
Common Failure Modes
MWMS must prevent:
treating created files as approved files
activating draft context too early
building assets before buyer is clear
using skills before procedures are defined
skipping proof review
skipping Retired Language
forgetting audit cadence
using client context without client review
moving to automation before manual proof
creating public-facing outputs from incomplete libraries
treating tool access as system readiness
assuming readiness from memory
Governance Role
HeadOffice owns the MWMS AI Brain Readiness Review Checklist.
HeadOffice is responsible for:
defining readiness gates
approving readiness levels
preventing premature activation
ensuring context libraries are reviewed
ensuring skills are tested before assisted use
ensuring high-risk systems require human review
ensuring client systems remain isolated
ensuring audit and maintenance paths are defined
AI Business Systems Brain governs future client-system readiness.
Offer Brain governs offer readiness.
Content Brain governs content readiness.
Sales Brain governs sales asset readiness.
Creative Brain governs creative readiness.
Compliance Brain governs claims and public-risk readiness.
Relationship To Other MWMS Standards
This checklist supports and must align with:
MWMS Document Structure Standard
MWMS AI Brain Build Sequence Framework
MWMS Client Brain Intake And Onboarding Protocol
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 Context-Driven Asset Builder Framework
MWMS Tool-Agnostic Context Portability Protocol
MWMS AI Skill Builder And Audit Protocol
MWMS AI Brain Audit And Decay Prevention Framework
MWMS AI Agent Memory And Context Framework
MWMS AI Agent Skill Library Framework
MWMS AI Output Validation Standard
MWMS Brain Routing Rule
MWMS MCR Promotion To Brain Protocol
MWMS Page Naming Standard
MWMS Architecture Registry
AI Business Systems Brain Canon
This checklist provides the readiness gate for the related context, skill, asset, and client Brain standards.
Drift Protection
This checklist protects MWMS from:
premature activation
draft files becoming active source truth
AI Employees acting on incomplete context
client systems launched before review
skills used before tested
context libraries used without proof boundaries
public assets created from weak source
automation before manual clarity
audit paths being forgotten
tool access being mistaken for readiness
Any Brain, skill, context library, or client system that has not passed readiness review should be treated as draft or review-only.
Architectural Intent
The architectural intent of the MWMS AI Brain Readiness Review Checklist is to create a practical activation gate for MWMS AI systems.
MWMS will create many Brains, libraries, skills, and future client systems.
The system needs a clear way to decide when something is ready for use.
The long-term goal is that every Brain or context system can answer:
Do we have enough source material?
Has the intelligence been excavated?
Is the context library structured?
Is the voice clear?
Is the offer clear?
Is the buyer clear?
Are skills defined?
Are risks known?
Are outputs defined?
Are handoffs clear?
Is audit scheduled?
What readiness level applies?
When MWMS can answer these questions consistently, AI systems can move from draft to use without losing governance, quality, or safety.
Change Log
v1.0 — Initial Draft
Created the MWMS AI Brain Readiness Review Checklist as the readiness gate for AI Brains, client Brains, offer context libraries, skill libraries, AI Employee context bases, and future AIBS client systems.
This checklist defines readiness stages, readiness levels, review templates, decision rules, failure modes, governance role, drift protection, and architectural intent.
Change Impact Declaration
Pages Created:
MWMS AI Brain Readiness Review Checklist
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
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
Skill Auditor
Offer Strategist Employee
Content Planner Employee
Creative Strategist Employee
Sales Strategist Employee
AI Business Systems Architect Employee
Required behaviour updates:
AI Employees must not treat created files as active context until readiness is reviewed.
AI Employees must classify Brains, context libraries, skill sets, and client systems into readiness levels before use.
AI Employees must flag missing source material, missing context files, unclear offer, unclear buyer, undefined skills, risk gaps, missing handoff paths, and missing audit cadence.
AI Employees must not recommend automation, public-facing use, paid traffic use, or client deployment before readiness conditions are met.
END MWMS AI BRAIN READINESS REVIEW CHECKLIST v1.0