MWMS MCR

MWMS MCR Brain Wiring Map

Document Type: Reference
Status: Active
Authority: HeadOffice
Applies To: HeadOffice, MCR, All MWMS Brains, mwmsbrain.site, mwmsheadofficebrain.site, Future Brain Sites, Plugin Systems, UI Systems, Supabase Execution Systems
Parent: HeadOffice
Version: v1.2
Last Reviewed: 2026-05-11

Purpose

The MWMS MCR Brain Wiring Map defines the controlled wiring relationship between MCR and downstream operational surfaces inside the MWMS ecosystem.

This page explains how MWMS knowledge moves from:

MCR → Brain Sites → Plugin/UI/Supabase Execution → Operational Feedback → HeadOffice Review → MCR Decision

It exists to make the following explicit before any page copying, UI build, plugin build, Brain-surface expansion, or Supabase-connected execution work occurs:

  • page role
  • source-of-truth location
  • copy eligibility
  • operational dependency
  • plugin/UI destination
  • Brain site readiness
  • feedback routing
  • fail-safe requirements
  • HeadOffice review authority

This page prevents:

  • premature page copying
  • duplicated authority logic
  • MCR to Brain drift
  • Brain to MCR direct-update drift
  • accidental creation of competing source-of-truth pages
  • operational confusion between canonical structure and live surfaces
  • plugin/UI systems becoming hidden authority layers
  • Supabase execution becoming disconnected from MCR rules

This page is not a temporary scratch list.

This page is the governed mapping layer used to determine where MWMS knowledge should remain canonical and where future operational surfaces should later be copied, transformed, displayed, automated, or built.

Scope

This reference applies to:

  • MCR to mwmsbrain.site wiring decisions
  • MCR to mwmsheadofficebrain.site wiring decisions
  • MCR to future Brain-site copy decisions
  • page-role classification across MWMS
  • first-pass continuity risk identification
  • fail-safe identification for critical pages
  • Affiliate Brain classification
  • Research Brain classification
  • Experimentation Brain classification
  • Finance Brain classification
  • HeadOffice Brain classification
  • cross-Brain coordination surfaces
  • plugin/UI build planning
  • Supabase execution planning
  • controlled expansion of MWMS execution surfaces
  • Brain-site feedback routing back to HeadOffice

This page governs structural classification and destination planning.

It does not by itself:

  • approve implementation work
  • approve plugin build work
  • replace Brain canon
  • replace registry pages
  • replace connector architecture
  • replace dashboard specifications
  • allow Brain sites to update MCR directly
  • allow plugin/UI systems to become source-of-truth layers

Core Principle

MWMS must not copy pages simply because they seem important.

Importance alone does not determine destination.

Destination is determined by structural role.

The core wiring rule is:

MCR is the Source of Truth. Brain sites are operational environments. Plugin/UI systems are execution surfaces. Supabase stores and supports approved execution. HeadOffice reviews feedback before MCR changes.

The approved authority path is:

MCR → Brain Site → Plugin/UI/Supabase Execution

The approved learning path is:

Brain Site → HeadOffice Review → MCR Decision

The prohibited path is:

Brain Site → MCR Direct Update

Definition Of MCR

MCR is the canonical Source of Truth for MWMS.

MCR owns:

  • canon pages
  • governance rules
  • architecture definitions
  • Brain structures
  • standards
  • copy maps
  • page registries
  • authority rules
  • cross-Brain protocols
  • build specifications
  • approved structural logic

MCR defines what the system is.

MCR does not act as the live operating surface for daily Brain work.

Definition Of Brain Sites

Brain sites are downstream operational environments.

They may include:

  • mwmsbrain.site
  • mwmsheadofficebrain.site
  • future Brain-specific sites
  • working Brain pages
  • operating manuals
  • simplified frameworks
  • workflows
  • dashboards
  • task views
  • Brain Room surfaces
  • plugin/UI screens
  • Supabase-connected tools

Brain sites use MCR-approved knowledge to perform work.

Brain sites do not replace MCR.

Definition Of Plugin/UI/Supabase Execution

Plugin, UI, and Supabase systems are execution layers.

