Document Type: Specification
Status: Active
Version: v1.0
Authority: Affiliate Brain
Applies To: mwmsbrain.site operational interface for Affiliate Brain intake workflow
Parent: Affiliate Brain Architecture
Last Reviewed: 2026-04-23
Purpose
This specification defines the exact operational screen used to capture and manage new affiliate opportunities inside mwmsbrain.site.
Its purpose is to translate the Affiliate Brain Offer Intake Form and Affiliate Brain Opportunity Intake Workflow into a usable interface that:
• allows structured opportunity entry
• supports intake-stage review decisions
• enables early rejection and escalation
• preserves decision lineage
• reduces uncontrolled loss risk
This page defines how the intake system must function at the interface level.
Scope
This specification applies to:
• Affiliate Brain intake screen UI
• opportunity record creation
• intake-stage workflow actions
• queue-based opportunity management
• interaction patterns for Martyn, M, and future operators
It defines:
• layout
• sections
• fields
• user actions
• system responses
• status transitions
It does not define:
• backend schema
• database implementation
• API design
• automation logic
Those are handled by development.
Definition Or Rules
Core Principle
The intake screen must prioritize:
• clarity
• speed of entry
• structured capture
• immediate usability
• decision support
It must not overload the operator.
Screen Structure
The intake system consists of two primary surfaces:
1. Opportunity Intake Queue (List View)
2. Opportunity Intake Record (Detail View)
1. Opportunity Intake Queue
Purpose
Provides a centralized view of all opportunities currently in intake stage.
Queue Columns
Each row must display:
• Product Name
• Platform
• Vendor
• Discovery Source
• Date Found
• Status
• Strategic Interest (optional visual flag)
Queue Filters
User must be able to filter by:
• Status (New / Under Review / Rejected / Escalated)
• Platform
• Discovery Source
• Date Range
Queue Sections (Visual Grouping)
• New
• Under Review
• Rejected
• Escalated
Queue Actions
Available actions from queue:
• Open Record
• Quick Reject
• Move to Under Review
• Escalate
Quick actions should require minimal clicks.
2. Opportunity Intake Record
Purpose
Provides full detail capture and review interface for a single opportunity.
Layout Structure
The record should be structured in collapsible sections:
Section A — Opportunity Source Identity
Fields:
• Product Name
• Product Link
• Platform
• Platform Confidence (Dropdown: Trusted / Unknown / Low)
• Vendor Name
• Discovery Source
• Discovery Agent
• Discovery Method
• Date Found
Section B — Initial Opportunity Notes
Fields:
• First Idea
• What Caught Attention
• Raw Notes
Section C — Vendor Marketing Material
Fields:
• Vendor Emails Available (Yes / No toggle)
• Email Angle Notes
• Swipe Material Available (Yes / No toggle)
• Hook / Promise Observations
Section D — Research And Market Evidence
Fields:
• Ads Found (Yes / No toggle)
• Ad Notes
• Competitors Found (Yes / No toggle)
• Competitor Links
• Competitor Notes
• Best Site Found
• Best Funnel Notes
• Estimated CPC
• Existing Angles Observed
• Signs Of Success
• Market Validation Notes
Section E — MWMS Fit Check
Fields:
• Fits MWMS (Yes / No / Unclear)
• Reason For Fit Decision
• Strategic Interest Level (Low / Medium / High)
• Category Acceptable (Yes / No)
• Exclusion Risk Flag
Section F — Exclusion Gate
Fields:
• Sex (Yes / No)
• Dating (Yes / No)
• Gambling (Yes / No)
• Other Risk Category (Yes / No)
If any = Yes:
→ System must visually flag record as Blocked
Section G — Intake Decision Panel
Fields:
• Status (Dropdown)
• Review Notes
Buttons:
• Reject
• Move to Under Review
• Escalate to Offer Intelligence
Status Logic
Allowed States
• New
• Under Review
• Rejected
• Escalated
State Rules
New
→ default on creation
Under Review
→ used when more research needed
Rejected
→ terminal state at intake
Escalated
→ creates Offer Intelligence record
Action Behavior
Reject
• requires reason
• sets Status = Rejected
• prevents further progression
Under Review
• sets Status = Under Review
• allows continued editing
Escalate
• sets Status = Escalated
• triggers creation of Offer Intelligence record
• links intake record to new record
System Feedback
The system must:
• confirm successful save
• visually update status
• highlight missing critical fields
• show warnings for incomplete intake
Required Fields Enforcement
The following must be present before escalation:
• Product Name
• Product Link
• Platform
• MWMS Fit decision
• Exclusion Gate completed
If missing:
→ Escalation must be blocked
Controlled Loss Alignment
This screen supports the MWMS Controlled Loss Principle by:
• enforcing structured intake
• capturing research before testing
• enabling early rejection
• preventing blind escalation
• improving decision quality
Governance Role
This screen ensures:
• Affiliate Brain logic is used consistently
• intake is not bypassed
• poor opportunities are filtered early
• better inputs reach evaluation stage
Relationship To Other MWMS Pages
This specification is based on:
• Affiliate Brain Offer Intake Form
• Affiliate Brain Opportunity Intake Workflow
• MWMS Controlled Loss Principle
These define the logic this screen implements.
Drift Protection
The system must prevent:
• skipping intake screen
• incomplete opportunity records
• escalation without required fields
• bypassing exclusion gate
• duplicate or fragmented records
Architectural Intent
This specification defines the first true operational surface of Affiliate Brain.
It transforms intake from:
a document
→
a usable system
It establishes the foundation for:
• structured opportunity flow
• controlled decision-making
• improved test selection
• reduced uncontrolled loss
Change Log
Version: v1.0
Date: 2026-04-23
Author: Affiliate Brain / HeadOffice
Change:
Initial creation of Affiliate Brain Intake Screen Specification defining queue view, record view, field structure, action logic, and operational behavior for mwmsbrain.site implementation.
Change Impact Declaration
Pages Created:
Affiliate Brain Intake Screen Specification
Pages Updated:
None
Pages Deprecated:
None
Registries Requiring Update:
None
Canon Version Update Required:
No
Change Log Entry Required:
No