MWMS AI Agent Operations Core Copy Map

System: MWMS
Document Type: Copy Map
Authority Level: MCR Source Of Truth
Status: Draft For MCR
Primary Location: MCR
Future Operational Destination: HeadOffice Brain, MWMS Brain, Brain Room, AI Manager, AI Employee Router, Task Executor Systems, Newsletter Intelligence, Course Absorption System, Opportunity System, AI Business Systems Brain
Parent Page: HeadOffice
Owner: Martyn
Developer Boundary: Do Not Touch M’s Active Build Areas Unless Specifically Assigned
Source Of Truth: MCR

Purpose

The purpose of this document is to define the MWMS AI Agent Operations Core Copy Map.

This copy map classifies each AI Agent Operations Core page according to where it belongs and how it should be used across MWMS.

The AI Agent Operations Core has produced a major governance layer for managing AI Employees, Agentic Work Units, orchestration, workflow pipelines, validation, normalization, reporting, handoffs, failure handling, outcome measurement, deployment readiness, capability stacks, tool permissions, memory, context, and workforce governance.

Not every page should be copied everywhere.

Some pages must remain MCR-only governance.

Some pages may later be simplified and copied into operational Brain sites.

Some pages may later become plugin screens, UI fields, dashboards, forms, task records, or developer build requirements.

This copy map exists to prevent confusion between:

MCR source-of-truth pages
operational Brain copies
dashboard/UI specifications
plugin or database implementation
future AIBS client packaging assets
developer build instructions

Scope

This copy map applies to all pages currently created under the MWMS AI Agent Operations Core.

It covers:

page destination
copy classification
operational role
developer relevance
Brain relevance
implementation priority
risk level
future transformation requirement

This copy map applies only at the planning and governance level.

It does not authorize immediate copying, plugin work, dashboard work, Supabase changes, or M development tasks.

Core Definition

The MWMS AI Agent Operations Core Copy Map defines how each AI Agent Operations Core page should be handled after creation in MCR.

Each page is classified into one or more of the following categories:

MCR Only
Copy To Brain Later
Operational Template Later
Later Plugin Or UI
Future Developer Brief
Future AIBS Packaging
Park For Later

This prevents MWMS from treating every governance page as a direct build task.

Core Principle

The core principle of this copy map is:

MCR remains the source of truth. Operational copies and technical builds must be derived carefully, simplified where needed, and never allowed to override MCR governance.

This means:

MCR pages define the standards.
Brain copies should simplify standards for daily use.
Plugin/UI builds should convert proven workflows into fields and screens.
Developer briefs should be precise and limited.
AIBS packaging should adapt the standards for client-facing clarity.
Nothing should be copied or built just because the page exists.

Copy Classification Definitions

1. MCR Only

A page classified as MCR Only should remain primarily in MCR as source-of-truth governance.

It may be referenced by other systems, but it should not be copied word-for-word into operational sites unless there is a specific reason.

Best for:

high-level governance
architecture standards
system-wide principles
registry pages
implementation maps
governance models

Rule:

MCR Only pages govern the system but do not need to become daily operating screens.

2. Copy To Brain Later

A page classified as Copy To Brain Later may eventually be copied into a Brain site in simplified form.

The copied version should be shorter, cleaner, and easier to use operationally.

Best for:

standards used by operators
workflow rules
validation checklists
reporting rules
handoff rules
AI Employee guidance

Rule:

Brain copies should preserve meaning but reduce complexity.

3. Operational Template Later

A page classified as Operational Template Later should later be transformed into a reusable template.

Best for:

role cards
work units
handoff packages
validation records
outcome records
failure logs
deployment checks

Rule:

Templates should convert governance into repeatable use.

4. Later Plugin Or UI

A page classified as Later Plugin Or UI contains concepts that may eventually become:

forms
fields
dashboards
status tabs
task records
Supabase tables
WordPress admin screens
Brain Room panels
AI Manager logic
employee router configuration
review queues

Rule:

UI and plugin work must only happen after manual proof and developer briefing.

5. Future Developer Brief

A page classified as Future Developer Brief may later be converted into exact build instructions for M or future developers.

The developer brief must include:

