Document Type: Standard
Status: Active
Authority: HeadOffice
Applies To: All MWMS Brains, MCR Structure, Page Creation, Page Updates
Parent: HeadOffice
Version: v1.0
Last Reviewed: 2026-04-24
Purpose
The MWMS Page Parent Map defines the correct parent structure for all page types across the MWMS system.
This standard exists to eliminate:
- incorrect page placement
- structural inconsistency
- duplication caused by misplaced pages
- time wasted searching for pages
- broken Brain architecture
This page is the single reference point for where pages must live.
Core Principle
Every page in MWMS must:
- have a clearly defined parent
- sit inside the correct Brain or system layer
- follow a consistent structural hierarchy
No page should exist:
- at root level (unless explicitly defined)
- under the wrong Brain
- duplicated under multiple parents
Top-Level Structure
All pages must sit under one of the following:
- HeadOffice
- A specific Brain
- A defined system container (if applicable)
HeadOffice Parent Structure
Pages that belong under HeadOffice:
Governance & Control
- MWMS How to Start a Session Operating Guide
- MWMS Canon Session Protocol
- MWMS AI Session Context Lock Rule
- MWMS AI Output Standard Full File Delivery Rule
- MWMS Decision Authority Matrix
System Architecture & Mapping
- MWMS Architecture Registry
- MWMS Brain Interaction Map
- MWMS System Data Flow Map
System Control & Tracking
- HeadOffice Page Registry
- MWMS System Improvement Log
- MWMS Page Parent Map
Cross-Brain Standards
- MWMS Brain Routing Rule
- MWMS Brain to Brain Request Protocol
- MWMS Brain Header Schema Standard
- MWMS Page Naming Standard
- MWMS Document Structure Standard
Brain Parent Structure
Each Brain must follow this structure:
Required Core Pages
- [Brain Name] Canon
- [Brain Name]
- [Brain Name] Architecture
Framework Pages
All frameworks must sit under:
→ [Brain Name] Canon
Examples:
- Affiliate Brain Offer Intelligence Framework
- Research Brain Signal Classification Framework
- Conversion Brain Friction Reduction Framework
Registry Pages
If present, must sit under:
→ [Brain Name]
Examples:
- Affiliate Brain Page Registry
- Ads Brain Creative Registry
System-Level Pages (Non-Brain Specific)
Pages that apply across multiple systems must sit under:
→ HeadOffice
These include:
- system-wide standards
- cross-brain coordination rules
- shared architecture definitions
Parent Assignment Rules
Rule 1 — Canon Ownership
All frameworks belong to their Brain Canon.
Rule 2 — No Frameworks Under Root Brain Page
Frameworks must NOT sit directly under:
- Affiliate Brain
- Research Brain
- etc.
They must sit under:
→ [Brain Name] Canon
Rule 3 — Registry Placement
Registries sit under the main Brain page, not Canon.
Rule 4 — HeadOffice Controls System Standards
Any page that affects multiple Brains must sit under HeadOffice.
Rule 5 — No Duplicate Parents
A page must exist in one location only.
No mirrored structures.
Rule 6 — Naming Must Match Placement
Page naming must clearly reflect its Brain ownership.
Example:
✔ Affiliate Brain Offer Intelligence
✖ Offer Intelligence
Validation Checklist (Use Before Saving Any Page)
Before saving or updating any page, confirm:
- correct parent assigned
- naming matches Brain ownership
- no duplicate page already exists
- page is not sitting at root level
- page type matches placement (framework vs registry vs system)
Common Errors This Prevents
- frameworks created under wrong Brain
- duplicate pages created due to poor visibility
- pages lost at root level
- cross-brain rules placed inside a single Brain
- broken architecture causing confusion during builds
System Impact
Following this structure ensures:
- clean navigation
- fast page discovery
- reliable system growth
- reduced duplication
- consistent Brain architecture
- easier AI-assisted development
Final Rule
If there is any uncertainty about where a page belongs:
→ default to HeadOffice
→ then validate before final placement
Status
This is now the official parent structure standard for MWMS.
All future page creation and updates must follow this map.