Affiliate Capital Request Trigger Points
Document Type: Framework
Status: Active
Version: v1.0
Authority: MWMS HeadOffice
Applies To: Affiliate Brain, Finance Brain
Parent: MWMS Routing Layer
Last Reviewed: 2026-04-03
Purpose
This page defines when Affiliate Brain must request capital approval from Finance Brain.
It ensures testing capital is deployed:
- at the correct stage
- with sufficient preparation
- without premature scaling
- without uncontrolled risk exposure
- with proper survivability discipline
Core Principle
Capital is requested only when a defined transition point is reached in the Affiliate workflow.
Capital is never deployed based on enthusiasm alone.
Each request must correspond to a structured learning objective or scaling objective.
Primary Trigger Points
Trigger 1 — Initial Exploration Test
Occurs when:
an offer has passed initial evaluation
core hook hypotheses exist
creative angles have been defined
tracking structure is prepared
Purpose:
test basic market response
collect initial signal data
measure traffic cost behaviour
Typical budget scope:
small controlled test
Trigger 2 — Validation Phase Expansion
Occurs when:
initial signals show promise
click-through behaviour meets expectations
traffic cost falls within acceptable range
Purpose:
confirm signal consistency
test additional hooks
test additional creatives
test audience variations
Typical budget scope:
moderate test budget
Trigger 3 — Conversion Structure Validation
Occurs when:
traffic signal is stable
click costs are predictable
initial conversion behaviour observed
Purpose:
confirm funnel behaviour
validate conversion assumptions
identify friction points
Typical budget scope:
moderate structured test budget
Trigger 4 — Optimisation Testing
Occurs when:
initial conversion data exists
performance variation observed
improvement opportunities identified
Purpose:
improve conversion rate
reduce cost per acquisition
identify stronger creative combinations
Typical budget scope:
controlled iterative budget
Trigger 5 — Scaling Preparation
Occurs when:
stable conversion signal exists
cost structure predictable
creative performance consistent
Purpose:
confirm scalability potential
test higher spend tolerance
observe signal stability at increased volume
Typical budget scope:
larger but still controlled budget
Trigger 6 — Controlled Scaling
Occurs when:
performance metrics stable
risk exposure acceptable
budget capacity confirmed
Purpose:
increase volume while maintaining profitability discipline
Typical budget scope:
increasing structured budget
Capital Discipline Rules
Affiliate Brain must not request scaling capital without:
validated signal behaviour
understood cost structure
repeatable creative response
Finance Brain may delay scaling approval if:
signal stability insufficient
risk concentration too high
capital availability limited
Relationship to Other Pages
Finance Affiliate Coordination Layer
Affiliate Finance Request Structure
Finance Brain Affiliate Testing Capital Request Protocol
Affiliate Brain Canon
MWMS Standard Conversion Signal Ladder
Architectural Role
This framework ensures capital deployment follows structured progression.
It prevents premature scaling and reduces survivability risk.
Future Expansion
Future versions may include:
automated trigger detection
signal threshold automation
cross-brain trigger validation
capital velocity balancing
risk-based trigger adjustment
Change Log
Version: v1.0
Date: 2026-04-03
Author: MWMS HeadOffice
Change: Initial creation of Affiliate Capital Request Trigger Points defining when capital requests occur within the Affiliate workflow.