MWMS MCR To Brain Copy Rule

Document Type: Standard
Status: Active
Authority: HeadOffice
Applies To: All MWMS Brains, MCR Content, Brain Site (mwmsbrain.site), Future UI/Plugin Systems
Parent: HeadOffice
Version: v1.0
Last Reviewed: 2026-04-24


Purpose

The MWMS MCR To Brain Copy Rule defines how content moves from MCR into:

  • Brain environments (mwmsbrain.site)
  • plugin systems
  • UI interfaces
  • operational tools

This rule prevents:

  • duplication
  • unnecessary copying
  • structural confusion
  • broken source of truth
  • wasted build effort

MCR remains the central intelligence and governance layer.


Core Principle

MCR is always the Source of Truth.

No Brain, UI, or plugin system owns the original version of any page.

All downstream systems:

  • consume
  • display
  • operationalise

But do not replace MCR authority.


Three Destination Types

Every page must be classified into one of three destinations:


1. MCR Only

The page remains inside MCR and is not copied elsewhere.

Used for:

  • governance rules
  • Canon pages
  • system standards
  • architecture definitions
  • decision authority structures

These pages are:

  • read-only references
  • not operational tools
  • not used in workflows

2. Copy To Brain

The page is copied (or transformed) into the Brain environment.

Used for:

  • operational workflows
  • structured evaluation pages
  • repeat-use frameworks
  • decision-support tools
  • intake systems
  • execution guides

These pages are:

  • actively used by operators
  • part of daily workflow
  • potentially simplified for usability

3. Later Plugin or UI

The page should not be manually copied.

Instead, it will be:

  • converted into a system
  • turned into a UI
  • built into a plugin
  • powered by Supabase or automation

Used for:

  • dashboards
  • intake forms
  • registries
  • tracking systems
  • automation flows
  • signal logging
  • task execution

Classification Rule

Every page must be assigned:

FieldRequired Value
DestinationMCR Only / Copy To Brain / Later Plugin or UI
ReasonGovernance / Operational / Automation
Source of TruthAlways MCR

Decision Logic

Use this logic when classifying pages:

If the page defines rules → MCR Only

Examples:

  • naming standards
  • Canon protocols
  • authority structures

If the page is used regularly by a human → Copy To Brain

Examples:

  • offer evaluation
  • research workflows
  • decision frameworks
  • testing processes

If the page involves repeated structured interaction → Later Plugin/UI

Examples:

  • intake forms
  • dashboards
  • registries
  • tracking tables
  • reporting systems

Transformation Rule

When copying a page to a Brain:

  • simplify structure if needed
  • remove governance-only sections
  • keep operational logic intact
  • ensure usability for real workflows

The Brain version is:

  • a working version
  • not the canonical version

No Blind Copy Rule

Pages must NOT be copied:

  • without classification
  • without a defined use case
  • without a clear operator benefit

Blind copying leads to:

  • duplication
  • confusion
  • system bloat

Example Classification

PageDestinationReason
MWMS Page Naming StandardMCR OnlyGovernance
Affiliate Brain Offer IntelligenceCopy To BrainOperational
Affiliate Brain Opportunity QueueLater Plugin/UIAutomation
Research Brain Signal Classification FrameworkCopy To BrainOperational
HeadOffice Page RegistryLater Plugin/UISystem tracking

System Flow

  1. Page created or updated in MCR
  2. Page classified using this rule
  3. Destination assigned
  4. If required:
    • copied to Brain
    • scheduled for plugin/UI build
  5. MCR remains unchanged as source

Validation Checklist

Before copying any page, confirm:

  • destination clearly defined
  • real use case exists
  • no duplicate already exists
  • page is not governance-only
  • transformation (if needed) is understood

Common Errors This Prevents

  • copying every page into Brain unnecessarily
  • creating duplicate systems
  • mixing governance with operations
  • building UI before understanding usage
  • losing track of source of truth

System Impact

Following this rule ensures:

  • clean system separation
  • efficient Brain environments
  • scalable plugin architecture
  • reduced duplication
  • faster development cycles

Final Rule

If unsure:

→ default to MCR Only
→ classify later when usage becomes clear


Status

This is now the official rule for all MCR to Brain content movement.

All future copy decisions must follow this structure.