They may:

  • display approved Brain content
  • collect structured data
  • trigger tasks
  • store operational records
  • show dashboards
  • manage queues
  • route requests
  • surface status
  • log events
  • support Brain Room interaction
  • support employee execution

They must not:

  • define canon
  • rewrite MCR pages
  • become hidden source-of-truth layers
  • bypass HeadOffice approval
  • create unapproved governance logic

Classification Fields

Each page must first be classified by the following fields:

FieldPossible Values
Source Of TruthMCR / Brain Site / Shared System Layer
Page RoleGovernance / System Architecture / Decision Engine / Operational Tool / Registry / UI Or Plugin Surface / System Structure
Copy NowYes / No
Later Plugin Or UIYes / No
Operational DependencyNone / Low / Medium / High / Critical
Fail Safe RequiredYes / No
Feedback PathNone / HeadOffice Review / MCR Decision Required
NotesContext-specific explanation

Decision Rules

Rule 1 — Governance And Architecture Stay In MCR

If a page defines governance, architecture, routing logic, validation, authority, standards, or decision rules:

Source Of Truth = MCR
Copy Now = No

Examples include:

  • MWMS Page Naming Standard
  • MWMS Document Structure Standard
  • MWMS Brain Routing Rule
  • MWMS Architecture Registry
  • MWMS Canon Session Protocol
  • MWMS AI Output Standard Full File Delivery Rule

Rule 2 — Operational Pages May Be Copied Or Transformed

If a page is used regularly by a human operator to perform work:

Copy Now = Possible
Destination = Relevant Brain Site

Examples include:

  • offer evaluation workflows
  • research workflows
  • testing workflows
  • decision-support frameworks
  • operating models
  • handoff instructions
  • working checklists

These pages must remain aligned to their MCR source.

Rule 3 — Dashboards And Structured Systems Become Plugin/UI

If a page represents dashboards, control panels, structured records, queues, forms, or UI surfaces:

Later Plugin Or UI = Yes

Examples include:

  • opportunity queues
  • dashboard specifications
  • intake forms
  • task screens
  • registries
  • signal logs
  • reporting systems

These should not be manually copied as ordinary content pages unless HeadOffice explicitly approves a temporary working version.

Rule 4 — Operational Importance Does Not Justify Duplication

A page being important does not mean it should be copied.

If the page is critical but canonical, use:

Fail Safe Required = Yes

Do not duplicate authority.

Rule 5 — Registries Are Not Manually Copied

Registries should not be cloned into Brain sites as uncontrolled copies.

They should be:

  • kept canonical in MCR
  • displayed through UI later if needed
  • powered by system data where appropriate
  • referenced by Brain sites without becoming competing registries

Rule 6 — Protocols And Standards Remain Canonical Unless Systemized

Protocols and standards remain MCR-owned unless HeadOffice approves:

  • a simplified Brain reference version
  • a UI checklist
  • a plugin validation rule
  • a dashboard indicator
  • an automation guardrail

Rule 7 — Brain Sites May Report Feedback But Not Rewrite MCR

Brain sites may generate:

  • improvement suggestions
  • workflow friction reports
  • missing-field alerts
  • dashboard gaps
  • operational lessons
  • task failure signals
  • plugin/UI improvement requests

But all such feedback must route to:

HeadOffice Review → MCR Decision

Brain sites must never directly update MCR canon.

Direction Of Movement

MovementAllowed?Rule
MCR → mwmsbrain.siteYesApproved through copy map, build pack, or HeadOffice decision
MCR → mwmsheadofficebrain.siteYesApproved for HeadOffice operational reporting and command surfaces
MCR → Future Brain SiteYesApproved through Brain-specific copy map
MCR → Plugin/UI SpecificationYesApproved through build specification
MCR → Supabase ExecutionYesApproved through schema/task specification
Brain Site → HeadOffice FeedbackYesAllowed as operational signal
Brain Site → MCR Direct UpdateNoProhibited
Plugin/UI → MCR Direct UpdateNoProhibited
Supabase Automation → MCR Direct UpdateNoProhibited
HeadOffice → MCR UpdateYesApproved authority path

Continuity Interpretation

MCR and Brain sites have different risk profiles.