exact site
exact plugin/module
exact scope
exact data fields
exact screen behavior
exact routes if needed
what not to touch
test steps
save point awareness

Rule:

Governance is not a developer brief until it is translated into exact build scope.

6. Future AIBS Packaging

A page classified as Future AIBS Packaging may later be adapted into client-facing delivery assets.

Best for:

client AI employee systems
AI workflow packages
approval gates
reporting standards
permission models
outcome measurement
client dashboard structure

Rule:

AIBS copies must be business-friendly, not internal governance-heavy.

7. Park For Later

A page or concept classified as Park For Later is useful but not needed now.

Rule:

Parked material should not distract current build or course absorption work.

Page Copy Map

1. MWMS AI Agent Operations Core

Document Type: Core Operating Standard
Current Location: MCR
Parent Page: HeadOffice

Classification

MCR Only
Copy To Brain Later
Future AIBS Packaging

Reason

This is the foundation standard for the entire AI Agent Operations layer.

It defines the philosophy and governing model for treating AI as a structured workforce instead of casual prompts.

Copy Guidance

Do not copy the full page into operational sites yet.

Later, create a shortened operational version called something like:

AI Agent Operations Overview

This could be used inside HeadOffice Brain or AI Business Systems Brain.

Developer Relevance

Indirect only.

This page should not be sent to M as a build brief.

Priority

High as MCR governance.
Low as immediate implementation.

2. MWMS Agentic Work Unit Standard

Document Type: Operating Standard
Current Location: MCR
Parent Page: HeadOffice

Classification

Copy To Brain Later
Operational Template Later
Later Plugin Or UI
Future Developer Brief
Future AIBS Packaging

Reason

This page defines the core structure for turning AI requests into controlled work units.

It has strong future technical relevance.

Copy Guidance

Later, create a simplified operational template:

Agentic Work Unit Template

Likely fields:

Work Unit Title
Type
Source
Owning Brain
Assigned AI Employee
Input Payload
Context Pack
Required Output
Validation Level
Handoff Destination
Business Outcome
Priority
Risk Level
Status

Developer Relevance

Very high later.

This may influence Supabase task records, Brain Room task conversion, AI Manager routing, and Task Executor design.

Priority

High for future implementation, but only after manual proof.

3. MWMS AI Employee Role Card Standard

Document Type: Operating Standard
Current Location: MCR
Parent Page: HeadOffice

Classification

Copy To Brain Later
Operational Template Later
Later Plugin Or UI
Future Developer Brief
Future AIBS Packaging

Reason

This page defines how every AI Employee should be described and governed.

It is essential for building a real AI workforce.

Copy Guidance

Create a practical role card template later.

Possible simplified template:

Employee Name
Owning Brain
Purpose
Responsibilities
Non Responsibilities
Inputs
Outputs
Tools
Forbidden Actions
Validation
Handoff
Escalation
Outcome

Developer Relevance

Very high later.

This may become an AI Employee registry, employee configuration table, or router reference.

Priority

High for manual role design.
Medium for future build.

4. MWMS AI Agent Orchestration Framework

Document Type: Framework
Current Location: MCR
Parent Page: HeadOffice

Classification

MCR Only
Copy To Brain Later
Future Developer Brief
Future AIBS Packaging

Reason

This page defines how work is coordinated across Brains, AI Employees, workflows, validation, handoffs, and outcomes.

Copy Guidance

Do not copy full page directly.

Later, create a practical orchestration checklist for operational use.

Possible simplified version:

AI Workflow Orchestration Checklist

Developer Relevance

High later, especially for AI Manager and AI Employee Router logic.

But this page must be transformed into specific routing rules before M receives it.

Priority

High governance.
Medium implementation later.

5. MWMS AI Workflow Pipeline Standard

Document Type: Operating Standard
Current Location: MCR
Parent Page: HeadOffice

Classification

Copy To Brain Later
Operational Template Later
Later Plugin Or UI
Future Developer Brief
Future AIBS Packaging

Reason

This page defines the standard AI workflow sequence:

Input → Cleaning → Classification → Task → Assignment → Context → Processing → Validation → Decision → Routing → Logging → Learning

Copy Guidance

Create shorter pipeline templates later for:

