Document Type: Specification
Status: Active
Version: v1.0
Authority: Affiliate Brain
Applies To: Affiliate Brain decision output and handoff into Experimentation Brain testing workflows
Parent: Affiliate Brain Architecture
Last Reviewed: 2026-04-23
Purpose
This specification defines the structured handoff from Affiliate Brain to Experimentation Brain when an opportunity is approved for testing.
Its purpose is to ensure that no opportunity enters testing without:
• sufficient research context
• structured evaluation output
• defined testing intent
• controlled risk visibility
• complete decision lineage
This specification prevents uncontrolled testing and reduces the probability of uncontrolled loss at the transition point between evaluation and execution.
Scope
This specification applies to:
• opportunities marked Ready For Testing inside Affiliate Brain
• creation of test-ready records
• transfer of structured data into Experimentation Brain
• enforcement of testing readiness conditions
It defines:
• required handoff data
• test readiness conditions
• handoff structure
• lineage requirements
• system behavior at transition
It does not define:
• testing execution
• experiment setup
• statistical methods
• budget allocation
Those are governed by Experimentation Brain and Finance Brain.
Definition Or Rules
Core Principle
An opportunity must not enter testing based on opinion alone.
Testing entry requires:
• structured evaluation
• evidence-backed reasoning
• defined test intent
• risk visibility
If these are not present, the opportunity must not be handed off.
Handoff Position In Flow
Opportunity Intake
↓
Offer Intelligence
↓
Evaluation Decision
↓
Handoff to Experimentation Brain
↓
Test Candidate Record
↓
Testing
Handoff Object
Test Candidate Record
When an opportunity is approved for testing, a new structured object must be created:
Test Candidate Record
This record becomes the input object for Experimentation Brain.
Required Handoff Data
The following data must be passed into the Test Candidate Record.
Section A — Opportunity Identity
• Product Name
• Product Link
• Platform
• Vendor Name
Section B — Source And Context
• Discovery Source
• Discovery Method
• Discovery Agent
• Date Found
Section C — Evaluation Summary
• Opportunity Score
• Confidence Level
• Risk Level
• Strengths
• Weaknesses
• Key Risks
Section D — Market Evidence
• Competitor Summary
• Ad Activity Summary
• Estimated CPC
• Observed Angles
• Market Validation Notes
Section E — Strategic Positioning
• Selected Angle(s) for Testing
• Target Audience
• Traffic Source Hypothesis
Section F — Test Intent
• Test Objective
• What is being tested (angle, hook, funnel, etc.)
• Expected outcome
Section G — Risk Visibility
• Primary Risk Factors
• Known Constraints
• Confidence Limitations
Test Readiness Gate
An opportunity must not pass into Experimentation Brain unless all required conditions are met.
Minimum Requirements
Before handoff, the following must be complete:
• Offer Intelligence evaluation complete
• Opportunity Score assigned
• Confidence Level defined
• Risk Level defined
• MWMS Fit confirmed
• Exclusion Gate passed
• At least one test angle defined
• Basic market evidence present
Blocking Conditions
Handoff must be blocked if:
• evaluation is incomplete
• research evidence is missing
• no clear angle exists
• no test objective is defined
• MWMS fit is unclear
• risk is not understood
Handoff Actions
Approve For Testing
When selected:
• creates Test Candidate Record
• transfers all required data
• links to Offer Intelligence record
• updates status to Ready For Testing
Reject Before Testing
Used when:
• new information invalidates the opportunity
• evaluation was incorrect
• risk becomes unacceptable
Outcome:
• Status updated to Rejected
• reason recorded
Return For Refinement
Used when:
• more research required
• angle unclear
• evaluation incomplete
Outcome:
• Status set to Needs Work
Lineage Requirements
The system must maintain full linkage between:
• Intake Record
• Offer Intelligence Record
• Test Candidate Record
This ensures:
• traceability
• accountability
• learning continuity
• ability to review decision quality
System Behavior
The system must:
• prevent incomplete handoff
• enforce required fields
• confirm successful creation of Test Candidate Record
• visually indicate readiness state
• flag missing data
Controlled Loss Alignment
This specification directly supports the MWMS Controlled Loss Principle by:
• preventing unstructured testing
• enforcing evidence-based entry
• requiring defined test intent
• ensuring risk visibility
• reducing uncontrolled capital exposure
Governance Role
This specification ensures:
• Affiliate Brain outputs are structured
• Experimentation Brain receives usable inputs
• testing begins with clarity
• decision discipline is preserved
Relationship To Other MWMS Pages
This specification operates alongside:
• Affiliate Brain Offer Intake Form
• Affiliate Brain Opportunity Intake Workflow
• Affiliate Brain Intake Screen Specification
• Affiliate Brain Offer Intelligence Screen Specification
• Experimentation Brain Structured Testing Protocol
• Finance Brain Capital Allocation Ladder
• MWMS Controlled Loss Principle
Drift Protection
The system must prevent:
• testing without evaluation
• missing handoff data
• unclear test intent
• broken lineage
• emotional decision-based testing
• premature testing escalation
Architectural Intent
This specification defines the critical transition from:
evaluation
→
execution
It ensures that every test entering Experimentation Brain is:
• intentional
• structured
• evidence-backed
• traceable
This is one of the most important control points in MWMS.
Change Log
Version: v1.0
Date: 2026-04-23
Author: Affiliate Brain / HeadOffice
Change:
Initial creation of Affiliate Brain To Experimentation Brain Handoff Specification defining test candidate structure, readiness gate, handoff requirements, and lineage control.
Change Impact Declaration
Pages Created:
Affiliate Brain To Experimentation Brain Handoff Specification
Pages Updated:
None
Pages Deprecated:
None
Registries Requiring Update:
None
Canon Version Update Required:
No
Change Log Entry Required:
No