System: MWMS
Document Type: Standard
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 Page And Asset Registry Standard.
This standard establishes how MWMS records, tracks, classifies, and governs the pages, context files, skills, assets, frameworks, protocols, checklists, client-brain components, and AI Employee support materials created during AI Brain build work.
MWMS must not create pages and assets without registry control.
As MWMS grows, it will create many related items:
framework pages
standard pages
protocol pages
checklists
context libraries
skills
asset templates
lead magnets
webinars
client intake documents
AI Employee instructions
audit records
offer libraries
client libraries
If these items are not registered, MWMS risks:
duplicate pages
lost assets
unclear ownership
wrong parent placement
unclear status
unclear destination
unclear Brain responsibility
untracked client materials
untracked context files
unreviewed assets being reused
MCR clutter
Brain site confusion
future AIBS delivery inconsistency
The AI Brain Page And Asset Registry Standard ensures that created intelligence remains findable, governed, and connected to the wider MWMS ecosystem.
Scope
This standard applies to all MWMS page and asset tracking related to AI Brain building, context library creation, course absorption outputs, client Brain onboarding, AI Employee skill creation, content asset systems, offer asset systems, and future AIBS client systems.
This includes:
MCR pages
Brain site pages
frameworks
standards
protocols
checklists
reference pages
context files
skill records
AI Employee records
lead magnet assets
webinar assets
content assets
sales assets
creative assets
audit records
client intake records
offer context libraries
client context libraries
This standard supports:
HeadOffice Brain
AI Business Systems Brain
AI Manager
AI Employee Router
Brain Room
Course Absorption System
Offer Brain
Content Brain
Creative Brain
Sales Brain
Conversion Brain
Customer Brain
Research Brain
Affiliate Brain
Ads Brain
future AIBS client systems
This standard does not authorize development work, plugin changes, Supabase changes, WordPress changes, automation wiring, or M developer action.
Core Definition
An AI Brain Page And Asset Registry is a structured record of what has been created, where it lives, what it is for, who owns it, what status it holds, and what it connects to.
The registry may track:
page title
document type
owning Brain
parent page
status
authority level
source of truth
destination
related standards
related assets
related skills
related context libraries
review status
change log requirement
employee impact
next action
The registry prevents MWMS from creating valuable materials that later become lost, duplicated, or misused.
Core Principle
The core principle of this standard is:
If MWMS creates reusable intelligence, it must be registered.
A page, skill, asset, or context file should not float without ownership.
Every reusable item should answer:
What is this?
Where does it live?
Who owns it?
What status does it have?
What does it support?
What should use it?
What should not use it?
Does it need review?
Does it need an update elsewhere?
This keeps MWMS scalable.
Registry Object Types
MWMS may register several object types.
Framework Page
A page defining a conceptual or operational framework.
Example:
MWMS Client IP Excavation Framework
Standard Page
A page defining required rules or structure.
Example:
MWMS Offer Context Library Standard
Protocol Page
A page defining a process or sequence of actions.
Example:
MWMS Client Brain Intake And Onboarding Protocol
Checklist Page
A page defining review or readiness checks.
Example:
MWMS AI Brain Readiness Review Checklist
Context File
A file used as AI-readable source context.
Examples:
Offer Profile
Voice Architecture
Objection Library
Proof Library
Skill Record
A reusable procedural AI skill.
Examples:
Course Absorption Skill
Voice Checker Skill
Client Report Drafting Skill
Asset Template
A reusable structure for creating an asset.
Examples:
Lead Magnet Outline Template
Webinar Outline Template
Client Report Template
Business Asset
A created deliverable or asset.
Examples:
lead magnet
webinar
email sequence
VEO3 script set
landing page draft
Audit Record
A record of review, drift, or readiness state.
Examples:
Context Library Audit
Skill Audit
Brain Readiness Review
Client Brain Component
A client-specific library, skill, workflow, report, or asset.
Example:
Client A Voice Architecture
Client A Content Brief Skill
Registry Fields
Each registered item should include the following fields where relevant.
Title:
Object Type:
Owning Brain:
Supporting Brains:
Parent Page:
Primary Location:
Future Operational Destination:
Authority Level:
Status:
Source Of Truth:
Purpose:
Related Standards:
Related Context Library:
Related Skills:
Related Assets:
Human Review Required:
Client-Specific:
Developer Boundary:
Change Log Required:
Registry Update Required:
Current Version:
Last Reviewed:
Next Review:
Notes:
Recommended Status Values
MWMS should use clear status values.
Draft
Created but not approved.
Draft For MCR
Prepared for MCR entry.
Active
Approved for use.
Canon
Official governing source.
Manual Use
Usable manually with review.
Assisted Use
Usable in assisted AI workflows.
Review Required
Needs human or HeadOffice review.
Parked
Useful later, not active now.
Deprecated
Replaced by newer material.
Retired
No longer used.
Archived
Preserved for history only.
Do not leave status unclear.
Registry Placement Rules
Rule 1: MCR Source Pages Must Be Registered
Any page intended for MCR must be added to the appropriate registry.
Rule 2: Brain-Specific Pages Must Be Registered In That Brain
If a page belongs to Content Brain, it must appear in Content Brain Page Registry.
If it belongs to Offer Brain, it must appear in Offer Brain Page Registry.
Rule 3: Cross-Brain Pages Need HeadOffice Awareness
If a page affects multiple Brains, HeadOffice registry awareness is required.
Rule 4: Client-Specific Assets Must Be Clearly Marked
Client assets must not be confused with general MWMS assets.
Rule 5: Draft Assets Must Not Be Listed As Active
Draft pages or assets must remain marked draft until reviewed.
Rule 6: Deprecated And Retired Items Must Stay Traceable
Do not silently delete important old materials unless safe deletion is approved.
Rule 7: Registry Must Match Actual Location
The registry must reflect where the page or file actually lives.
Do not list an asset as active in MCR if it has not been created there.
Creation Workflow
MWMS uses the following workflow when creating reusable pages or assets.
Step 1: Create Draft Output
Create the page, file, skill, asset, or checklist.
Step 2: Assign Object Type
Classify what it is.
Examples:
Framework
Standard
Protocol
Checklist
Context File
Skill
Asset
Audit Record
Step 3: Assign Owning Brain
Identify the Brain responsible for it.
Step 4: Assign Parent Page
Identify correct parent.
Step 5: Assign Status
Mark it as draft, active, canon, parked, or other correct status.
Step 6: Identify Related Standards
List the standards or frameworks it depends on.
Step 7: Identify Registry Destinations
Determine which registries require updates.
Step 8: Check Duplication Risk
Check whether similar page or asset already exists.
Step 9: Add Change Impact Declaration
For MCR pages, include required change impact declaration.
Step 10: Update Registry
Record the item in the relevant registry after human approval.
Registry Review Workflow
MWMS should periodically review registries.
Review questions:
Do all active pages still exist?
Are statuses current?
Are parent pages correct?
Are duplicate pages listed?
Are parked pages still parked?
Are deprecated pages clearly marked?
Are retired pages archived?
Are client assets separated?
Are cross-Brain pages visible to HeadOffice?
Are new pages missing from registries?
Are old pages no longer relevant?
Registry review should support MCR cleanliness and Brain clarity.
Duplicate Prevention Rules
Before creating a new page or asset, MWMS must check:
Does a similar page already exist?
Is this an update to an existing page?
Is this a merge candidate?
Is this a separate capability?
Does it belong under another Brain?
Is the name too close to an existing page?
Can this be added to a current standard instead?
Possible outcomes:
Create New Page
Update Existing Page
Merge Into Existing Page
Park For Later
Reject
Rename Proposed Page
No duplicate decision should remain unclear.
Client Asset Registry Rules
Future AIBS client assets require strict registry control.
Client asset records should include:
client name
client system
asset type
approval status
source context used
human reviewer
usage permission
review date
next review date
privacy level
client-specific restrictions
Client assets must not be registered as general MWMS assets unless deliberately generalized and approved.
Registry And Audit Relationship
Registries support audits.
The registry tells MWMS what exists.
Audits tell MWMS whether those things are still useful, accurate, and active.
Registry review and audit review should work together.
If the registry shows an active item that has not been reviewed, it may need an audit.
If an audit retires an item, the registry must update its status.
Common Failure Modes
MWMS must prevent:
pages created without registry updates
assets created without ownership
duplicate pages
wrong parent pages
draft pages treated as active
client assets mixed with MWMS assets
deprecated items still used
retired items not archived
change impact declarations missing
Brain-specific pages not added to Brain registries
cross-Brain pages hidden from HeadOffice
registries becoming outdated
Governance Role
HeadOffice owns the MWMS AI Brain Page And Asset Registry Standard.
HeadOffice is responsible for:
ensuring reusable intelligence is registered
preventing duplicate pages and assets
ensuring correct Brain ownership
ensuring correct parent placement
ensuring draft, active, parked, deprecated, and retired statuses are clear
ensuring registries remain current
ensuring client-specific assets are separated
ensuring MCR source-of-truth discipline
Individual Brains are responsible for maintaining their own page and asset registries in alignment with this standard.
AI Business Systems Brain governs future client asset registry behaviour.
Relationship To Other MWMS Standards
This standard supports and must align with:
MWMS Document Structure Standard
MWMS Page Naming Standard
MWMS MCR Promotion To Brain Protocol
MWMS Course Absorption Operating Rule
MWMS AI Brain Build Sequence Framework
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 AI Brain Readiness Review Checklist
MWMS AI Brain Audit And Decay Prevention Framework
MWMS AI Agent Memory And Context Framework
MWMS AI Agent Skill Library Framework
MWMS Architecture Registry
AI Business Systems Brain Canon
This standard provides the registry control layer for reusable AI Brain outputs.
Drift Protection
This standard protects MWMS from:
lost pages
lost assets
duplicate pages
wrong parent placement
unclear ownership
unclear status
untracked client assets
draft material being reused
deprecated material staying active
Brain registries becoming incomplete
MCR clutter
future AIBS client assets becoming ungoverned
Any reusable page, skill, context file, or asset without registry ownership should be treated as a drift risk.
Architectural Intent
The architectural intent of the MWMS AI Brain Page And Asset Registry Standard is to make MWMS intelligence findable, traceable, governed, and scalable.
MWMS will continue creating pages, frameworks, protocols, skills, assets, and client components.
The system needs a reliable way to know what exists.
The long-term goal is that every reusable MWMS item can answer:
What is this?
Where does it live?
Who owns it?
What status does it have?
What does it connect to?
Is it active?
Is it draft?
Is it client-specific?
Does it require review?
Does it replace something?
Does it need registry update?
When MWMS can answer these questions consistently, the ecosystem becomes easier to govern, easier to maintain, and safer to scale.
Change Log
v1.0 — Initial Draft
Created the MWMS AI Brain Page And Asset Registry Standard as the registry control standard for pages, assets, context files, skills, audit records, client components, and reusable AI Brain outputs.
This standard defines registry object types, registry fields, status values, placement rules, creation workflow, registry review workflow, duplicate prevention rules, client asset registry rules, registry-audit relationship, failure modes, governance role, drift protection, and architectural intent.
Change Impact Declaration
Pages Created:
MWMS AI Brain Page And Asset Registry Standard
Pages Updated:
None
Pages Deprecated:
None
Registries Requiring Update:
MWMS Architecture Registry
HeadOffice Page Registry
AI Business Systems Brain Page Registry
Content Brain Page Registry
Offer 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
Course Absorption Agent
AI Business Systems Architect Employee
Offer Strategist Employee
Content Planner Employee
Creative Strategist Employee
Sales Strategist Employee
Required behaviour updates:
AI Employees must identify object type, owning Brain, parent page, status, source of truth, and registry destination when creating reusable MWMS pages or assets.
AI Employees must not allow reusable frameworks, standards, protocols, checklists, context files, skills, or client assets to remain unregistered.
AI Employees must check duplicate risk before recommending new pages or assets.
AI Employees must keep client-specific assets clearly separated from general MWMS assets.
AI Employees must update relevant registry recommendations when pages are created, updated, deprecated, retired, parked, or archived.
END MWMS AI BRAIN PAGE AND ASSET REGISTRY STANDARD v1.0