MWMS Opportunity System Phase Two Developer Build Pack

Document Type: Protocol
Status: Active
Version: v1.0
Authority: HeadOffice
Applies To: M, mwmsbrain.site Phase 2 build execution, Affiliate Brain evaluation workflow, Supabase opportunity and evaluation records, plugin/UI implementation, future Brain Request expansion
Parent: HeadOffice Brain
Last Reviewed: 2026-05-11


Purpose

The MWMS Opportunity System Phase Two Developer Build Pack defines the controlled build requirements for Phase 2 of the MWMS Opportunity System.

Phase 2 begins only after Phase 1 has been accepted.

Phase 1 creates the intake system.

Phase 2 creates the evaluation system.

Its purpose is to:

  • give M a clear developer-ready build instruction for Phase 2
  • prevent M from guessing what comes after intake
  • define the first evaluation layer after opportunity capture
  • connect evaluation records back to Phase 1 opportunity records
  • keep the system simple and usable
  • prevent early measurement, forecasting, testing, Finance logic, dashboards, automation, or AI integrations
  • preserve future Supabase lineage
  • protect MCR as Source of Truth
  • prevent plugin/UI code from becoming hidden authority
  • prepare clean input for Phase 3 Measurement And Forecast System

This is the Phase 2 execution pack M should follow after Phase 1 is complete and accepted.


Scope

This protocol applies to:

  • mwmsbrain.site Phase 2 build
  • Affiliate Brain evaluation workflow
  • Offer Intelligence Queue
  • Offer Intelligence Record Screen
  • Evaluation Decision Panel
  • basic viability review
  • link between Phase 1 intake record and Phase 2 evaluation record
  • Supabase records where used
  • plugin/UI implementation
  • manual testing
  • safe save points
  • future Research Brain request expansion

It defines:

  • required Phase 2 features
  • required Phase 2 fields
  • required Phase 2 status logic
  • required decision actions
  • system behaviour
  • completion criteria
  • what must not be built yet
  • future compatibility requirements
  • safe save point requirements

It does not include:

  • Measurement Planning UI
  • Forecasting
  • Testing workflows
  • Finance controls
  • dashboards
  • automation
  • AI integrations
  • full Brain-to-Brain automation
  • full Research Brain workflow
  • MCR update automation

Core Principle

Phase 2 must turn a captured opportunity into a structured evaluation.

The goal is not to fully judge every detail of the offer.

The goal is to decide whether the opportunity is worth moving toward the next controlled stage.

Phase 2 must answer:

Is this opportunity worth further investigation, rejection, parking, or progression?

Phase 2 should remain simple, practical, and expandable.


Phase 2 Build Target

System Name

Affiliate Brain Offer Evaluation System

Components To Build

Phase 2 includes only:

  1. Offer Intelligence Queue
  2. Offer Intelligence Record Screen
  3. Evaluation Decision Panel
  4. Link To Phase 1 Opportunity Record
  5. Basic Research Request Preparation

Do not add additional modules during Phase 2.


Dependency Rule

Phase 2 must not begin until Phase 1 has passed:

MWMS Opportunity Intake Phase One Acceptance Checklist

Phase 2 depends on:

  • opportunity records being created
  • opportunity records saving correctly
  • opportunity records appearing in the queue
  • opportunity records being reopenable
  • status management working
  • no data loss
  • safe save point provided

If Phase 1 is unstable, Phase 2 must wait.


Source Of Truth Rule

MCR remains the Source of Truth.

This build pack gives M permission to build the approved Phase 2 operational surface on mwmsbrain.site.

It does not give permission to:

  • change MCR canon
  • create new MCR rules inside code
  • create direct Brain site to MCR updates
  • build automatic MCR editing
  • create hidden source-of-truth logic inside plugin/UI systems

If M discovers a missing rule, field, workflow, or conflict, M must report it back to Martyn/HeadOffice.

The correct path is:

M identifies issue → HeadOffice review → MCR decision if required

The prohibited path is:

M changes plugin logic → plugin becomes hidden canon


1. Offer Intelligence Queue

Required Features

The Offer Intelligence Queue must:

  • display opportunities that are ready for evaluation
  • show linked Phase 1 opportunity records
  • allow opening an evaluation record
  • show current evaluation status
  • allow filtering or grouping by evaluation status
  • make it clear which opportunities are unevaluated

