System: MWMS
Document Type: Standard
Authority Level: MCR Source Of Truth
Status: Draft For MCR
Primary Location: MCR
Future Operational Destination: HeadOffice Brain, AIBS Brain, Content Brain, Offer Brain, Creative Brain, Sales Brain, Conversion Brain, Customer Brain, AI Manager, AI Employee Router, Future AIBS Client Systems
Parent Page: Content Brain Canon
Owner: Martyn
Developer Boundary: No Development Action Authorized By This Page
Source Of Truth: MCR
Last Reviewed: 2026-06-21
Source / Origin: MWMS Voice Architecture And Brand Language Standard v1.0 + AI Automations by Jack — tone-of-voice extraction, written-versus-spoken source separation, micro-level, meso-level and macro-level style analysis block
MWMS Classification: Voice Architecture Standard / Brand Language Governance Standard / Founder Voice Extraction Framework / AI Style Validation Standard
Primary Brain: Content Brain
Supporting Brains: HeadOffice Brain, AIBS Brain, Offer Brain, Creative Brain, Sales Brain, Conversion Brain, Customer Brain, Research Brain, Affiliate Brain, Ads Brain, Compliance Brain
Purpose
The purpose of this document is to define the MWMS Voice Architecture And Brand Language Standard.
This standard establishes how MWMS captures, structures, governs, preserves, reviews, and applies founder voice, brand voice, offer language, customer language, preferred phrasing, banned wording, retired language, tone rules, and communication style across AI-generated business outputs.
MWMS must not allow AI-generated content to sound generic.
AI output should not become:
over-polished
corporate
robotic
bland
too perfect
too safe
too vague
too distant from the founder
too detached from the buyer
too similar across different clients or offers
Voice is not decoration.
Voice is part of trust.
Voice helps the buyer feel that the business is real, specific, consistent, and credible.
This standard exists because AI tools often flatten voice unless the system gives them clear structure.
The Voice Architecture And Brand Language Standard gives MWMS a way to preserve voice across:
content
emails
ads
VEO3 scripts
landing pages
webinars
lead magnets
sales scripts
client reports
AI Employee outputs
future AIBS client systems
Scope
This standard applies to all MWMS work where AI creates, reviews, rewrites, adapts, or evaluates language intended for humans.
This includes:
Content Brain
Offer Brain
Creative Brain
Sales Brain
Conversion Brain
Customer Brain
Research Brain
Affiliate Brain
Ads Brain
AIBS Brain
HeadOffice Brain
AI Manager
AI Employee Router
Course Absorption System
Client Brain systems
future AIBS client systems
This standard applies to:
emails
newsletters
landing pages
sales pages
VSL scripts
VEO3 scripts
ad scripts
social posts
lead magnets
webinars
client reports
onboarding messages
support replies
brand documents
offer pages
internal AI Employee output
client-facing AI output
This standard does not authorize development work, plugin changes, Supabase changes, WordPress changes, automation wiring, publishing, client implementation, or M developer action.
Core Definition
Voice Architecture is the structured context file that defines how a founder, business, offer, brand, Brain, or client should sound.
Brand Language is the set of words, phrases, tones, expressions, examples, exclusions, and communication habits that make that voice recognizable and consistent.
Voice Architecture may include:
tone
rhythm
sentence style
directness level
humour level
formality level
emotional register
preferred phrases
banned phrases
retired language
example openings
example CTAs
founder expressions
customer-facing phrasing
words to avoid
words to preserve
before-and-after examples
Voice Architecture is not a generic tone guide.
It is a working source file that AI Employees must read before creating or reviewing language-heavy outputs.
Voice Source Modality Separation
Written voice and spoken voice should not automatically be treated as identical.
A founder, brand, or client may have different communication patterns across:
written content
spoken content
sales conversations
educational content
support communication
formal client communication
social content
founder commentary
Possible Voice Profiles
MWMS may maintain separate approved profiles for:
Founder Written Voice
Founder Spoken Voice
Brand Written Voice
Brand Spoken Voice
Sales Voice
Educational Voice
Support Voice
Social Voice
Formal Client Voice
Rule
Train the voice profile from source material that matches the intended output modality.
Use spoken source material for spoken scripts where practical.
Use written source material for written outputs where practical.
Do not combine all communication sources into one undifferentiated profile without review.
Three-Level Voice Analysis Model
MWMS should analyse voice across three levels.
Micro-Level Analysis
Micro-level analysis covers:
vocabulary
preferred words
repeated phrases
banned words
grammar
active versus passive voice
tense patterns
contractions
punctuation
formatting quirks
sentence openings
word frequency
specialist terminology
plain-language preference
Meso-Level Analysis
Meso-level analysis covers:
sentence length
sentence variation
paragraph length
transitions
rhetorical devices
questions
examples
anecdotes
repetition
pacing
fragments
emphasis patterns
paragraph progression
Macro-Level Analysis
Macro-level analysis covers:
overall tone
mood
authority level
warmth
humour
directness
structure
coherence
worldview
recurring themes
distinctive quirks
figurative language
dialogue style
emotional register
Rule
A voice profile should explain not only which words are used, but how the communication is constructed.
Positive And Negative Example Rule
Each important voice instruction should include where practical:
what to do
a good example
what not to do
a bad example
Weak guidance such as:
sound professional and friendly
is not enough by itself.
Strong voice guidance should show the difference between acceptable and unacceptable execution.
Voice Profile Record
Each approved Voice Architecture profile should include:
Voice Profile ID:
Person Or Brand:
Purpose:
Output Modality:
Audience:
Approved Source Material:
Excluded Source Material:
Source Period:
Vocabulary Rules:
Grammar Rules:
Punctuation Rules:
Sentence Rules:
Paragraph Rules:
Tone Rules:
Humour Rules:
Authority Rules:
Story Rules:
CTA Rules:
Examples:
Forbidden Patterns:
Claims Style:
Risk Notes:
Reviewer:
Status:
Version:
Created Date:
Last Reviewed:
Rule
Voice profiles must be structured, versioned, and reviewable.
They must not exist only as loose prompts or chat history.
Voice Profile Validation
A generated voice profile should be tested against source samples not used during extraction where possible.
Validation should review:
recognisability
accuracy
exaggeration
repeated catchphrases
unnatural mimicry
factual integrity
platform fit
brand fit
readability
unwanted caricature
reviewer confidence
Rule
Voice extraction is not complete when the first profile is generated.
It requires human review, testing, correction, and version approval.
Anti-Caricature Rule
AI may overuse:
catchphrases
slang
hyperbole
punctuation quirks
dramatic metaphors
motivational language
repetition
founder mannerisms
The goal is not to create a parody.
The goal is to preserve recognisable communication patterns while maintaining clarity and restraint.
Rule
Distinctive voice markers should be represented proportionally.
They should not be amplified until the output sounds artificial.
Voice Profile Versus Task Instruction
Keep separate:
what to create
who it is for
what evidence to use
what format to follow
which approved voice profile to apply
Voice must not override:
factual accuracy
source evidence
compliance
platform requirements
business objective
output structure
claim safety
Rule
Voice is one governed context layer.
It is not the entire instruction set.
Consent And Impersonation Rule
Do not build or commercially use a detailed voice profile for a living person without appropriate authority.
Public content may support educational pattern analysis.
It must not be used to falsely represent authorship, endorsement, identity, or approval.
Do not:
impersonate
misrepresent authorship
fabricate endorsements
create deceptive messages
use private communications without permission
clone voice or likeness without authority
publish content that falsely appears to come from another person
Rule
Voice analysis does not create a right to impersonate.
Core Principle
The core principle of this standard is:
AI should preserve the real communication style of the business, not replace it with generic marketing language.
AI may improve clarity.
AI may improve structure.
AI may improve flow.
AI may improve conversion logic.
But AI must not erase the voice that makes the business specific.
Voice should be governed, not guessed.
Voice Architecture File
Each serious offer, Brain, founder, brand, or client system should have a Voice Architecture file where voice matters.
The file should define:
Voice Summary
Tone Rules
Rhythm And Sentence Style
Preferred Language
Banned Language
Retired Language
Founder Phrases
Customer Language Usage
CTA Style
Humour And Personality Rules
Emotional Register
Examples Of Strong Voice
Examples Of Weak Voice
Platform Adjustments
Compliance And Claim Language Notes
The Voice Architecture file should sit inside the approved context library.
It should not be scattered across random prompts, chat history, or project notes.
Voice Summary
Purpose
The Voice Summary gives a short overview of how the brand or founder should sound.
Examples:
direct but warm
plainspoken and practical
confident but not arrogant
expert but not academic
humorous but not silly
premium but not corporate
sharp but not aggressive
calm but not passive
The Voice Summary helps AI Employees quickly understand the overall feel.
Tone Rules
Tone Rules define what emotional and communication style should be used.
Tone may include:
friendly
direct
curious
bold
practical
reassuring
strategic
challenging
plainspoken
energetic
calm
premium
conversational
Tone Rules should also define what the voice is not.
Examples:
not hype-heavy
not robotic
not corporate
not overly academic
not fluffy
not fake urgent
not overly polished
not childish
not fearmongering
Rhythm And Sentence Style
Rhythm defines how the writing moves.
It may include:
short sentences
varied sentence length
simple structure
punchy lines
clear spacing
plain language
occasional fragments
strong transitions
low jargon
direct calls to action
AI often creates long, smooth paragraphs.
MWMS should preserve rhythm where rhythm matters.
Preferred Language
Preferred Language includes words, phrases, and expressions that should be used where appropriate.
Examples:
plain words
founder phrases
brand phrases
buyer-recognizable language
offer-specific terms
framework names
approved terminology
category language
Preferred language should be specific enough to guide AI, but not so rigid that every output sounds repeated.
Banned Language
Banned Language includes words and phrases that should not be used.
Examples:
generic hype
overused AI phrases
empty marketing language
unapproved claims
phrases the founder dislikes
language that sounds off-brand
phrases that create compliance risk
Examples of common banned AI-style phrases may include:
unlock your potential
game-changing
revolutionary
seamless solution
in today’s fast-paced world
take your business to the next level
supercharge your success
unless the specific brand truly uses that language.
Retired Language
Retired Language includes words, phrases, claims, taglines, old positioning, old campaign language, or old offer descriptions that used to be used but should no longer appear.
Retired Language is active protection.
It tells AI what not to resurrect.
Retired Language may include:
old slogans
outdated claims
old offer names
old pricing references
old campaign angles
old compliance-sensitive wording
old product descriptions
old brand positioning
phrases that caused ad disapproval
phrases that no longer match strategy
Retired Language must be checked for public-facing and customer-facing outputs.
Founder Phrases
Founder Phrases are real phrases the founder, business owner, expert, or brand naturally uses.
These may come from:
emails
voice notes
calls
training videos
course content
social posts
sales calls
interviews
Brain Room messages
old scripts
Founder Phrases help AI preserve human voice.
MWMS should preserve strong founder language where useful.
Do not over-polish founder phrases until they lose personality.
Customer Language Usage
Customer Language is different from founder voice.
Customer language reflects how buyers describe problems, desires, anxieties, objections, and outcomes.
Voice Architecture should define how customer language should be used.
Rules:
use customer language for resonance
do not pretend customer language is founder voice
do not invent customer quotes
do not exaggerate emotional language
do not distort buyer wording
preserve strong real phrases where useful
Customer Language should connect with the Content Brain VOC Grounded AI Copy Framework.
CTA Style
CTA Style defines how the brand asks people to take action.
CTA style may be:
direct
soft
curious
instructional
minimal
urgent
calm
educational
playful
premium
Examples:
Watch the video now.
See how it works.
Start with the checklist.
Book your review.
Get the guide.
Compare your options.
CTAs should match the brand voice and buyer readiness.
Do not use aggressive CTAs if the brand voice is calm and advisory.
Do not use soft CTAs if the campaign requires direct-response clarity.
Humour And Personality Rules
Some brands use humour.
Some do not.
Voice Architecture should define:
whether humour is allowed
what type of humour fits
what humour is off-limits
how playful the brand can be
whether sarcasm is allowed
whether self-deprecation is allowed
whether jokes should be avoided in serious contexts
For MWMS, humour may be useful in some ad concepts, VEO3 hooks, and content, but it must not damage trust, compliance, or offer clarity.
Emotional Register
Emotional Register defines the emotional level the voice should use.
Examples:
calm and reassuring
urgent but not fearful
bold but not aggressive
empathetic but not sentimental
serious but not cold
curious but not vague
Emotional Register helps prevent AI from either underplaying or overdramatizing the message.
For affiliate, health, finance, compliance-sensitive, or paid traffic outputs, emotional register must be checked carefully.
Examples Of Strong Voice
The Voice Architecture file should include strong examples.
Examples may include:
headline examples
email openings
CTA examples
paragraph examples
story snippets
founder phrases
ad hook examples
before-and-after rewrites
Strong examples help AI match style more accurately.
Examples Of Weak Voice
The Voice Architecture file should also include examples of what not to do.
Examples may include:
too corporate
too robotic
too hype-heavy
too academic
too vague
too polished
too salesy
too casual
too childish
too fear-based
Weak examples are useful because AI often needs contrast.
Platform Adjustments
Voice may shift slightly by platform.
Examples:
YouTube ad scripts may be punchier.
Emails may be warmer.
MCR pages must be operational and governed.
Client reports may be clearer and more formal.
Social posts may be more conversational.
Landing pages may be more direct-response focused.
Voice Architecture should define permitted platform adjustments without losing the core voice.
Compliance And Claim Language Notes
Some voice choices create risk.
Voice Architecture should include claim language notes where relevant.
Examples:
avoid guaranteed outcomes
avoid medical claims
avoid income promises
avoid exaggerated fear
avoid fake scarcity
avoid unsupported proof
avoid misleading testimonial language
avoid direct product claims not approved by vendor
Compliance Brain should review claim-sensitive voice rules where necessary.
Voice Extraction Sources
MWMS may extract voice from:
emails
newsletters
social posts
video transcripts
sales pages
podcasts
voice memos
workshop recordings
Brain Room chats
client reports
founder notes
customer replies
sales calls
course content
The best voice sources are usually real, natural, and unpolished.
Highly polished marketing pages can help, but they may not capture the founder’s real voice.
Voice Extraction Workflow
MWMS uses the following workflow.
Step 1: Gather Voice Samples
Collect representative writing and speaking samples.
Record:
source
date
modality
audience
purpose
whether the sample is approved
whether the sample is natural or heavily edited
Step 2: Separate Written Voice, Spoken Voice, Founder Voice, Brand Voice, And Customer Language
Founder voice and customer wording serve different roles.
Step 3: Analyse Micro-Level Features
Analyse vocabulary, grammar, punctuation, contractions, tense, preferred words, banned words, formatting habits, and recurring phrase structures.
Step 4: Analyse Meso-Level Features
Analyse sentence length, sentence variation, paragraph structure, pacing, transitions, questions, examples, anecdotes, repetition, fragments, and rhetorical devices.
Step 5: Analyse Macro-Level Features
Analyse tone, mood, warmth, humour, directness, authority, worldview, structure, recurring themes, quirks, figurative language, and emotional register.
Step 6: Identify Repeated Patterns
Look for repeated tone, phrasing, rhythm, transitions, CTAs, humour, and emotional style.
Step 7: Identify Strong Phrases
Capture phrases that feel specific and usable.
Step 8: Identify Weak Or Unwanted Language
Capture language that should not be repeated.
Step 9: Identify Retired Language
Mark old positioning, old phrases, and outdated claims.
Step 10: Create Voice Architecture File
Structure findings into the approved format.
Step 11: Review With Human Operator
Voice requires human review because it is subjective and brand-sensitive.
Step 12: Validate Against Unseen Samples
Test the profile against source samples not used during extraction where possible.
Review for recognisability, exaggeration, caricature, compliance, platform fit, and brand fit.
Step 13: Correct And Version
Apply human corrections.
Record the version, reviewer, approval status, source period, and last reviewed date.
Step 14: Activate For Use
Once approved, the file becomes part of the active context library.
Voice Usage Rules
Rule 1: Voice Must Be Based On Evidence
Do not invent brand voice from a few vague adjectives.
Rule 2: Voice Must Be Separated From Buyer Language
The buyer’s words are not automatically the brand’s voice.
Rule 3: Retired Language Must Be Enforced
Old language must not reappear in new outputs.
Rule 4: AI May Clarify But Must Not Flatten
AI may improve readability without making the copy generic.
Rule 5: Voice Must Serve The Asset Objective
Voice should support the purpose of the asset.
Rule 6: Compliance Overrides Voice
If brand voice creates compliance risk, compliance wins.
Rule 7: Human Review Is Required For Voice Approval
AI can draft voice rules, but human review must approve them.
Rule 8: Client Voice Must Stay Isolated
Client voice files must not influence other clients or MWMS internal voice.
Rule 9: Voice Must Match Modality
Do not use a spoken voice profile for written output without review.
Do not use a written profile for spoken scripts without adaptation.
Rule 10: Voice Must Be Proportionate
Do not overuse distinctive phrases, slang, humour, or punctuation quirks.
Rule 11: Voice Profiles Must Be Versioned
Voice changes over time.
The approved profile must identify its source period, version, reviewer, and last reviewed date.
Rule 12: Voice Examples Must Not Become Templates
Examples guide pattern recognition.
They should not be copied repeatedly into outputs.
Rule 13: Voice Analysis Must Not Authorize Impersonation
A voice profile may support approved brand production.
It must not falsely represent another person.
Voice Validation Checklist
Before approving a language-heavy output, check:
Does it sound like the approved voice?
Is it too generic?
Is it over-polished?
Is it too corporate?
Is it too casual?
Is it too hype-heavy?
Is rhythm consistent?
Are preferred phrases used where appropriate?
Are banned phrases avoided?
Is retired language avoided?
Is customer language used accurately?
Are claims safe?
Is the CTA style aligned?
Does the platform adjustment make sense?
Would the founder or client actually say this?
Was the correct written or spoken profile used?
Are distinctive phrases overused?
Does the output sound like a caricature?
Does the profile match the intended audience and platform?
Was the profile built from approved source material?
Has the profile been reviewed recently?
Does the output falsely imply authorship by another person?
If the answer is no, revise before use.
Voice Drift Signals
Voice may be drifting if:
outputs sound like generic AI
the same phrases appear repeatedly
the founder keeps rewriting tone
customer-facing copy feels off
old phrases return
CTAs feel wrong
emails sound unlike the brand
ads sound too hype-heavy
reports sound too robotic
social posts sound too polished
client feedback says “this does not sound like us”
spoken scripts sound like written articles
written outputs sound like raw transcripts
catchphrases appear too often
punctuation quirks are exaggerated
humour is overused
voice profile has no source period
voice profile has no reviewer or version
outputs imitate a public figure too closely
examples are copied instead of adapted
Repeated voice correction should trigger a Voice Architecture review.
Rewrite Versus Polish Rule
If the human reviewer only polishes small wording, voice may be acceptable.
If the human reviewer rewrites the whole tone, rhythm, structure, or phrasing, the Voice Architecture needs review.
Small edits are normal.
Repeated full rewrites signal voice decay.
Application To MWMS Internal Voice
MWMS internal documents must use operational clarity.
MCR pages should be:
structured
plain
direct
governed
not fluffy
not academic
not salesy
not chatty
not filled with course references
not filled with citations inside the page output
MWMS internal voice should support AI interpretation and governance.
Application To Content Brain
Content Brain uses Voice Architecture to create:
emails
social posts
newsletters
content briefs
headlines
hooks
educational content
belief-shift content
Content Brain must use VOC and Voice Architecture together.
VOC grounds the buyer reality.
Voice Architecture preserves the brand expression.
Application To Creative Brain
Creative Brain uses Voice Architecture to create:
ad hooks
VEO3 scripts
storyboards
thumbnail text
campaign concepts
visual prompt language
Creative Brain may stretch style for creative testing but must not violate approved voice, retired language, or compliance notes.
Application To Sales Brain
Sales Brain uses Voice Architecture to create:
sales scripts
follow-up messages
objection responses
proposal language
call summaries
sales emails
Sales Brain must preserve trust and avoid over-hype.
Application To AIBS Client Systems
Future AIBS client systems require client-specific Voice Architecture files.
Client voice must be isolated.
A client Voice Architecture should include:
client tone
client phrases
client banned phrases
client CTA style
client examples
client retired language
client compliance notes
client approval rules
client written voice profile
client spoken voice profile
approved source list
excluded source list
source period
validation samples
anti-caricature rules
version and review date
Client voice must not leak into MWMS internal voice or another client system.
Common Failure Modes
MWMS must prevent:
AI-generated generic voice
over-polishing founder language
mixing founder voice with buyer language
using old campaign language
using retired phrases
inventing customer wording
using compliance-risky claims for the sake of punchiness
making every client sound the same
making MCR pages sound like marketing pages
using voice files without human review
allowing voice examples to become stale
mixing written and spoken voice without review
overusing catchphrases
creating a caricature of the founder
building a profile from too little evidence
using unapproved source material
copying examples as templates
using stale profiles without version review
using public-figure analysis as impersonation
allowing voice to override facts, compliance, or task purpose
Governance Role
Content Brain owns the MWMS Voice Architecture And Brand Language Standard.
HeadOffice governs cross-Brain alignment, MCR voice discipline, and source-of-truth usage.
Offer Brain governs offer-specific language.
Creative Brain governs creative expression within voice boundaries.
Sales Brain governs sales language.
Conversion Brain governs conversion copy alignment.
Compliance Brain governs claim-sensitive language.
AIBS Brain governs future client voice architecture usage.
Individual Brains may define specialized voice usage, but they must align with this standard.
Relationship To Other MWMS Standards
This standard supports and must align with:
MWMS Document Structure Standard
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 Content Intelligence Scanner Framework
MWMS AI Brain Audit And Decay Prevention Framework
MWMS AI Brain Readiness Review Checklist
MWMS Tool-Agnostic Context Portability Protocol
Content Brain VOC Grounded AI Copy Framework
Research Brain Voice Of Customer Extraction Framework
Creative Brain Belief Shift Framework
Sales Brain Objection Resolution Framework
Conversion Brain Landing Page Structure Framework
Compliance Brain Claims Risk Framework
AIBS Brain Canon
This standard provides the voice and language governance layer for context-driven AI output.
Drift Protection
This standard protects MWMS from:
generic AI copy
voice flattening
over-polished language
old language returning
banned phrases reappearing
founder voice being replaced
client voices blending together
buyer language being invented
MCR pages becoming sales copy
public-facing claims becoming unsafe
AI Employees ignoring voice context
client systems producing off-brand output
Any language-heavy AI output produced without relevant Voice Architecture should be treated as a voice drift risk.
Architectural Intent
The architectural intent of the MWMS Voice Architecture And Brand Language Standard is to make voice reusable, governable, and portable across MWMS AI systems.
MWMS needs AI outputs that are not only correct, but recognizably aligned with the business, offer, founder, client, and buyer.
The long-term goal is that every serious brand or offer can answer:
How should this sound?
What should it never sound like?
What phrases should be preserved?
What phrases are banned?
What language has been retired?
How should CTAs sound?
How should humour be used?
How should emotion be handled?
What examples show the voice correctly?
What examples show the voice incorrectly?
When MWMS can answer these questions consistently, AI-generated content becomes more specific, more trusted, more brand-aligned, and safer to scale.
Change Log
Version: v1.1
Date: 2026-06-21
Author: HeadOffice
Change
Updated the MWMS Voice Architecture And Brand Language Standard using the AI Automations by Jack tone-of-voice extraction block.
Preserved the existing standard and added:
Voice Source Modality Separation
separate written and spoken voice profiles
Three-Level Voice Analysis Model
Micro-Level Analysis
Meso-Level Analysis
Macro-Level Analysis
Positive And Negative Example Rule
Voice Profile Record
Voice Profile Validation
Anti-Caricature Rule
Voice Profile Versus Task Instruction
Consent And Impersonation Rule
expanded Voice Extraction Workflow
expanded Voice Usage Rules
expanded Voice Validation Checklist
expanded Voice Drift Signals
expanded AIBS client voice requirements
expanded failure modes
Corrected all references from AI Business Systems Brain to the canonical AIBS Brain name.
Purpose of update:
To strengthen MWMS voice architecture from a general tone-and-language guide into a structured, modality-aware, evidence-based, versioned and human-validated voice system that preserves recognisable founder and brand communication without creating caricature, impersonation risk, or generic AI flattening.
v1.0 — Initial Draft
Created the MWMS Voice Architecture And Brand Language Standard as the standard for capturing, structuring, preserving, reviewing, and applying founder voice, brand voice, offer language, customer language, preferred phrasing, banned wording, retired language, tone rules, and communication style across MWMS AI-generated outputs and future AIBS client systems.
This standard defines Voice Architecture, Brand Language, voice file structure, tone rules, rhythm, preferred language, banned language, retired language, founder phrases, customer language usage, CTA style, humour rules, emotional register, platform adjustments, extraction workflow, usage rules, validation checklist, drift signals, Brain applications, governance role, drift protection, and architectural intent.
Change Impact Declaration
This v1.1 update strengthens the existing standard without changing its ownership, parent page, authority level, or core voice-governance purpose.
Pages Created
None
Pages Updated
MWMS Voice Architecture And Brand Language Standard
Pages Deprecated
None
Standalone Pages Not Created
MWMS Founder Written Voice Standard
MWMS Founder Spoken Voice Standard
MWMS Voice Profile Validation Framework
MWMS Anti-Caricature Voice Standard
MWMS Voice Modality Separation Framework
MWMS Voice Impersonation And Consent Standard
These concepts remain absorbed into the unified Voice Architecture And Brand Language Standard rather than created as separate pages.
Registries Requiring Update
None confirmed by the supplied source.
Canon Version Update Required
No
Change Log Entry Required
Yes
Employee Impact Check
Employees impacted:
Content Planner Employee
Creative Strategist Employee
Sales Strategist Employee
Conversion Strategist Employee
Offer Strategist Employee
Context Library Builder
Client IP Excavator
AIBS Architect Employee
HeadOffice Manager Employee
Required behaviour updates:
AI Employees must use the correct approved written or spoken Voice Architecture profile for the intended output.
AI Employees must analyse voice across micro-level, meso-level, and macro-level patterns.
AI Employees must use positive and negative examples where practical.
AI Employees must not exaggerate catchphrases, slang, punctuation quirks, humour, or founder mannerisms.
AI Employees must not use voice analysis to impersonate, misrepresent authorship, fabricate endorsement, or use private communications without authority.
AI Employees must keep task instructions, factual evidence, compliance rules, and voice context separate.
AI Employees must route repeated voice rewrites, profile mismatch, caricature, stale source periods, or impersonation risk into voice audit and human review.
Strategic Absorption Result
MWMS gains a stronger voice architecture system that separates written and spoken source material, analyses style at micro, meso and macro levels, validates profiles against unseen examples, prevents caricature, preserves version control, and blocks impersonation while maintaining brand-specific output.
END OF FULL FILE OUTPUT