Document Type: Standard
Status: Canon
Authority: HeadOffice
Applies To: Affiliate Brain
Parent: Affiliate Brain
Version: v1.0
Last Reviewed: 2026-04-04
Purpose
This document defines the observable signals indicating that an affiliate opportunity has reached sufficient maturity to justify submission of a structured Finance request.
The purpose is to ensure that capital allocation decisions occur only when sufficient structural validation exists.
This protects the MWMS system from premature scaling risk and preserves disciplined capital deployment.
Affiliate Brain does not request budget based on enthusiasm or perceived opportunity strength.
Requests are based on structured evidence signals.
Core Principle
Finance requests must be triggered by evidence, not belief.
Signals must demonstrate that:
the opportunity has passed initial structural validation
risk exposure is understood
expected behaviour has been observed
measurement conditions are stable
scaling inputs can be controlled
Finance decisions must be based on signal stability.
Not early optimism.
Position in System Flow
Offer Intake
→ Offer Intelligence
→ Velocity Decision Engine
→ Phase 4 Structured Testing
→ Signal Collection
→ Finance Request Readiness Signals
→ Finance Brain Review
→ Budget Allocation Decision
This page defines the final readiness criteria before Finance evaluation.
Signal Categories
Signals fall into five primary groups:
Structural Readiness
Market Response Stability
Measurement Reliability
Risk Containment
Operational Consistency
All groups must be satisfied before Finance request submission.
Structural Readiness Signals
The opportunity must demonstrate:
clear problem-solution structure
defined audience match
validated positioning logic
mechanism clarity
offer pathway stability
Offer must not depend on:
unclear positioning
weak mechanism explanation
untested assumptions
unverified audience fit
Structural uncertainty blocks Finance request eligibility.
Market Response Stability Signals
Evidence must indicate stable behavioural response patterns.
Examples:
consistent CTR range across tests
predictable engagement behaviour
absence of extreme performance volatility
no immediate signal collapse after initial test exposure
Observed behaviour must indicate repeatability potential.
Unstable response patterns indicate insufficient readiness.
Measurement Reliability Signals
Tracking environment must demonstrate:
consistent event capture
accurate click attribution
conversion event integrity
stable signal reporting
absence of unexplained anomalies
Signal noise must be within acceptable tolerance.
Measurement instability blocks Finance readiness.
Risk Containment Signals
Observed performance must demonstrate controlled downside exposure.
Examples:
no rapid performance collapse after budget increase
no sudden conversion failure patterns
no unexplained signal distortion
no structural funnel breakpoints
no abnormal refund indicators (if applicable)
Risk must be measurable.
Unbounded risk blocks Finance readiness.
Operational Consistency Signals
Execution environment must demonstrate stability.
Examples:
consistent creative delivery
stable landing page behaviour
no unresolved technical errors
no policy violations
no compliance flags
Execution environment must support controlled scaling conditions.
Operational instability blocks Finance request eligibility.
Minimum Signal Requirements
Finance readiness requires:
evidence from multiple test cycles
repeatable signal patterns
stable measurement environment
controlled performance variance
documented signal observations
Single-test performance is insufficient.
Observed stability must persist across exposure cycles.
Disqualification Conditions
Finance request must not be submitted if:
signal instability is present
measurement inconsistency exists
structural weaknesses remain unresolved
compliance uncertainty exists
execution environment is unstable
Premature Finance requests introduce capital risk.
Risk exposure must remain bounded.
Relationship to Velocity Decision Engine
Velocity determines whether the opportunity qualifies for structured testing.
Finance readiness determines whether the opportunity qualifies for controlled scaling capital.
Velocity protects testing discipline.
Finance protects capital discipline.
Both controls must remain independent.
Relationship to Experimentation Brain
Experimentation Brain validates statistical reliability of observed signals.
Finance readiness requires signal credibility.
Statistical instability blocks capital allocation.
Experimentation governance overrides scaling enthusiasm.
Governance Position
Affiliate Brain proposes.
Finance Brain allocates.
Experimentation Brain validates signal integrity.
HeadOffice retains final authority.
Capital allocation is not automatic.
It is conditional.
Outcome
Applying this framework ensures:
capital exposure occurs only under controlled conditions
scaling occurs only when structural signals support expansion
risk remains measurable and bounded
decision authority remains disciplined
Signal readiness protects system survivability.
Change Log
Version: v1.0
Date: 2026-04-04
Change: Page created
Author: HeadOffice