Required Fields In Queue

The queue should show:

  • Product Name
  • Platform
  • Vendor Name
  • Discovery Source
  • Intake Status
  • Evaluation Status
  • Date Found
  • Last Updated where possible

Optional if easy:

  • Fits MWMS
  • Exclusion Flag
  • Research Needed

Required Evaluation Status Groups

The queue must support these evaluation statuses:

  • Not Started
  • In Review
  • Rejected
  • Parked
  • Research Needed
  • Ready For Measurement Planning

Required Actions

The queue should support:

  • Open Evaluation Record
  • Create Evaluation From Intake Record where needed
  • Change Evaluation Status where practical

Do not overcomplicate the queue.

The main requirement is that Martyn can find and open opportunities that need evaluation.


2. Offer Intelligence Record Screen

Required Purpose

The Offer Intelligence Record Screen is where Martyn reviews a captured opportunity and records the first structured Affiliate Brain evaluation.

It should not attempt to become a full research system, testing system, or finance system.

It is a practical evaluation screen.


Required Link To Phase 1 Intake Record

Each evaluation record must connect back to its original opportunity intake record.

The evaluation screen should show or reference:

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

The Phase 2 evaluation must not become disconnected from Phase 1 intake.


Required Evaluation Fields

The Offer Intelligence Record Screen must include the following fields.


Identity And Source Fields

These may be displayed from the intake record or copied into the evaluation record if needed:

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

Basic Offer Review Fields

  • Offer Type
  • Niche / Market
  • Target Audience
  • Primary Problem
  • Main Promise
  • Payout / Commission Notes
  • Funnel Type
  • Sales Page / VSL Link
  • Notes

Allowed values for Offer Type may include:

  • Affiliate Product
  • Lead Generation
  • Pay Per Lead
  • SaaS / Recurring
  • Ecommerce
  • Unknown
  • Other

Allowed values for Funnel Type may include:

  • VSL
  • Sales Page
  • Webinar
  • Lead Form
  • Quiz
  • Application
  • Unknown
  • Other

Basic Viability Fields

  • Commercial Potential
  • Audience Fit
  • Traffic Fit
  • Offer Clarity
  • Compliance Sensitivity
  • Competition Present
  • Research Needed
  • Evaluation Notes

Allowed values for Commercial Potential:

  • High
  • Medium
  • Low
  • Unknown

Allowed values for Audience Fit:

  • Strong
  • Moderate
  • Weak
  • Unknown

Allowed values for Traffic Fit:

  • Strong
  • Moderate
  • Weak
  • Unknown

Allowed values for Offer Clarity:

  • Clear
  • Somewhat Clear
  • Unclear
  • Unknown

Allowed values for Compliance Sensitivity:

  • Low
  • Medium
  • High
  • Unknown

Allowed values for Competition Present:

  • Yes
  • No
  • Unknown

Allowed values for Research Needed:

  • Yes
  • No
  • Unsure

Evaluation Decision Fields

  • Evaluation Status
  • Decision
  • Decision Reason
  • Next Step
  • Review Notes

Allowed values for Evaluation Status:

  • Not Started
  • In Review
  • Rejected
  • Parked
  • Research Needed
  • Ready For Measurement Planning

Allowed values for Decision:

  • Reject
  • Park
  • Request Research
  • Proceed To Measurement Planning
  • Needs More Information

Allowed values for Next Step:

  • No Action
  • Add More Info
  • Research Brain Review Later
  • Move To Measurement Planning Later
  • Reject And Archive
  • Park For Later
  • HeadOffice Review

3. Evaluation Decision Panel

Required Purpose

The Evaluation Decision Panel allows Martyn to make a controlled Phase 2 decision.

It must be simple.

It must not become an advanced scoring engine yet.


Required Decision Actions

Phase 2 must include these decision actions:

Reject

Sets:

  • Evaluation Status = Rejected
  • Decision = Reject

Used when the opportunity is clearly not worth further action.


Park

Sets:

  • Evaluation Status = Parked
  • Decision = Park

Used when the opportunity may be useful later but is not ready now.


Request Research

