MWMS Opportunity System Phase Two Developer Build Pack


Document Type: Protocol
Status: Active
Version: v1.0
Authority: HeadOffice
Applies To: M (developer), mwmsbrain.site Phase 2 build execution
Parent: HeadOffice Brain
Last Reviewed: 2026-04-25


Purpose

This document defines the developer build requirements for Phase 2 of the MWMS Opportunity System.

Its purpose is to:

• provide a single source of truth for Phase 2 implementation
• eliminate ambiguity during development
• define exactly what must be built
• define what must not be built
• ensure correct system progression
• prepare clean input for Measurement Planning

This is the execution guide for building the Offer Intelligence system.


Scope

This protocol applies to:

• Affiliate Brain Offer Intelligence System
• mwmsbrain.site Phase 2 build
• evaluation UI and workflow

It defines:

• required screens
• required fields
• required actions
• state transitions
• completion criteria

It does not include:

• measurement planning UI
• forecasting systems
• testing system
• finance system
• dashboards
• automation


Core Principle

Build a structured evaluation system.

Do not build beyond evaluation.

This phase answers:

👉 “Is this opportunity worth testing?”

It does NOT answer:

👉 “How do we test it?”
👉 “What will it convert at?”


Phase 2 Build Target

System Name

Affiliate Brain Offer Intelligence System


Components To Build

• Offer Intelligence Queue
• Offer Intelligence Record
• Decision Panel
• Status Management System


1. Offer Intelligence Queue


Required Features

• display all evaluation records
• group by status
• allow record selection


Required Columns

• Product Name
• Platform
• Vendor
• Intake Source
• Strategic Interest (optional simple field)
• Status
• Confidence Level (optional)


Required Status Groups

• Under Evaluation
• Needs Work
• Rejected
• Ready For Measurement Planning


Required Actions

• Open Record
• Quick Reject
• Mark Needs Work
• Mark Ready For Measurement Planning


2. Offer Intelligence Record


Required Sections


Section A — Intake Summary (Read Only)

Display:

• Product Name
• Product Link
• Platform
• Vendor
• Discovery Source
• Initial Notes


Section B — Research Consolidation

Fields:

• Competitor Overview
• Ad Activity Summary
• Market Validation Notes
• Observed Angles

(Simple text fields — no complexity required)


Section C — Offer Quality Assessment

Fields:

• Offer Clarity (High / Medium / Low)
• Market Demand Signal (Strong / Medium / Weak)
• Competition Quality (High / Medium / Low)
• Funnel Quality (High / Medium / Low)
• Traffic Compatibility (High / Medium / Low)


Section D — Opportunity Scoring

Fields:

• Opportunity Score (simple number or rating)
• Confidence Level (Low / Medium / High)
• Risk Level (Low / Medium / High)


Section E — Strategic Fit

Fields:

• Fits MWMS (Yes / No / Borderline)
• Strategic Category (simple text)
• Expansion Potential (simple text)
• Long-Term Viability (simple text)


Section F — Decision Support

Fields:

• Strengths
• Weaknesses
• Key Risks
• Required Improvements


Section G — Decision Panel


Required Field

Final Decision (dropdown):

• Reject
• Needs Work
• Ready For Measurement Planning


Required Buttons

• Reject
• Send Back For Work
• Approve For Measurement Planning


3. Status Management System


Allowed Statuses

• Under Evaluation
• Needs Work
• Rejected
• Ready For Measurement Planning


Required Behavior

• status updates must persist
• UI must update immediately
• invalid transitions must be blocked


Progression Rules (CRITICAL)

System must enforce:

Before marking Ready For Measurement Planning:

• Offer Quality Assessment complete
• Opportunity Score assigned
• Risk Level assigned
• Fits MWMS selected

If missing:

→ block progression


System Behavior Requirements

The system must:

• save reliably
• allow editing at all times
• display data clearly
• prevent incomplete progression
• support multiple records


User Flow


Step 1

Martyn opens an intake record


Step 2

Record is escalated to Offer Intelligence


Step 3

Martyn completes evaluation sections


Step 4

Martyn selects decision


Step 5

Record moves to appropriate status


Completion Criteria


Phase 2 is complete when:

• records can be evaluated
• all sections can be filled
• decisions can be made
• progression rules are enforced
• status updates work
• system is easy to use
• system prepares clean output for next stage


Testing Requirements

M must verify:

• evaluation fields save correctly
• decision panel works
• status transitions work
• progression blocking works
• multiple records behave correctly
• no UI errors exist


What Not To Build

Do NOT include:

• measurement planning UI
• forecasting tools
• testing workflows
• finance logic
• dashboards
• automation
• AI features
• advanced scoring algorithms


Build Constraints

M must:

• keep UI simple
• avoid unnecessary complexity
• minimize clicks
• prioritize clarity
• avoid over-structuring inputs


Future Compatibility Rule

System must allow:

• adding measurement planning later
• linking to next-stage records
• expanding decision logic
• extending fields without rebuild


Dependencies

Derived from:

• Affiliate Brain Offer Intelligence Screen Specification
• MWMS Opportunity System Build Order
• MWMS Opportunity System Operating Protocol
• MWMS Opportunity System Implementation Brief For M


Controlled Loss Alignment

This phase supports the MWMS Controlled Loss Principle by:

• improving decision quality
• preventing poor test selection
• identifying risk before spend
• filtering weak opportunities early


Governance Role

This document ensures:

• Phase 2 is built correctly
• evaluation is structured
• decisions are controlled
• system progression remains intact
• clean input is passed to Data Brain


Drift Protection

The system must prevent:

• skipping evaluation
• testing without decision
• incomplete records
• overbuilding UI
• early measurement or testing logic


Architectural Intent

This build pack ensures MWMS evolves into:

👉 a decision system

not:

👉 a guess-based system

It ensures:

• better test selection
• lower risk
• cleaner system flow


Change Log

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


Change

Initial creation of Phase 2 Developer Build Pack aligned with updated Opportunity System Flow and Offer Intelligence Specification.


Pages Created

MWMS Opportunity System Phase Two Developer Build Pack


Pages Updated

None


Registries Requiring Update

None


End of Protocol