Course Absorption Pipeline
Newsletter Intelligence Pipeline
Brain Room Pipeline
Offer Evaluation Pipeline
AIBS Client Workflow Pipeline

Developer Relevance

High later.

This page may inform workflow status fields and automation stages.

Priority

High for manual workflow design.
Medium for build.

6. MWMS AI Output Validation Standard

Document Type: Operating Standard
Current Location: MCR
Parent Page: HeadOffice

Classification

Copy To Brain Later
Operational Template Later
Later Plugin Or UI
Future Developer Brief
Future AIBS Packaging

Reason

This page is one of the most important trust-control standards.

It defines how AI outputs are checked before being accepted, routed, saved, displayed, automated, or acted upon.

Copy Guidance

Create practical validation checklists later for:

MCR page validation
Newsletter validation
Offer evaluation validation
Developer instruction validation
Dashboard item validation
AIBS client report validation

Developer Relevance

High later.

This may become validation statuses, review queues, pass/fail fields, and dashboard filters.

Priority

Very high.

This should be used manually immediately.

7. MWMS Messy Input Normalization Framework

Document Type: Framework
Current Location: MCR
Parent Page: HeadOffice

Classification

Copy To Brain Later
Operational Template Later
Later Plugin Or UI
Future AIBS Packaging

Reason

This page defines how messy inputs become usable intelligence.

It is especially relevant to newsletters, course files, pasted content, offer pages, screenshots, and future client data.

Copy Guidance

Later create simplified normalization templates for:

Newsletter input
Course transcript input
Offer page input
Brain Room message input
Client document input

Developer Relevance

Medium to high later.

Could influence preprocessing logic, data cleaning fields, or source capture screens.

Priority

High for manual use.
Medium for technical build.

8. MWMS Agentic Reporting Standard

Document Type: Operating Standard
Current Location: MCR
Parent Page: HeadOffice

Classification

Copy To Brain Later
Operational Template Later
Later Plugin Or UI
Future AIBS Packaging

Reason

This page defines how AI reports become decision-ready instead of passive summaries.

Copy Guidance

Create practical report templates later for:

Course Absorption Report
Newsletter Intelligence Report
Offer Evaluation Report
Developer Support Report
Validation Report
HeadOffice Dashboard Report
AIBS Client Report

Developer Relevance

Medium later.

Could influence dashboard cards, routed action cards, and report output formats.

Priority

High for manual reporting.

9. MWMS AI Employee Handoff Protocol

Document Type: Protocol
Current Location: MCR
Parent Page: HeadOffice

Classification

Copy To Brain Later
Operational Template Later
Later Plugin Or UI
Future Developer Brief
Future AIBS Packaging

Reason

This page defines how work passes safely between AI Employees, Brains, humans, queues, dashboards, MCR, developers, and clients.

Copy Guidance

Create short handoff templates later for:

Brain-to-Brain Handoff
AI Employee Handoff
Developer Handoff
MCR Page Handoff
Client Handoff

Developer Relevance

High later.

Could become handoff records, routing statuses, task transitions, and Brain-to-Brain request screens.

Priority

High for future Brain Room and AI Manager work.

10. MWMS AI Agent Failure Handling And Escalation Protocol

Document Type: Protocol
Current Location: MCR
Parent Page: HeadOffice

Classification

Copy To Brain Later
Operational Template Later
Later Plugin Or UI
Future Developer Brief
Future AIBS Packaging

Reason

This page defines how AI failures are detected, contained, escalated, logged, and converted into learning.

Copy Guidance

Later create practical templates for:

Failure Log
Escalation Decision
Automation Stop Condition
Failed Validation Review
Kaizen Failure Learning

Developer Relevance

High later.

Could influence error states, failure logs, task statuses, stop conditions, and escalation screens.

Priority

High for governance.
Medium for first build.

11. MWMS AI Agent Outcome Measurement Framework

Document Type: Framework
Current Location: MCR
Parent Page: HeadOffice

Classification

Copy To Brain Later
Operational Template Later
Later Plugin Or UI
Future AIBS Packaging

Reason

This page defines how MWMS measures whether AI work creates real business value.

Copy Guidance

Create simplified outcome scorecards later for:

AI Employee outcomes
Newsletter outcomes
Course absorption outcomes
Offer evaluation outcomes
Developer support outcomes
AIBS client outcomes

Developer Relevance

Medium to high later.

Could influence dashboards, scorecards, review cycles, and AI Employee performance tracking.

Priority

High for strategic governance.
Medium for technical implementation.

12. MWMS AI Agent Operations Core Page Registry

Document Type: Registry
Current Location: MCR
Parent Page: HeadOffice

Classification

MCR Only

Reason

This page records the AI Agent Operations Core page structure.

It prevents duplication and helps maintain the MCR page map.

Copy Guidance

Do not copy into operational Brain sites unless a shortened index is needed later.

Developer Relevance

Low.

This is a governance registry, not build material.

Priority

High for MCR organization.

13. MWMS AI Agent Deployment Readiness Checklist

Document Type: Checklist
Current Location: MCR
Parent Page: HeadOffice

Classification

Copy To Brain Later
Operational Template Later
Later Plugin Or UI
Future Developer Brief
Future AIBS Packaging

Reason

This page defines whether an AI Employee or workflow is ready to move from concept to operation.

Copy Guidance

Create a practical readiness checklist later for:

AI Employee deployment
Brain Room workflow deployment
Newsletter workflow upgrade
Offer evaluation workflow
AIBS client workflow

Developer Relevance

High later.

This should be used before asking M to implement AI workforce features.

Priority

Very high as a readiness gate.

14. MWMS AI Employee Capability Stack Framework

Document Type: Framework
Current Location: MCR
Parent Page: HeadOffice

Classification

Copy To Brain Later
Operational Template Later
Later Plugin Or UI
Future Developer Brief
Future AIBS Packaging

Reason

This page defines what capabilities each AI Employee has and what it must not do.

Copy Guidance

Create a simplified capability stack template later.

Possible fields:

Role Capability
Input Capability
Context Capability
Reasoning Capability
Tool Capability
Workflow Capability
Output Capability
Validation Capability
Handoff Capability
Escalation Capability
Learning Capability
Outcome Capability
Forbidden Capabilities

Developer Relevance

Very high later.

This may become part of AI Employee configuration and router logic.

Priority

High.

15. MWMS AI Tool Permission And Access Framework

Document Type: Framework
Current Location: MCR
Parent Page: HeadOffice

Classification

Copy To Brain Later
Operational Template Later
Later Plugin Or UI
Future Developer Brief
Future AIBS Packaging

Reason

This page controls how AI Employees access tools, APIs, files, databases, email, WordPress, Supabase, and client systems.

Copy Guidance

Create simplified tool permission matrices later.

Possible levels:

No Tool Access
Provided Input Only
Read Only
Draft Creation
Controlled Write
Supervised External Action
Restricted Autonomous

Developer Relevance

Very high later.

This should influence any future AI Manager tool routing, permission screens, task executor permissions, and client workflow controls.

Priority

Very high before any tool-enabled automation expansion.

16. MWMS AI Agent Memory And Context Framework

Document Type: Framework
Current Location: MCR
Parent Page: HeadOffice

Classification

Copy To Brain Later
Operational Template Later
Later Plugin Or UI
Future Developer Brief
Future AIBS Packaging

Reason

This page defines how AI Employees use memory, context, source of truth, task context, Brain context, developer context, business context, and client context.

Copy Guidance

Create practical context pack templates later.

Possible operational templates:

Task Context Pack
Developer Context Pack
Course Absorption Context Pack
Newsletter Context Pack
Offer Evaluation Context Pack
Client Context Pack

Developer Relevance

Very high later.

This may influence task context fields, AI Manager context injection, Brain Room thread context, and client memory isolation.

Priority

High for future AI Manager and AIBS systems.

17. MWMS AI Workforce Governance Model

Document Type: Governance Model
Current Location: MCR
Parent Page: HeadOffice

Classification

MCR Only
Copy To Brain Later
Future AIBS Packaging

Reason

This page defines the governance model for managing the total AI workforce.

It sits above individual AI Employee standards.

Copy Guidance

Do not copy full page into operational sites yet.

Later create a simplified version for HeadOffice Brain called:

AI Workforce Governance Overview

Developer Relevance

Medium later.