Sets:

  • Evaluation Status = Research Needed
  • Decision = Request Research

Used when the opportunity needs deeper validation before moving forward.

Phase 2 does not need to fully automate Research Brain work yet.

It only needs to mark that research is needed.


Proceed To Measurement Planning

Sets:

  • Evaluation Status = Ready For Measurement Planning
  • Decision = Proceed To Measurement Planning

Used when the opportunity has enough basic evaluation strength to move toward Phase 3.

Phase 3 must not be built inside Phase 2.

This action only prepares the pathway.


Needs More Information

Sets:

  • Evaluation Status = In Review
  • Decision = Needs More Information

Used when the opportunity is not ready for a decision.


Required Behaviour

Decision actions must:

  • save reliably
  • update evaluation status
  • preserve all record data
  • remain linked to the original intake record
  • avoid triggering unapproved automation
  • avoid creating automatic MCR updates

4. Link To Phase 1 Opportunity Record

Required Behaviour

Phase 2 must preserve the relationship between:

Opportunity Intake Record → Offer Evaluation Record

At minimum, the evaluation record should store or reference:

  • opportunity_id
  • product_name
  • platform
  • vendor_name
  • intake_status
  • evaluation_status

If Supabase is used, use stable naming that can later support:

  • opportunity_id
  • evaluation_id
  • brain_request_id
  • task_id
  • event_id
  • result_id
  • feedback_id

The evaluation record must not become an isolated object.


5. Basic Research Request Preparation

Purpose

Some evaluated opportunities will need Research Brain review later.

Phase 2 must prepare for that without building full cross-Brain automation too early.

Required Behaviour

When Martyn selects Request Research, the system should:

  • mark Evaluation Status as Research Needed
  • preserve the decision reason
  • preserve review notes
  • keep the record visible in the queue
  • make it easy to find later

What Not To Do Yet

Do not build full Research Brain automation in Phase 2 unless separately approved.

Do not build:

  • automatic Research Brain task creation
  • full Brain Request routing
  • AI research automation
  • Research Brain dashboard
  • advanced evidence scoring

For Phase 2, Research Needed is enough.


System Behaviour Requirements

The Phase 2 system must:

  • open evaluation records reliably
  • save evaluation fields correctly
  • preserve the link to the intake record
  • update evaluation status reliably
  • display evaluation records in the queue
  • support multiple evaluation records
  • allow basic decision actions
  • avoid confusing screens
  • avoid unnecessary complexity
  • avoid later-phase features

This system should feel like a practical review tool.


User Flow

Step 1

Martyn opens the Offer Intelligence Queue.

Step 2

Martyn selects an opportunity that came from Phase 1 intake.

Step 3

Martyn opens or creates an evaluation record.

Step 4

Martyn fills in basic evaluation fields.

Step 5

Martyn chooses one decision:

  • Reject
  • Park
  • Request Research
  • Proceed To Measurement Planning
  • Needs More Information

Step 6

The evaluation status updates.

Step 7

The record remains linked to the original intake record.


Completion Criteria

Phase 2 is complete when:

  • Phase 1 intake records can be linked to evaluation records
  • evaluation records can be created
  • evaluation records can be saved
  • evaluation records appear in the evaluation queue
  • evaluation records can be reopened
  • basic evaluation fields persist after reload
  • evaluation decisions can be made
  • evaluation status updates correctly
  • rejected records remain visible or retrievable
  • parked records remain visible or retrievable
  • research-needed records remain visible or retrievable
  • ready-for-measurement records remain visible or retrievable
  • no Phase 3, Phase 4, Finance, dashboard, automation, AI, or direct MCR update features were added
  • safe save point is provided

Testing Requirements

M must verify:

  • Phase 1 intake records are available for evaluation
  • evaluation record creation works
  • evaluation record save works
  • evaluation record reopen works
  • evaluation queue displays records
  • evaluation status updates work
  • decision actions persist correctly
  • multiple evaluation records behave correctly
  • evaluation record remains linked to intake record
  • data persists after reload
  • no later-phase features were added
  • no direct MCR update pathway exists

Testing should be manual and simple.

Do not build a full testing framework for Phase 2.


What Not To Build

