Document Type: Standard
Status: Canon
Authority: HeadOffice
Applies To: Affiliate Brain, Experimentation Brain, Ads Brain
Parent: Affiliate Brain
Version: v1.0
Last Reviewed: 2026-04-04
Purpose
Testing Readiness Criteria defines the minimum structural conditions required before an opportunity may enter Phase 4 Structured Testing.
Its purpose is to ensure that testing begins only when sufficient preparation has occurred.
This prevents:
premature testing
confused signal collection
unclear offer positioning
avoidable tracking waste
unstructured traffic exposure
false learning caused by incomplete setup
Testing should begin only when the system can reasonably interpret the results.
Position in System Flow
Research Intelligence
→ Opportunity Queue
→ Offer Intelligence
→ Velocity Decision Engine
→ Testing Readiness Criteria
→ Phase 4 Structured Testing Protocol
→ Stage Progression Protocol
→ Finance Request
→ Controlled Scaling Protocol
Testing Readiness sits between approval and exposure.
Velocity grants permission.
Testing Readiness confirms operational preparedness.
Core Principle
An opportunity may be structurally viable but still not be operationally ready for testing.
Testing readiness requires more than opportunity quality.
Testing readiness requires:
clarity
preparedness
observability
controlled execution conditions
Without readiness, valid opportunities produce invalid learning.
Required Readiness Conditions
All of the following conditions should be satisfied before testing begins.
Opportunity Definition Readiness
The opportunity must have:
clear offer identification
clear mechanism description
clear audience definition
clear problem statement
clear hook direction
If the opportunity is still vague, testing should not begin.
Offer Intelligence Completion
Offer Intelligence must be sufficiently complete.
The evaluation must include:
mechanism clarity review
market demand alignment
hook potential review
funnel integrity review
compliance exposure review
traffic compatibility review
competitive context review
backend potential review
Incomplete evaluation reduces testing quality.
Velocity Approval Status
Velocity must have already produced one of the following:
YES
CONDITIONAL YES
A NO decision blocks testing.
Conditional YES may require additional constraints before testing begins.
Funnel Access Readiness
Testing requires access to the destination environment.
This may include:
landing page access
vendor funnel access
tracking destination availability
working checkout or lead form flow
mobile visibility review where applicable
Unavailable or unstable funnels block readiness.
Tracking Readiness
Signal collection requires observability.
Tracking should be sufficiently prepared to observe:
click behaviour
engagement behaviour
conversion behaviour
page interaction behaviour where relevant
Testing should not begin if the system cannot observe meaningful outcomes.
Creative Preparation Readiness
Testing requires at least minimum creative execution readiness.
This may include:
approved hook directions
defined angle variations
usable creative concepts
copy direction clarity
destination-message alignment
Testing should not begin if creative structure is undefined.
Compliance Readiness
Testing should not begin if unresolved compliance issues remain.
This may include:
claim ambiguity
platform policy conflicts
regulatory risk signals
identity transparency concerns
disallowed representation risk
Compliance uncertainty reduces survivability.
Traffic Source Readiness
The intended traffic source should be suitable for the offer.
This requires:
platform compatibility
message compatibility
audience awareness compatibility
offer explanation suitability
Wrong environment creates misleading learning.
Conditional Readiness Cases
An opportunity may be partially ready.
In such cases, testing may proceed only with constraints.
Examples:
reduced exposure
limited audience scope
single hook test only
tracking validation first
landing page observation first
Conditional readiness must be explicitly documented.
Readiness Failure Conditions
Testing readiness is blocked when:
offer definition remains vague
Offer Intelligence is incomplete
Velocity approval is absent
funnel access is unstable
tracking is insufficient
creative direction is undefined
compliance concerns remain unresolved
traffic environment is structurally mismatched
If blocked, the opportunity returns to the appropriate prior layer for correction.
Relationship to Velocity Decision Engine
Velocity determines whether the opportunity deserves testing consideration.
Testing Readiness determines whether the opportunity can actually enter testing safely.
Velocity answers:
Should this be tested?
Testing Readiness answers:
Can this be tested correctly now?
Both controls are required.
Relationship to Experimentation Brain
Experimentation Brain protects statistical integrity.
Testing Readiness protects setup integrity.
A valid statistical framework cannot compensate for broken setup conditions.
Readiness improves signal quality before statistical evaluation begins.
Relationship to Ads Brain
Ads Brain executes the testing environment.
Testing Readiness ensures Ads Brain receives a prepared opportunity rather than an undefined one.
Prepared structure improves creative and traffic execution quality.
Governance Rules
Testing must not begin because of urgency alone.
Testing must not begin because of intuition alone.
Testing must not begin because a vendor appears exciting.
Testing must remain disciplined.
Readiness protects decision quality.
Decision quality protects survivability.
Architectural Intent
Testing Readiness Criteria creates a final preparation checkpoint before exposure begins.
Its role is to ensure that the system does not confuse poor preparation with poor opportunity quality.
By separating viability from readiness, MWMS preserves learning quality and reduces avoidable signal contamination.
Change Log
Version: v1.0
Date: 2026-04-04
Author: HeadOffice
Change: Initial creation.
END Affiliate Brain Testing Readiness Criteria v1.0