MCR Failure

MCR failure creates structural risk.

It affects:

  • canon
  • governance
  • source-of-truth access
  • standards
  • architecture
  • page registries
  • copy maps

Correct response:

  • backup
  • export
  • fail-safe documentation
  • protected access
  • controlled recovery process

Not uncontrolled duplication.

Brain Site Failure

Brain site failure creates operational risk.

It affects:

  • workflows
  • dashboards
  • task execution
  • Brain Room surfaces
  • plugin screens
  • operational visibility
  • Supabase-connected actions

Correct response:

  • plugin backup
  • Supabase continuity
  • UI rebuild instructions
  • operating packs
  • HeadOffice visibility
  • recovery documentation

Not MCR authority transfer.

MCR To Brain Operating Flow

The approved MCR to Brain operating flow is:

  1. Page exists or is created in MCR.
  2. Page is classified by role and destination.
  3. HeadOffice determines whether the page is:
    • MCR Only
    • Copy To Brain
    • Later Plugin Or UI
  4. If Copy To Brain:
    • page is transformed into a working version
    • governance-only content may be reduced
    • operational logic is preserved
  5. If Later Plugin Or UI:
    • page becomes a build specification
    • M or future developers build the operational surface
  6. Brain site uses the approved working version.
  7. Plugin/UI/Supabase systems execute approved workflows.
  8. Brain site produces operational feedback.
  9. HeadOffice reviews feedback.
  10. HeadOffice decides whether MCR should change.

Brain Site Readiness Requirements

Before expecting a Brain site to do useful work, it must have enough operational content from MCR.

A Brain site should not be treated as “ready” just because the WordPress site or plugin exists.

Brain site readiness requires:

  • operating pages
  • workflow maps
  • handoff instructions
  • screen specifications
  • task definitions
  • dashboard specifications
  • copy maps
  • relevant Brain role definitions
  • Supabase schema references where needed
  • plugin/UI instructions where needed
  • feedback path to HeadOffice

A Brain site without approved operational content is only a container.

A Brain site becomes useful when approved MCR content is copied, transformed, displayed, or systemized into working surfaces.

Brain Classification Blocks

Affiliate Brain First Pass

Summary Block

Brain: Affiliate Brain
Source Of Truth: MCR
Primary Role: Canonical offer, opportunity, and affiliate decision system
Copy Now: Select operational pages only
mwmsbrain.site Later: Dashboard Metrics, Command Dashboard, Opportunity Queue, Intake Screen, Offer Intelligence Screen
Operational Dependency: High to Critical
Fail Safe Required: Yes
Feedback Path: HeadOffice Review
Notes: Architecture-first system. Operational workflows may be copied or transformed. Queues and dashboards should become plugin/UI surfaces.

Likely Copy To Brain

  • Affiliate Brain Opportunity Intake Workflow
  • Affiliate Brain Offer Intelligence
  • Affiliate Brain Research Signal Intake Framework
  • Affiliate Brain To Experimentation Brain Handoff Specification
  • Affiliate Brain Testing Readiness Criteria
  • Affiliate Brain Scaling Readiness Indicators

Likely Later Plugin Or UI

  • Affiliate Brain Opportunity Queue
  • Affiliate Brain Intake Screen Specification
  • Affiliate Brain Offer Intelligence Screen Specification
  • Affiliate Brain Command Dashboard
  • Affiliate Brain Dashboard Metrics

Research Brain First Pass

Summary Block

Brain: Research Brain
Source Of Truth: MCR
Primary Role: Canonical intelligence, evidence, market, customer, and signal interpretation system
Copy Now: Select operational pages only
mwmsbrain.site Later: Signal surfaces, handoff flows, analysis outputs, research task screens
Operational Dependency: High to Critical
Fail Safe Required: Yes
Feedback Path: HeadOffice Review
Notes: Upstream intelligence layer feeding Affiliate, Experimentation, Content, Strategy, and HeadOffice decisions.

Likely Copy To Brain

  • Research Brain Offer Opportunity Research Task Specification
  • Research Brain Offer Source Validation Framework
  • Research Brain Offer Evidence Standards
  • Research Brain Market Analysis Method
  • Research Brain Research Verdict Framework
  • Research Brain Test Learning And Signal Capture Framework
  • Research Brain Research Affiliate Handoff Protocol

