System: MWMS
Document Type: Protocol
Authority Level: MCR Source Of Truth
Status: Draft For MCR
Primary Location: MCR
Future Operational Destination: AI Business Systems Brain, HeadOffice Brain, AI Manager, AI Employee Router, Brain Room, Client Brain Systems, Offer Brain, Content Brain, Sales Brain, Creative Brain, Research Brain, Compliance Brain, Future AIBS Client Systems
Parent Page: AI Business Systems Brain
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 Client Approval And Review Gate Protocol.
This protocol establishes how MWMS controls review, approval, rejection, revision, and release of client-facing context, client reports, client proof, client assets, client workflows, client AI skills, and future AIBS deliverables.
MWMS must not treat client-facing AI output as approved just because it is well-written.
AI can draft, structure, summarize, and prepare.
But client-facing material must pass review before it is treated as approved.
This protocol exists to protect future AIBS delivery from:
wrong client context
unapproved proof
off-brand voice
incorrect offer details
misleading claims
private data exposure
wrong workflow assumptions
unapproved client reports
premature asset use
AI-generated outputs being mistaken for final deliverables
client dissatisfaction caused by skipped review
Client approval is not a bottleneck.
It is a trust layer.
Scope
This protocol applies to all future MWMS client-facing and client-owned work inside AI Business Systems and client Brain systems.
This includes:
client context libraries
client business snapshots
client offer profiles
client buyer profiles
client voice architecture
client differentiation profiles
client objection libraries
client proof libraries
client methodology maps
client expert thinking rules
client customer language banks
client compliance notes
client approval rules
client reports
client dashboards
client content drafts
client sales assets
client lead magnets
client webinars
client ad assets
client workflows
client skills
client AI Employee instructions
client audit records
future AIBS deliverables
This protocol supports:
AI Business Systems Brain
HeadOffice Brain
AI Manager
AI Employee Router
Brain Room
Client Brain Systems
Offer Brain
Content Brain
Sales Brain
Creative Brain
Conversion Brain
Research Brain
Compliance Brain
future AIBS client systems
This protocol does not authorize development work, plugin changes, Supabase changes, WordPress changes, automation wiring, publishing, client implementation, credential handling, file deletion, or M developer action.
Core Definition
A Client Review Gate is a required decision point before client-owned or client-facing material moves from draft to approved use.
A Client Approval Record is the traceable record of what was reviewed, who approved it, what use was allowed, what restrictions apply, and when it should be reviewed again.
Client approval may apply to:
context files
proof
voice rules
claims
reports
assets
workflow rules
AI skills
public examples
case studies
client-facing recommendations
Core Principle
The core principle of this protocol is:
Client-facing output remains draft until the correct review gate is passed.
AI-generated client work must not be treated as final without review.
Review protects:
accuracy
trust
privacy
brand voice
proof integrity
client relationship
future recurring delivery
AIBS credibility
Client Review Gate Types
MWMS uses several review gate types.
Internal MWMS Review
Used before showing material to the client.
Purpose:
catch obvious errors
check structure
check missing context
check privacy issues
check proof status
check compliance risk
Client Review
Used when client confirmation is required.
Purpose:
confirm accuracy
confirm voice
confirm offer details
confirm proof permission
confirm approval boundaries
confirm business context
Compliance Review
Used when sensitive claims or regulated areas are involved.
Purpose:
check health, finance, income, privacy, testimonial, platform, affiliate, or paid traffic risk
HeadOffice Review
Used for cross-system, governance, or high-risk decisions.
Purpose:
protect MWMS source-of-truth discipline and system integrity
Brain Owner Review
Used when a specialist Brain must validate the work.
Examples:
Offer Brain reviews offer accuracy.
Content Brain reviews content and voice.
Sales Brain reviews sales assets.
Compliance Brain reviews claim risk.
AI Business Systems Brain reviews client system fit.
M Review
Used only when a future technical or implementation boundary is involved.
This protocol itself does not authorize M work.
Client Approval Required For
Client approval is required before using:
client testimonials publicly
client screenshots publicly
client performance data publicly
client case studies
client proof in marketing
client voice architecture as active final context
client offer profile as active final context
client buyer profile as active final context
client public-facing assets
client reports sent outside MWMS
client sales assets
client ad assets
client AI skill instructions used in live client workflows
client workflows represented as final
client private examples
client deliverables as MWMS portfolio material
client material generalized into AIBS templates where approval is required
Client approval may not be required for internal draft preparation, but draft status must remain clear.
Client Approval Statuses
MWMS uses the following statuses.
Draft
Created but not reviewed.
Internal Review Complete
Checked by MWMS but not client-approved.
Client Review Required
Needs client approval before use.
Client Approved
Approved for the stated use.
Client Approved With Restrictions
Approved only under specific conditions.
Revision Required
Client or reviewer requested changes.
Rejected
Should not be used.
Expired Approval
Previously approved but review date has passed or context changed.
Approval Withdrawn
Previously approved but no longer allowed.
Archive Only
Preserved but inactive.
Approval Scope
Every approval must define scope.
Approval scope may include:
internal use only
client-facing report use
public website use
case study use
ad use
sales page use
email use
social content use
portfolio use
training use
generalized template use
Approval for one use does not automatically approve all uses.
Example:
A client may approve a testimonial for a private report but not public advertising.
Client Review Gate Workflow
MWMS uses the following workflow.
Step 1: Identify Material
Define what is being reviewed.
Step 2: Identify Owner
Confirm which client owns the material.
Step 3: Identify Use Case
Define where and how the material will be used.
Step 4: Identify Risk
Check privacy, proof, claims, brand, client, compliance, and public-facing risk.
Step 5: Run Internal Review
MWMS checks quality before sending to client.
Step 6: Send For Client Review Where Required
Client confirms, rejects, or requests changes.
Step 7: Record Approval Decision
Capture status, scope, restrictions, reviewer, and date.
Step 8: Update Context Or Asset Status
Move from draft to approved, restricted, revision required, rejected, or archived.
Step 9: Propagate Changes
Update dependent files, assets, skills, or reports where needed.
Step 10: Set Next Review Date
If context may change, set review timing.
Client Approval Record Template
Use the following template.
Client Name:
Material Name:
Material Type:
Source:
Proposed Use:
Review Gate Type:
Risk Level:
Privacy Level:
Reviewer:
Review Date:
Approval Status:
Approval Scope:
Restrictions:
Required Changes:
Proof Permission:
Public Use Allowed:
Ad Use Allowed:
Client-Facing Use Allowed:
Internal Use Allowed:
Can Be Generalized:
Expiration Or Review Date:
Dependent Files Or Assets:
Next Action:
Notes:
Minimum Approval Record
For quick approval tracking:
Client:
Material:
Use:
Status:
Approved By:
Restrictions:
Next Review:
Client Review Questions
When reviewing client material, ask:
Is this accurate?
Does this reflect the client’s actual offer?
Does this reflect the client’s actual buyer?
Does this sound like the client?
Is the proof approved?
Is any private data exposed?
Is this claim safe?
Is this output ready for the intended use?
Are restrictions needed?
Does anything require revision?
Can this be reused later?
Can this be generalized?
Does approval expire?
Proof Review Gate
Client proof requires a stricter gate.
Before using client proof, confirm:
source
client ownership
claim supported
claim not supported
approval status
public use permission
ad use permission
privacy sensitivity
identifying details
expiration or review date
Client proof must not be used beyond approved scope.
Voice Review Gate
Client voice requires approval before active use.
Before approving client voice, confirm:
tone is accurate
phrases are accurate
banned language is accurate
retired language is accurate
examples are acceptable
CTA style is acceptable
platform adjustments are acceptable
client has reviewed voice direction where required
Offer Review Gate
Client offer context requires approval before active use.
Before approving client offer profile, confirm:
offer name
offer type
main promise
delivery model
included components
not included
pricing if relevant
proof
limitations
risk notes
next step
Buyer Review Gate
Client buyer context requires approval before active use.
Before approving buyer profile, confirm:
buyer segment
current problem
desired outcome
objections
trust barriers
buyer language
bad-fit buyers
decision criteria
assumptions versus evidence
Report Review Gate
Client reports require review before delivery.
Before sending a client report, confirm:
data is accurate
recommendations are grounded
no private unrelated data is included
claims are supported
tone is appropriate
next actions are clear
client-sensitive information is protected
AI assumptions are labelled
Asset Review Gate
Client assets require review before use.
Client assets may include:
emails
landing pages
lead magnets
webinars
sales scripts
ads
social posts
reports
workshop decks
Before approval, confirm:
correct offer
correct buyer
correct voice
approved proof
safe claims
no retired language
clear CTA
client approval where required
Compliance Review Gate
Compliance review is required when material includes:
health claims
finance claims
income claims
testimonials
before-and-after claims
paid traffic ads
affiliate claims
privacy-sensitive data
regulated industry claims
client performance data
public proof
Compliance Brain must review or flag for expert review where needed.
Revision Rules
If a reviewer requests changes, the material status becomes Revision Required.
Revision should record:
what changed
who requested it
why
what file was updated
whether dependent assets are affected
whether approval must be repeated
Material should not be treated as approved until revision is reviewed.
Approval Expiry Rules
Some approvals may expire.
Approval should be reviewed when:
offer changes
buyer changes
proof changes
client positioning changes
client voice changes
compliance rules change
campaign changes
public use expands
review date passes
client withdraws approval
Expired approval must not be used until renewed.
Approval Withdrawal Rule
If client approval is withdrawn:
mark material Approval Withdrawn
stop active use
update dependent assets
remove from public-facing use where required
archive or restrict material
record withdrawal date and reason
notify relevant Brain or human owner
Generalization Approval Rule
Client material may be generalized into MWMS or AIBS templates only after review.
Before generalizing, confirm:
client identifiers removed
private details removed
proof not reused without permission
strategy abstracted
client approval if required
HeadOffice review complete
AI Business Systems Brain review complete
Generalized material must become MWMS-owned only after proper review.
Client Review Gate Failure Modes
MWMS must prevent:
client-facing output sent without review
client proof used without approval
public use beyond approved scope
client voice activated without review
client reports using wrong context
client assets treated as final too early
approval scope not recorded
approval expiry ignored
client rejection not propagated
client material generalized without approval
AI-generated client content treated as client-approved
Governance Role
AI Business Systems Brain owns the MWMS Client Approval And Review Gate Protocol.
HeadOffice governs cross-system risk, source-of-truth discipline, and escalation.
Compliance Brain governs sensitive claims, privacy, platform, and regulated-risk review.
AI Business Systems Brain is responsible for:
client approval workflows
client approval records
client context approval status
client report review gates
client asset review gates
client skill review gates
client generalization approval
future AIBS delivery trust
HeadOffice is responsible for:
ensuring client approval gates are respected
ensuring client-specific context remains isolated
ensuring approval status is not overstated
ensuring high-risk material is escalated
Relationship To Other MWMS Standards
This protocol supports and must align with:
MWMS Document Structure Standard
MWMS Client Context Isolation And Privacy Boundary Standard
MWMS Client Brain Intake And Onboarding Protocol
MWMS Client IP Excavation Framework
MWMS Source Material Intake And Evidence Inventory Checklist
MWMS Context File Promotion And Approval Protocol
MWMS Context Change Propagation And Dependency Map Protocol
MWMS Proof Library And Claims Control Standard
MWMS Voice Architecture And Brand Language Standard
MWMS Right-Fit Client And Offer Profile Standard
MWMS Differentiation And Objection Library Standard
MWMS Context Library Hygiene And Retired Language Rule
MWMS Missing Context And Evidence Gap Handling Rule
MWMS Minimum Viable Context Library Rule
MWMS AI Brain Readiness Review Checklist
MWMS AI Brain Audit And Decay Prevention Framework
MWMS AI Context Pack Template Standard
AI Business Systems Brain Canon
This protocol provides the approval gate required before client-specific material becomes active, public, generalized, or client-facing.
Drift Protection
This protocol protects MWMS from:
unapproved client output
client proof misuse
client privacy leakage
wrong approval scope
client voice drift
client offer inaccuracy
client report errors
client assets released too early
client material generalized without review
approval expiry being ignored
Any client-facing material used without a clear approval status and approval scope should be treated as a client approval drift risk.
Architectural Intent
The architectural intent of the MWMS Client Approval And Review Gate Protocol is to make future AIBS client delivery safe, trusted, and professionally governed.
MWMS will eventually produce client-facing AI outputs at scale.
That cannot happen safely unless review gates are clear.
The long-term goal is that every client-facing item can answer:
Has this been reviewed?
Who reviewed it?
What was approved?
What use is allowed?
What use is restricted?
Does approval expire?
Is public use allowed?
Is ad use allowed?
Can this be generalized?
What dependent assets must update if approval changes?
When MWMS can answer these questions consistently, future client delivery becomes safer, clearer, and more scalable.
Change Log
v1.0 — Initial Draft
Created the MWMS Client Approval And Review Gate Protocol as the protocol for reviewing, approving, restricting, revising, rejecting, and releasing client-facing context, proof, voice files, offer files, buyer files, reports, assets, skills, workflows, and future AIBS deliverables.
This protocol defines review gate types, approval requirements, approval statuses, approval scope, review workflow, approval records, review questions, proof gates, voice gates, offer gates, buyer gates, report gates, asset gates, compliance gates, revision rules, expiry rules, withdrawal rules, generalization rules, failure modes, governance role, drift protection, and architectural intent.
Change Impact Declaration
Pages Created:
MWMS Client Approval And Review Gate Protocol
Pages Updated:
None
Pages Deprecated:
None
Registries Requiring Update:
MWMS Architecture Registry
AI Business Systems Brain Page Registry
HeadOffice Page Registry
Compliance Brain Page Registry
Client Asset Registry
Canon Version Update Required:
No
Change Log Entry Required:
Yes
Employee Impact Check
Employees impacted:
AI Business Systems Architect Employee
HeadOffice Manager Employee
AI Manager
AI Employee Router
Client IP Excavator
Context Library Builder
Skill Auditor
Content Planner Employee
Offer Strategist Employee
Creative Strategist Employee
Sales Strategist Employee
Research Analyst Employee
Compliance Reviewer Employee
Required behaviour updates:
AI Employees must treat client-facing output as draft until the correct review gate has been passed.
AI Employees must identify client approval status, approval scope, restrictions, reviewer, review date, and next review requirement before using client material.
AI Employees must not use client proof, testimonials, screenshots, reports, voice, workflows, public examples, case studies, or client-facing assets beyond approved scope.
AI Employees must route client proof, claims, public-facing assets, ad assets, privacy-sensitive material, and regulated content through the correct review path.
AI Employees must propagate client approval changes, restrictions, expiry, or withdrawal to dependent files, assets, skills, and reports.
END MWMS CLIENT APPROVAL AND REVIEW GATE PROTOCOL v1.0