Status: Active
Version: v1.0
Authority: Affiliate Brain (Operational)
Parent: Affiliate Brain Canon
Linked Canon: Affiliate Brain Architecture v2.3
Last Updated: 2026-03-07
========================================================
PURPOSE
The Testing Definition Protocol defines the mechanical structure
required before a campaign test can be launched inside the
Affiliate Brain system.
It ensures that every test:
- has a declared structure
- uses valid optimisation signals
- defines traffic source discipline
- defines landing asset structure
- has a measurable revenue validation path
- can be interpreted correctly after launch
This protocol protects capital from undefined experiments
and ensures all tests generate usable learning signals.
========================================================
CORE PRINCIPLE
Undefined testing produces unreliable learning.
A valid test must define:
- traffic environment
- funnel structure
- optimisation signal
- validation signal
- revenue verification path
No test may proceed without these declarations.
========================================================
PROTOCOL POSITION IN ARCHITECTURE
Testing Definition occurs after:
Velocity Decision Engine
and before:
Phase 4 — Structured Testing
Flow position:
Velocity Decision Engine
↓
Testing Definition Protocol
↓
Phase 4 Structured Testing
========================================================
TEST DECLARATION REQUIREMENTS
A valid test must declare the following fields.
========================================================
1 — TRAFFIC SOURCE DECLARATION
Approved traffic sources for Affiliate Brain Phase-1:
- YouTube Ads
- Google Video Ads
- Google Display Ads
Rules:
Traffic source must be explicitly declared.
No test may operate across multiple traffic
sources simultaneously during initial testing.
Single-source tests produce clearer learning.
Output Field:
Traffic Source
========================================================
2 — LANDING ASSET TYPE
Approved landing structures:
- Bridge Page → VSL
- Direct-to-VSL
- Advertorial → VSL
Definitions:
Bridge Page → VSL
Pre-sell page introducing the mechanism
before directing traffic to the VSL.
Direct-to-VSL
Traffic lands directly on the VSL page
without a bridge page.
Advertorial → VSL
Editorial-style content presenting a problem,
mechanism, and authority narrative before
sending traffic to the VSL.
Output Field:
Landing Asset Type
========================================================
3 — PRIMARY OPTIMISATION SIGNAL
A test must declare a primary optimisation signal.
This signal is used by the advertising platform
for machine learning optimisation.
Examples:
- CTA click
- VSL buy button click
- order page visit
Rules:
Only one primary signal allowed.
Primary signal must represent meaningful buyer intent.
Engagement signals must never be primary signals.
Output Field:
Primary Optimisation Signal
========================================================
4 — SECONDARY VERIFICATION SIGNAL
Secondary signals help validate buyer intent
and provide additional signal density.
Examples:
- order page visit
- checkout page interaction
- product reveal click
Secondary signals assist interpretation
but are not the optimisation target.
Output Field:
Secondary Verification Signal
========================================================
5 — REVENUE VALIDATION SIGNAL
Every test must define a revenue validation path.
Examples:
- purchase confirmation page
- affiliate network postback
- subscription confirmation
Revenue signals confirm economic viability.
Rules:
Revenue validation may occur off-domain
in affiliate systems.
The revenue path must still be declared.
Output Field:
Revenue Validation Signal
========================================================
6 — ATTRIBUTION INTERPRETATION NOTE
Affiliate funnels often lose attribution
when the final purchase occurs on third-party domains.
Example:
Landing Page → VSL → Affiliate Checkout → Purchase
Tracking Governance must record:
- attribution gap risk
- consent impact
- server-side readiness
Testing Definition must record whether
interpretation caution is required.
Output Field:
Attribution Interpretation Level
Values:
Normal
Caution
High Attribution Loss Risk
========================================================
7 — TEST CAPITAL RANGE
Testing capital is declared to prevent uncontrolled
spending during early experimentation.
Recommended early-stage ranges:
Exploration Test
$100 – $300
Signal Learning Test
$300 – $800
Expanded Learning Test
$800
Capital ranges guide discipline
but do not override Finance Brain authority.
Output Field:
Test Capital Range
========================================================
TEST STRUCTURE TEMPLATE
Every test should produce a structured record.
Example:
Traffic Source:
YouTube Ads
Landing Asset Type:
Bridge Page → VSL
Primary Optimisation Signal:
CTA Click
Secondary Verification Signal:
Order Page Visit
Revenue Validation Signal:
Purchase Confirmation
Attribution Interpretation Level:
Caution
Test Capital Range:
$300 – $800
========================================================
FAIL CONDITIONS
Testing Definition fails if:
- traffic source not declared
- landing asset type undefined
- primary optimisation signal missing
- revenue validation path missing
Failure blocks Phase-4 testing.
========================================================
NON-BLOCKING RISK CONDITIONS
The following do not block tests
but must be logged for interpretation discipline:
- high attribution loss risk
- server-side tracking not implemented
- weak first-party data capture
- consent status unknown
These factors influence interpretation of results.
========================================================
DRIFT PROTECTION
The system must block:
- running tests without declared signals
- engagement signals used as optimisation targets
- multiple traffic sources in early testing
- undefined revenue validation paths
========================================================
ARCHITECTURAL ROLE
The Testing Definition Protocol ensures that:
- all experiments are structured
- optimisation signals are intentional
- traffic sources are controlled
- learning signals are interpretable
It protects the capital allocation engine
from undefined testing.
Testing Definition does not approve capital.
Velocity remains the capital gatekeeper.
========================================================
CHANGE LOG
v1.0 — 2026-03-07
Initial creation of Testing Definition Protocol.
Defined test declaration fields including:
- traffic source
- landing asset type
- optimisation signal
- verification signal
- revenue validation
- attribution interpretation
- capital range discipline
END OF TESTING DEFINITION PROTOCOL v1.0