Likely Later Plugin Or UI

  • Research Brain Intelligence Database
  • Research Brain Research Signal Logging Structure
  • Research Brain Research Source Registry Model
  • Research Brain Affiliate Opportunity Flow
  • Research Brain Copy Map

Experimentation Brain First Pass

Summary Block

Brain: Experimentation Brain
Source Of Truth: MCR
Primary Role: Canonical testing validation, experiment governance, and statistical enforcement system
Copy Now: Select operational pages only
mwmsbrain.site Later: Testing dashboards, validation panels, experiment tracking, statistical outputs
Operational Dependency: Critical
Fail Safe Required: Yes
Feedback Path: HeadOffice Review
Notes: Enforcement layer between Affiliate decisions and Finance capital exposure.

Likely Copy To Brain

  • Experimentation Brain Test Result And Decision Workflow
  • Experimentation Brain Test Candidate Screen Specification
  • Experimentation Brain Decision and Execution Framework
  • Experimentation Brain Experiment Validity Framework
  • Experimentation Brain Testing Trap Prevention Framework
  • Experimentation Brain Signal Confidence Framework
  • Experimentation Brain Stage Progression Protocol

Likely Later Plugin Or UI

  • Experimentation Brain Experiment Registry System
  • Experimentation Brain Testing Intelligence Log
  • Experimentation Brain Test Candidate Screen Specification
  • Experimentation Brain Finance Brain Capital Readiness Flow
  • Experimentation Brain Warehouse Based Test Analysis Framework

Finance Brain First Pass

Summary Block

Brain: Finance Brain
Source Of Truth: MCR
Primary Role: Canonical capital governance, survivability, risk, allocation, and financial control system
Copy Now: Select operational pages only
mwmsbrain.site Later: Capital readiness panels, approval systems, risk dashboards, escalation flows
Operational Dependency: Critical
Fail Safe Required: Yes
Feedback Path: HeadOffice Review
Notes: Final authority layer controlling exposure, pacing, risk, and survival.

Likely Copy To Brain

  • Finance Brain Capital Allocation Ladder
  • Finance Brain Financial Risk Escalation Logic
  • Finance Brain Phase 4 Testing Financial Discipline
  • Finance Brain Ads Testing Threshold Alignment
  • Finance Brain Risk Adjusted Testing Allocation Framework
  • Finance Brain Capital Preservation Framework
  • Finance Brain Financial Decision Confidence Framework

Likely Later Plugin Or UI

  • Finance Brain Test Budget And Capital Control Specification
  • Finance Brain Dashboard Financial Signal Indicators
  • Finance Brain HeadOffice System Posture Flow
  • Finance Brain Forecast Review Cycle
  • Finance Brain Page Registry

HeadOffice Brain First Pass

Summary Block

Brain: HeadOffice Brain
Source Of Truth: MCR
Primary Role: Cross-Brain command, review, governance, reporting, and decision oversight
Copy Now: Select operational pages only
mwmsheadofficebrain.site Later: Command dashboards, system reporting, newsletter intelligence surfaces, cross-Brain control panels
Operational Dependency: Critical
Fail Safe Required: Yes
Feedback Path: HeadOffice Internal Review
Notes: HeadOffice controls whether operational learning becomes MCR change.

Likely Copy To Brain

  • HeadOffice Cross Brain Decision Overview
  • HeadOffice Action Driven Reporting Standard
  • HeadOffice Newsletter Intelligence Operating Protocol
  • HeadOffice Newsletter Brain Routing Review Framework
  • HeadOffice Newsletter Insight Parking System
  • HeadOffice System Signal Overview Framework
  • HeadOffice Priority Visibility Framework

Likely Later Plugin Or UI

  • HeadOffice Cross Brain Performance And Control Dashboard Specification
  • HeadOffice Newsletter Intelligence Dashboard Specification
  • HeadOffice Active Command Dashboard
  • HeadOffice Weekly System Movement Dashboard
  • HeadOffice UI MWMS System Command Center Specification
  • HeadOffice UI Signals Dashboard Specification