Do not include:

  • Measurement Planning UI
  • Forecasting systems
  • Testing workflows
  • Finance logic
  • Dashboards
  • Automation
  • AI integrations
  • Advanced scoring
  • Full Research Brain automation
  • Full Brain Request routing
  • HeadOffice dashboard reporting
  • MCR update automation
  • Sync from Brain site back to MCR
  • Duplicate registries inside mwmsbrain.site

These are later phases.

Phase 2 must stay narrow.


Build Constraints

M must:

  • keep UI simple
  • avoid unnecessary features
  • minimize clicks
  • prioritize clarity
  • avoid premature structure complexity
  • avoid overengineering
  • maintain future expandability
  • preserve MCR authority
  • avoid hidden canon logic in code
  • keep evaluation linked to intake
  • create a stable second surface before adding future features

Future Compatibility Rule

Even though Phase 2 is simple, the system must allow future expansion.

The system should later be able to connect to:

  • Measurement Planning
  • Forecasting
  • Research Brain tasks
  • Experimentation Brain handoff
  • Finance Brain review
  • Brain Requests
  • task records
  • event records
  • result records
  • feedback records
  • HeadOffice visibility
  • dashboards

This does not mean building those features now.

It means avoiding hard-coded limitations that would block them later.


Supabase Future Lineage Rule

If Supabase is used in Phase 2, the structure must not block future lineage.

Phase 2 records should be able to later connect to:

  • opportunity_id
  • evaluation_id
  • offer_id
  • brain_request_id
  • task_id
  • event_id
  • result_id
  • feedback_id

Phase 2 does not need to fully implement these relationships.

But it must not be built in a way that prevents them later.

Tasks remain subordinate to future Brain Requests.


Event Logging Preparation

Where practical, Phase 2 should prepare for simple event logging.

Useful future events include:

  • evaluation_created
  • evaluation_updated
  • evaluation_status_changed
  • evaluation_rejected
  • evaluation_parked
  • research_needed
  • ready_for_measurement_planning

If event logging is not wired yet, M should note:

Event logging not yet wired

Do not fake logs.

Do not silently create unusable event records.


Brain Request Preparation

Phase 2 does not require full Brain Request automation.

However, the system should be designed so:

  • Request Research can later create a Research Brain Request
  • Proceed To Measurement Planning can later create a Data Brain / Experimentation Brain request
  • HeadOffice Review can later create a HeadOffice review request

For Phase 2:

  • Request Research may only set status to Research Needed.
  • Proceed To Measurement Planning may only set status to Ready For Measurement Planning.
  • Full cross-Brain routing comes later.

Do not build Phase 3 or full routing inside Phase 2.


Safe Save Point Requirement

At the end of a meaningful Phase 2 development session, M must provide a safe save point.

The save point should include:

  • what was built
  • what works
  • what does not work yet
  • what files were touched
  • what database tables or fields were touched
  • whether Supabase was changed
  • whether event logging was changed
  • what was tested
  • what still needs testing
  • next recommended step
  • any missing MCR instruction or blocker

This protects continuity.


Blocker Reporting Rule

If M hits uncertainty, M should not guess.

M should report the blocker clearly.

A blocker report should include:

  • what M was trying to build
  • what is unclear
  • what decision is needed
  • whether it affects UI
  • whether it affects Supabase
  • whether it affects MCR
  • whether it affects future phases
  • suggested safe temporary option if one exists

HeadOffice or Martyn then decides.


Dependencies

This build pack is governed by:

  • MWMS Opportunity System Implementation Control Brief
  • MWMS Opportunity System Implementation Brief For M
  • MWMS Opportunity System Build Order
  • MWMS Opportunity System Operating Protocol
  • MWMS Opportunity Intake Phase One Acceptance Checklist
  • MWMS Opportunity Intake Phase One Developer Build Pack
  • MWMS MCR To Brain Copy Rule
  • MWMS MCR Brain Wiring Map
  • MWMS Brain Connector Architecture
  • MWMS Brain To Brain Request Protocol
  • MWMS Standard Cross Brain Flow
  • MWMS Supabase Task Schema Standard
  • MWMS Plugin Build Instruction Standard

