MWMS Opportunity System Implementation Brief For M

Document Type: Protocol
Status: Active
Version: v2.0
Authority: HeadOffice
Applies To: M (developer), mwmsbrain.site system implementation
Parent: HeadOffice Brain
Last Reviewed: 2026-04-25


Purpose

This document provides a clear, simplified implementation brief for M to begin building the MWMS Opportunity System.

Its purpose is to:

• define exactly where to start
• remove ambiguity from the build process
• prevent overbuilding or building out of order
• ensure alignment with MWMS architecture
• accelerate development speed
• ensure correct system foundations for later stages

This is not a design document.
This is a build execution guide.


Scope

This protocol applies to:

• mwmsbrain.site development
• UI surface implementation
• workflow wiring
• early-stage system deployment

It defines:

• starting point
• build sequence (first steps only)
• what to build
• what not to build yet
• success criteria

It does not define:

• full system architecture
• long-term roadmap
• deep automation
• forecasting systems
• reporting systems
• finance logic


Core Principle

Build the simplest usable system first.

Do not build the full MWMS vision in one pass.

Start with:

👉 one working flow
👉 one usable interface
👉 one real interaction


Starting Point (Non-Negotiable)

Build First:

Affiliate Brain Intake System

This includes:

• Opportunity Intake Queue
• Opportunity Intake Record Screen
• Intake Status System

Do not start anywhere else.


Measurement Awareness Rule (IMPORTANT)

Even though Measurement Planning and Forecasting exist in MWMS:

❌ Do NOT build them in Phase 1
❌ Do NOT add tracking logic yet

At this stage:

👉 We are only creating structured input

Measurement, forecasting, and reporting will be layered later.


What To Build (Phase 1 Only)


1. Opportunity Intake Queue

Must include:

• list of opportunities
• status grouping (New / Under Review / Rejected / Escalated)
• ability to open record
• basic filters


2. Opportunity Intake Record

Must include:

Core Fields

• Product Name
• Product Link
• Platform
• Vendor Name
• Discovery Source
• Date Found


Basic Research Fields

• Competitors Found (Yes / No)
• Ads Found (Yes / No)
• Notes


Fit Fields

• Fits MWMS (Yes / No)
• Exclusion Flag


Workflow Fields

• Status
• Review Notes


3. Status Actions

Must include:

• Reject
• Move to Under Review
• Escalate


What NOT To Build Yet

Do NOT build:

• Offer Intelligence screens
• Measurement Planning UI
• Forecasting systems
• Experimentation Brain
• Finance Brain logic
• Research Brain signal systems
• dashboards
• automation
• AI integrations
• advanced scoring
• cross-brain linking

These come later.


How To Interpret MCR Pages

MCR pages are:

👉 logic definitions
👉 not UI designs

M must:

• translate structure into simple UI
• not attempt to replicate full documents
• extract only what is needed for the screen


First Milestone (Critical)

Definition of DONE (Phase 1)

The system is usable when:

Martyn can:

• create a new opportunity
• fill in basic fields
• save the record
• see it in the queue
• change its status
• reject or escalate it


Build Approach


Step 1

Create basic database structure for:

• Opportunity Intake Record


Step 2

Build simple form UI


Step 3

Build queue list


Step 4

Add status actions


Step 5

Test manually


Development Rules

M must:

• prioritize speed over perfection
• build simple, clean UI
• avoid over-engineering
• keep fields minimal
• ensure stability before adding features


System Behavior Expectations

The system should:

• save reliably
• update status immediately
• display records clearly
• allow fast entry
• require minimal clicks


Controlled Loss Alignment

This phase supports the MWMS Controlled Loss Principle by:

• ensuring structured opportunity entry
• preventing random testing
• improving early filtering


Governance Role

This document ensures:

• development starts correctly
• system builds in the right order
• architecture is respected
• unnecessary complexity is avoided
• future system layers can be added cleanly


Relationship To Other MWMS Pages

This protocol is derived from:

• MWMS Opportunity System Build Order
• Affiliate Brain Offer Intake Form
• Affiliate Brain Opportunity Intake Workflow
• Affiliate Brain Intake Screen Specification


Drift Protection

The system must prevent:

• building later phases early
• adding unnecessary features
• overcomplicating the intake system
• introducing measurement logic too early
• deviating from defined starting point


Architectural Intent

This document ensures MWMS begins as:

👉 a working system

not:

👉 a theoretical system

It establishes:

• real usage
• real data
• real workflow
• real operator interaction

before expansion.


Change Log

Version: v2.0
Date: 2026-04-25
Author: HeadOffice


Change

Updated Implementation Brief to:

• align with updated Opportunity System Flow
• clarify Phase 1 boundaries
• prevent early measurement and forecasting build
• ensure correct system layering
• improve developer clarity


Pages Updated

MWMS Opportunity System Implementation Brief For M


Pages Created

None


Registries Requiring Update

None


End of Protocol