System-Level Insight

Across the first operational Brain group:

  • Affiliate Brain → Opportunity and offer decision
  • Research Brain → Intelligence and evidence
  • Experimentation Brain → Validation and test discipline
  • Finance Brain → Capital control and survivability
  • HeadOffice Brain → Oversight and MCR decision authority

Unified result:

Copy Now = Select operational pages only
Dashboards, queues, registries, and structured controls = Later Plugin Or UI
Governance, canon, standards, and architecture = MCR Only

Fail Safe Requirements

Fail-safe planning is required for critical Brain systems.

Fail-safe planning may include:

  • MCR backup
  • copy map backup
  • plugin export
  • Supabase schema backup
  • task schema backup
  • dashboard rebuild instructions
  • Brain operating pack
  • HeadOffice review process
  • manual fallback workflow
  • data export process

Fail-safe does not mean duplicate the Source of Truth.

Fail-safe means preserve continuity without creating competing authority.

Governance Role

This page ensures:

  • HeadOffice maintains full structural visibility
  • MCR remains authoritative
  • mwmsbrain.site evolves correctly
  • mwmsheadofficebrain.site receives the correct operational reporting surfaces
  • cross-Brain logic is not duplicated
  • plugin/UI build work follows MCR-approved specifications
  • Supabase execution follows approved schemas
  • system drift is prevented
  • Brain-site feedback routes through HeadOffice before MCR change

Relationship To Other MWMS Standards

This page works alongside:

  • MWMS MCR To Brain Copy Rule
  • MWMS Brain Build Order Standard
  • MWMS Brain Connector Architecture
  • MWMS Standard Cross Brain Flow
  • MWMS Brain To Brain Request Protocol
  • MWMS Page Parent Map
  • MWMS Page Naming Standard
  • MWMS Document Structure Standard
  • MWMS Supabase Task Schema Standard
  • MWMS Plugin Build Instruction Standard
  • MWMS Opportunity System Operating Protocol

The MWMS MCR To Brain Copy Rule defines the copy classification rule.

This page defines the wiring relationship between MCR and downstream operating surfaces.

Drift Protection

The system must prevent:

  • copying pages without classification
  • duplicating governance logic
  • cloning registries
  • treating dashboards as source-of-truth
  • bypassing MCR authority
  • letting Brain sites directly edit MCR
  • letting plugin/UI systems define canon
  • letting Supabase execution create unapproved rules
  • external tracking replacing internal mapping
  • operational convenience overriding governance

No downstream system may become the hidden Source of Truth.

Architectural Intent

This page converts:

ad hoc page copying

into:

controlled architectural wiring

It ensures MWMS scales:

  • cleanly
  • predictably
  • operationally
  • without duplication
  • without authority drift
  • without confusing canon with execution
  • without blocking practical Brain-site work

The intended structure is:

MCR writes the law. Brain sites do the work. Plugin/UI systems make the work easier. Supabase stores execution data. HeadOffice decides what learning becomes canon.

Change Log

v1.1 — 2026-04-23

Added Experimentation Brain and Finance Brain summary blocks.

Completed full four-Brain first-pass wiring classification.

Confirmed system-wide Copy Now = None state.

v1.2 — 2026-05-11

Updated the wiring map to align with the expanded MCR To Brain Copy Rule.

Added:

  • MCR → Brain Site → Plugin/UI/Supabase execution path
  • Brain Site → HeadOffice Review → MCR Decision feedback path
  • Brain to MCR direct-update ban
  • HeadOffice Brain classification
  • Brain Site readiness requirements
  • direction of movement table
  • clearer distinction between Brain sites, plugin/UI systems, and Supabase execution
  • revised Copy Now position from “None approved” to “select operational pages only”
  • stronger drift protection for downstream execution systems

Change Impact Declaration

Pages Created:
None

Pages Updated:
MWMS MCR Brain Wiring Map

Pages Deprecated:
None

Registries Requiring Update:
None

Canon Version Update Required:
No

Change Log Entry Required:
Optional — only required if HeadOffice wants this wiring change recorded in the current MWMS System Change Log.