This build pack is derived from:

  • Affiliate Brain Offer Intelligence
  • Affiliate Brain Offer Intelligence Screen Specification
  • Affiliate Brain Evaluation Field Schema
  • Affiliate Brain Opportunity Intake Workflow
  • Affiliate Brain Offer Intelligence Page Template

Controlled Loss Alignment

This phase supports the MWMS Controlled Loss Principle by:

  • preventing weak opportunities from moving too quickly into testing
  • improving early-stage filtering
  • reducing wasted research
  • reducing wasted test spend
  • creating structured evaluation before measurement and forecasting
  • allowing poor-fit offers to be rejected or parked early

Governance Role

This document ensures:

  • Phase 2 build is executed correctly
  • development remains focused
  • evaluation happens before measurement and testing
  • system integrity is maintained
  • unnecessary complexity is avoided
  • future phases can be layered cleanly
  • MCR remains Source of Truth
  • M’s build lane stays clear
  • mwmsbrain.site becomes more practically useful
  • HeadOffice can later observe evaluation movement

Relationship To Other MWMS Pages

This protocol operates alongside:

  • MWMS Opportunity System Implementation Control Brief
  • MWMS Opportunity System Implementation Brief For M
  • MWMS Opportunity System Build Order
  • MWMS Opportunity System Operating Protocol
  • MWMS Opportunity Intake Phase One Developer Build Pack
  • MWMS Opportunity Intake Phase One Acceptance Checklist
  • MWMS MCR To Brain Copy Rule
  • MWMS MCR Brain Wiring Map
  • MWMS Brain Connector Architecture
  • MWMS Brain To Brain Request Protocol
  • MWMS Standard Cross Brain Flow
  • Affiliate Brain Offer Intelligence
  • Affiliate Brain Offer Intelligence Screen Specification
  • Affiliate Brain Evaluation Field Schema
  • Affiliate Brain Opportunity Intake Workflow
  • Affiliate Brain Offer Intelligence Page Template

Drift Protection

The system must prevent:

  • building Phase 3 early
  • adding unnecessary features
  • deviating from Phase 2 scope
  • incomplete evaluation implementation
  • early introduction of measurement or testing logic
  • hidden canon logic in code
  • MCR direct updates from Brain site
  • uncontrolled cross-Brain automation
  • disconnected evaluation records
  • fake event logs
  • future lineage dead ends
  • evaluation records disconnected from intake records

Architectural Intent

This build pack ensures MWMS moves from:

capturing opportunities

to:

evaluating opportunities

without jumping too early into testing, Finance, dashboards, or automation.

It provides:

  • real evaluation workflow
  • basic viability review
  • structured decision state
  • clean link back to intake
  • future expansion path

before expansion into measurement and forecasting.

The architectural intent is:

Evaluate before measuring. Measure before testing. Test before scaling.


Final Rule

Phase 2 is only the Affiliate Brain Offer Evaluation System.

Build:

  • Offer Intelligence Queue
  • Offer Intelligence Record Screen
  • Evaluation Decision Panel
  • Link to Phase 1 opportunity record
  • Basic Research Needed marker

Do not build:

  • measurement
  • forecasting
  • testing
  • finance
  • dashboards
  • automation
  • AI
  • full cross-Brain routing
  • MCR update automation

Keep it simple, stable, linked, and expandable.


Change Log

v1.0 — 2026-05-11

Initial creation of MWMS Opportunity System Phase Two Developer Build Pack.

Created to define the controlled Phase 2 build after Phase 1 intake acceptance.

Defines:

  • Offer Intelligence Queue
  • Offer Intelligence Record Screen
  • Evaluation Decision Panel
  • link to Phase 1 intake record
  • Research Needed marker
  • Phase 2 completion criteria
  • Phase 2 testing requirements
  • what not to build yet
  • Supabase future lineage rule
  • Brain Request preparation rule
  • safe save point requirement
  • blocker reporting rule
  • no direct Brain site to MCR update rule

Change Impact Declaration

Pages Created:
MWMS Opportunity System Phase Two Developer Build Pack

Pages Updated:
None

Pages Deprecated:
None

Registries Requiring Update:
Recommended: HeadOffice Page Registry

Canon Version Update Required:
No

Monthly Change Log Entry Required:
Recommended, because this creates a new developer build pack for Phase 2 of the MWMS Opportunity System.