Useful for understanding future AI Employee registry and governance dashboards, but not a direct build brief.

Priority

High governance.
Low immediate implementation.

18. MWMS AI Agent Operations Core Implementation Map

Document Type: Implementation Map
Current Location: MCR
Parent Page: HeadOffice

Classification

MCR Only
Future Developer Brief
Future AIBS Packaging

Reason

This page defines how the AI Agent Operations Core should move from MCR governance into manual proof, operational templates, data structures, build, dashboards, and AIBS packaging.

Copy Guidance

Keep as MCR-only for now.

Later extract a short developer roadmap only when a specific build phase is approved.

Developer Relevance

High later, but only after translation into exact build briefs.

Priority

High for sequencing.
No immediate build.

Summary Copy Classification Table

Page	MCR Only	Copy To Brain Later	Template Later	Plugin Or UI Later	Developer Brief Later	AIBS Packaging
MWMS AI Agent Operations Core	Yes	Yes	No	No	No	Yes
MWMS Agentic Work Unit Standard	No	Yes	Yes	Yes	Yes	Yes
MWMS AI Employee Role Card Standard	No	Yes	Yes	Yes	Yes	Yes
MWMS AI Agent Orchestration Framework	Yes	Yes	No	Possible	Yes	Yes
MWMS AI Workflow Pipeline Standard	No	Yes	Yes	Yes	Yes	Yes
MWMS AI Output Validation Standard	No	Yes	Yes	Yes	Yes	Yes
MWMS Messy Input Normalization Framework	No	Yes	Yes	Yes	Possible	Yes
MWMS Agentic Reporting Standard	No	Yes	Yes	Yes	Possible	Yes
MWMS AI Employee Handoff Protocol	No	Yes	Yes	Yes	Yes	Yes
MWMS AI Agent Failure Handling And Escalation Protocol	No	Yes	Yes	Yes	Yes	Yes
MWMS AI Agent Outcome Measurement Framework	No	Yes	Yes	Yes	Possible	Yes
MWMS AI Agent Operations Core Page Registry	Yes	No	No	No	No	No
MWMS AI Agent Deployment Readiness Checklist	No	Yes	Yes	Yes	Yes	Yes
MWMS AI Employee Capability Stack Framework	No	Yes	Yes	Yes	Yes	Yes
MWMS AI Tool Permission And Access Framework	No	Yes	Yes	Yes	Yes	Yes
MWMS AI Agent Memory And Context Framework	No	Yes	Yes	Yes	Yes	Yes
MWMS AI Workforce Governance Model	Yes	Yes	No	Possible	Possible	Yes
MWMS AI Agent Operations Core Implementation Map	Yes	No	No	No	Yes	Yes

Immediate Manual Use Pages

The following pages can be used immediately without technical implementation:

MWMS AI Agent Operations Core
MWMS Agentic Work Unit Standard
MWMS AI Employee Role Card Standard
MWMS AI Workflow Pipeline Standard
MWMS AI Output Validation Standard
MWMS Messy Input Normalization Framework
MWMS Agentic Reporting Standard
MWMS AI Employee Handoff Protocol
MWMS AI Agent Failure Handling And Escalation Protocol
MWMS AI Agent Outcome Measurement Framework
MWMS AI Agent Deployment Readiness Checklist
MWMS AI Employee Capability Stack Framework
MWMS AI Tool Permission And Access Framework
MWMS AI Agent Memory And Context Framework

Manual use means:

apply during course absorption
apply during newsletter review
apply during Brain Room planning
apply during offer evaluation
apply during M developer handoff preparation
apply during HeadOffice dashboard review
apply during future AIBS planning

Pages Not To Send To M Yet

The following should not be sent to M as-is:

MWMS AI Agent Operations Core
MWMS AI Agent Operations Core Page Registry
MWMS AI Agent Orchestration Framework
MWMS AI Workforce Governance Model
MWMS AI Agent Operations Core Implementation Map
MWMS AI Agent Operations Core Copy Map

Reason:

They are governance-heavy and not specific enough for development.

If M needs them later, they must be converted into a precise developer brief.

Pages That May Become Developer Briefs Later

These pages have strong future build relevance:

MWMS Agentic Work Unit Standard
MWMS AI Employee Role Card Standard
MWMS AI Workflow Pipeline Standard
MWMS AI Output Validation Standard
MWMS AI Employee Handoff Protocol
MWMS AI Agent Failure Handling And Escalation Protocol
MWMS AI Agent Deployment Readiness Checklist
MWMS AI Employee Capability Stack Framework
MWMS AI Tool Permission And Access Framework
MWMS AI Agent Memory And Context Framework

Possible future developer briefs:

Brain Room Agentic Work Unit Conversion Brief
AI Employee Registry Brief
AI Tool Permission Field Brief
AI Output Validation Queue Brief
AI Handoff Record Brief
AI Outcome Log Brief
AI Failure Log Brief

Pages That May Become Operational Templates

The strongest template candidates are:

Agentic Work Unit Template
AI Employee Role Card Template
AI Employee Capability Stack Template
AI Tool Permission Record Template
AI Workflow Pipeline Checklist
AI Output Validation Checklist
Messy Input Normalization Record
Agentic Report Template
AI Employee Handoff Package
Failure Log Record
Outcome Log Record
Deployment Readiness Review

These templates should be created only when MWMS is ready to use them repeatedly.

Recommended Operational Copy Order

When MWMS later copies simplified versions into operational Brain sites, use this order:

Phase 1 — Core Practical Templates

Agentic Work Unit Template
AI Employee Role Card Template
AI Output Validation Checklist
AI Employee Handoff Package

Phase 2 — Workflow Control

AI Workflow Pipeline Checklist
Messy Input Normalization Record
Agentic Reporting Template
Failure Log Record

Phase 3 — Measurement And Deployment

Outcome Log Record
Deployment Readiness Review
Capability Stack Template
Tool Permission Record
Context Pack Template

Phase 4 — Governance Overview

AI Workforce Governance Overview
AI Agent Operations Overview

Future Brain Site Destinations

mwmsheadofficebrain.site

Best future copies:

AI Output Validation Checklist
AI Employee Handoff Package
Outcome Scorecard
Deployment Readiness Review
AI Workforce Governance Overview
HeadOffice Dashboard Report Template

Reason:

HeadOffice needs control, review, validation, and decision visibility.

mwmsbrain.site

Best future copies:

Agentic Work Unit Template
AI Employee Role Card Template
AI Workflow Pipeline Checklist
AI Employee Capability Stack Template
AI Tool Permission Record
AI Agent Memory And Context Pack

Reason:

mwmsbrain.site will likely support operational Brain workflows, AI Manager, Brain Room, and task execution.

AI Business Systems Brain

Best future copies:

AI Workforce Governance Overview
AI Employee Role Card Template
AI Tool Permission And Access Framework
Agentic Reporting Template
Client Handoff Template
Outcome Measurement Framework
Deployment Readiness Checklist

Reason:

AIBS needs client-facing packaging and delivery safety.

Brain Room

Best future copies:

Agentic Work Unit Template
Brain Room Task Context Pack
Handoff Package
Validation Checklist
Failure/Escalation Decision
Outcome State

Reason:

Brain Room should convert conversation into structured work.

Copy Rules

Rule 1: Do Not Copy Full Governance Pages Unless Needed

Most MCR pages are long and detailed.

Operational copies should be simpler.

Rule 2: Do Not Change Meaning During Simplification

A simplified operational copy must preserve the MCR rule.

Rule 3: MCR Remains Source Of Truth

If operational copy conflicts with MCR, MCR wins.

Rule 4: Do Not Create Plugin Work From Copy Map Alone

This copy map identifies possible future build relevance.

It does not authorize development.

Rule 5: Create Templates Before UI

Before building a plugin screen, create and test the template manually.

Rule 6: Prove Workflow Before Database Fields

Do not create fields until MWMS knows the workflow is useful.

Rule 7: Protect M’s Active Build

No AI Agent Operations page should interrupt M’s current active work unless Martyn specifically assigns it.

Rule 8: Avoid Duplicate Pages

Before creating any operational copy, check whether a similar page already exists.

Rule 9: Mark Drafts Clearly

Operational copies should show whether they are draft, active, parked, or under review.

Rule 10: Keep Client Copies Simpler

AIBS client-facing versions should be clearer, shorter, and less internal than MCR governance pages.

Copy Map Validation Checklist

Before copying any AI Agent Operations Core page, check:

Is the MCR source page saved?
Is the page registered?
Is there a real operational need?
Is this for Brain use, template use, UI use, developer use, or client use?
Is full copy necessary or should it be simplified?
Does an equivalent page already exist?
Does the copy preserve the original rule?
Is the destination correct?
Is the parent page correct?
Is the title correct?
Does this interfere with M’s active build?
Does this create premature implementation pressure?
Is human review required?
Does HeadOffice approve the copy?
Is the copied page clearly marked as operational copy if needed?

Governance Role

HeadOffice owns the MWMS AI Agent Operations Core Copy Map.

HeadOffice is responsible for:

deciding what remains MCR-only
deciding what may be copied later
deciding what becomes a template
deciding what may become plugin/UI logic
deciding what requires developer brief
deciding what may become AIBS packaging
preventing duplicate pages
preserving MCR as source of truth
protecting M’s active build areas
ensuring operational copies remain useful and accurate

Individual Brains may request operational copies, but HeadOffice controls the copy decision.

Relationship To Other MWMS Standards

This copy map supports and must align with:

MWMS AI Agent Operations Core
MWMS Agentic Work Unit Standard
MWMS AI Employee Role Card Standard
MWMS AI Agent Orchestration Framework
MWMS AI Workflow Pipeline Standard
MWMS AI Output Validation Standard
MWMS Messy Input Normalization Framework
MWMS Agentic Reporting Standard
MWMS AI Employee Handoff Protocol
MWMS AI Agent Failure Handling And Escalation Protocol
MWMS AI Agent Outcome Measurement Framework
MWMS AI Agent Operations Core Page Registry
MWMS AI Agent Deployment Readiness Checklist
MWMS AI Employee Capability Stack Framework
MWMS AI Tool Permission And Access Framework
MWMS AI Agent Memory And Context Framework
MWMS AI Workforce Governance Model
MWMS AI Agent Operations Core Implementation Map
MWMS Brain Routing Rule
MWMS Brain To Brain Request Protocol
MWMS Document Structure Standard
MWMS Page Naming Standard
MWMS Architecture Registry
MCR To Brain Copy Rule
AI Business Systems Brain Blueprint

This copy map applies the MCR-to-operational-copy discipline specifically to the AI Agent Operations Core.

Drift Protection

This copy map protects MWMS from the following forms of drift:

Copying every MCR page into Brain sites unnecessarily
Treating governance pages as plugin specs
Sending broad standards to M as build instructions
Creating duplicate operational copies
Losing MCR source-of-truth control
Simplifying pages so much that rules are weakened
Building UI before templates are proven
Creating Supabase fields before workflow is stable
Moving client-facing packaging too early
Confusing future relevance with current priority
Letting course-derived standards overwhelm active development
Interrupting M’s active build areas
Creating too many pages without operational need
Turning AI Agent Operations into clutter instead of structure
Treating copy classification as implementation approval

Any AI Agent Operations Core page movement should be checked against this copy map first.

Architectural Intent

The architectural intent of the MWMS AI Agent Operations Core Copy Map is to preserve the correct relationship between MCR governance and future operation.

The AI Agent Operations Core is powerful, but it must move carefully.

Its pages should not all become live workflows immediately.

The correct path is:

MCR source → copy decision → simplified operational template → manual proof → developer brief → controlled build → outcome review

This copy map protects that sequence.

The long-term goal is that every AI Agent Operations Core page has a clear destination:

stay as governance
become an operational template
become a Brain site copy
become plugin/UI logic
become a developer brief
become AIBS packaging
stay parked

When MWMS knows the destination of each page, it can expand without confusion.

Change Log

v1.0 — Initial Draft

Created the MWMS AI Agent Operations Core Copy Map to classify each AI Agent Operations Core page by destination and future use.

This copy map defines MCR-only pages, operational copy candidates, template candidates, plugin/UI candidates, future developer brief candidates, future AIBS packaging candidates, recommended copy order, future Brain site destinations, copy rules, validation checklist, governance role, drift protection, and architectural intent.