Document Type: Specification
Status: Active
Version: v2.4
Authority: Affiliate Brain
Applies To: Affiliate Brain capital allocation flow, testing sequence, tracking governance, and structured progression logic
Parent: Affiliate Brain Canon
Last Reviewed: 2026-03-14
Purpose
This document defines the operating architecture of Affiliate Brain as a gated, sequential capital allocation system.
Its purpose is to ensure that opportunity evaluation, tracking governance, research interpretation, intent declaration, testing definition, and scaling progression occur in a controlled order.
This architecture exists to prevent skipped layers, uncontrolled capital deployment, and structural drift.
Affiliate Brain operates as a governed system.
Execution remains deferred unless explicitly authorised elsewhere.
Scope
This specification applies to:
• Affiliate Brain evaluation flow
• layer sequencing and gating logic
• tracking governance requirements
• signal architecture requirements
• structural audit interpretation
• testing definition requirements
• progression from intake through controlled scaling
This specification governs architectural order and decision flow.
It does not govern:
• live campaign execution
• creative production details
• budget deployment mechanics
• final financial authority outside approved gates
• platform-specific setup instructions
Those remain governed by Canon, Protocol, Framework, and operational pages connected to Affiliate Brain.
Definition / Rules
Architectural Model
Affiliate Brain operates as a flow-based capital allocation system.
No layer may be skipped.
No flow reversal is permitted.
No parallel capital paths are allowed.
Execution remains deferred.
Flow Overview
Mandatory sequence:
Layer 1 → Layer 2 → Layer 3 → Tracking Governance →
Layer 4 → Layer 5 → Layer 6 →
Structural Signal Audit (4B-4F) →
Intent Gate → Velocity → Testing Definition →
Phase 4 Structured Testing → Stage Progression →
Controlled Scaling
Layer 1 – Offer Intake
Lifecycle State:
Intake
This layer captures the raw opportunity and initiates structured evaluation.
Core intake logic remains unchanged from v1.9.
Layer 2 – Offer Intelligence
Lifecycle State:
Evaluated (Pre-Market Validation)
This layer evaluates the offer itself before testing logic is considered.
Core logic remains unchanged.
Layer 3 – Market Context
Lifecycle State:
Evaluated
This layer reviews the surrounding market environment and contextual pressure.
Core logic remains unchanged.
Infrastructure Governance – Tracking Layer
Purpose
This layer ensures measurement integrity, attribution durability, signal architecture validity, and platform training quality before any capital allocation or test approval.
This layer governs:
• tracking integrity
• conversion event reliability
• attribution visibility
• signal architecture design
• server-side attribution readiness
• first-party data resilience
• consent-aware measurement durability
Tracking Governance must verify that the funnel can produce usable platform learning signals under real-world conditions, including privacy friction, browser restrictions, and affiliate-domain attribution limitations.
This layer does not authorise capital.
It validates whether the infrastructure layer is strong enough to support disciplined testing.
Lifecycle State:
Evaluated (Tracking Verified)
Tracking Governance Requirements
Tracking Governance must confirm the following before Phase 4 testing can be defined:
• core event tracking is functioning
• signal ladder is defined
• primary optimisation signal is declared
• revenue validation path exists
• attribution gap is known
• consent-sensitive behaviour is understood
• server-side upgrade status is logged
• first-party data opportunity is assessed
If these are not known, Tracking Governance remains incomplete.
MWMS Standard Conversion Signal Ladder
Purpose
Advertising algorithms require behavioural signals in order to learn effectively.
Affiliate funnels often produce too few revenue events to train algorithms efficiently.
The Conversion Signal Ladder introduces structured behavioural signals that represent increasing levels of purchase intent.
Example signal density improvement:
1000 visitors
→ 300 engagement signals
→ 120 intent signals
→ 50 high-intent signals
→ 10 purchase signals
This structure improves:
• algorithm learning speed
• signal density
• early-stage campaign optimisation
Signal Ladder Tiers
Tier 1 – Engagement Signal
Purpose:
Detect attention and early interest.
Examples:
• video watch ≥ 30%
• scroll depth ≥ 60%
• page dwell ≥ 20 seconds
Rule:
Engagement signals must never be used as primary optimisation signals for paid acquisition campaigns.
Tier 2 – Intent Signal
Purpose:
Detect active buyer interest.
Examples:
• CTA click
• product reveal click
• VSL buy button interaction
Role:
Primary optimisation signal during early campaign learning.
Tier 3 – High-Intent Signal
Purpose:
Detect users preparing to purchase.
Examples:
• order page visit
• checkout page load
• payment form interaction
Role:
Secondary optimisation signal confirming purchase readiness.
Tier 4 – Revenue Signal
Purpose:
Record confirmed revenue events.
Examples:
• purchase confirmation page
• affiliate network conversion postback
• subscription activation
Role:
Final profitability validation.
Revenue signals confirm business viability but are typically too sparse to serve as primary learning signals.
Signal Priority Rule
Every campaign must define:
• Primary Signal
• Secondary Signal
• Revenue Signal
Example:
Primary Signal → CTA Click
Secondary Signal → Order Page Visit
Revenue Signal → Purchase
Affiliate Attribution Limitation
Affiliate networks frequently process the final purchase on third-party domains.
Example funnel:
Landing Page → VSL → Affiliate Checkout → Purchase
Because the purchase occurs off-domain, ad platforms may lose attribution.
Proxy signals such as Intent or High-Intent signals allow algorithms to optimise even when final purchase attribution is incomplete.
Server-Side Attribution Readiness
Purpose
Determine whether the campaign infrastructure is suitable for current browser privacy conditions and future attribution durability requirements.
Server-side attribution readiness evaluates whether the system can reduce dependence on browser-side pixels alone.
Evaluate:
• whether only browser-side tracking is in use
• whether a server-side GTM path exists
• whether a custom tracking subdomain is possible
• whether a server-side hosting option is identified
• whether event forwarding architecture is documented
Output:
Server-Side Status:
Not Assessed / Not Ready / Planned / Ready / Live
Rule:
Server-side infrastructure is not mandatory for all tests, but its status must be explicitly logged.
First-Party Data Resilience Review
Purpose
Determine whether the funnel can improve attribution quality using first-party user data when legally and operationally appropriate.
Evaluate:
• whether email or user-provided identifiers exist in funnel flow
• whether enhanced conversion pathways are technically possible
• whether first-party data can strengthen platform matching
• whether the current funnel captures any usable first-party data
• whether this opportunity is absent, partial, or strong
Output:
First-Party Data Status:
None / Limited / Usable / Strong
Rule:
First-party data use improves attribution resilience but must never be assumed without implementation review.
Consent and Attribution Durability Review
Purpose
Assess whether privacy restrictions, consent selection, or cookie limitations are likely to weaken attribution quality.
Evaluate:
• whether consent mode is absent, partial, or operational
• whether modeled conversions are expected to influence reporting
• whether attribution loss risk is low, moderate, or high
• whether browser-side signal loss is likely under current setup
• whether tracking interpretation requires caution due to privacy loss
Output:
Attribution Durability Status:
Low Risk / Moderate Risk / High Risk
Consent Status:
Unknown / Basic / Operational
Rule:
Poor consent and attribution durability do not automatically block testing, but they must be visible in the risk interpretation layer.
Signal Architecture Requirement
Before Phase 4 testing begins, the following signal structure must be defined:
Minimum requirements:
• Tier 2 – Intent Signal
• Tier 3 – High-Intent Signal
• Tier 4 – Revenue Signal
Tier 1 engagement signals remain optional.
Signal Integrity Requirements
Signals must be:
• deterministic
• non-duplicated
• consistently named
• verified before campaign launch
Verification occurs inside the Tracking Governance layer.
Prohibited Signal Types
The following signals must never be used as optimisation signals:
• page view
• session start
• ad click duplication
• low-intent micro interactions
These produce misleading algorithm training.
Layer 4 – Research Intelligence
Lifecycle State:
Evaluated (Friction & Awareness Assessed)
This layer analyses research intelligence and friction patterns.
Content remains unchanged, including CFAD references.
Layer 5 – Research Consolidation
Lifecycle State:
Evaluated
This layer consolidates research into a structured interpretation layer.
Core logic remains unchanged.
Layer 6 – Authority and Narrative Intelligence (ANIL)
Lifecycle State:
Evaluated (Narrative Scored)
This layer captures authority and narrative conditions affecting promotability and performance interpretation.
Core logic remains unchanged.
Structural Signal Audit (Canon 4B-4F Integration Layer)
Purpose
This layer translates Canon structural evaluation layers into operational sequencing awareness.
It does not authorise capital.
It informs prioritisation discipline before Intent Gate activation.
This layer includes the following sub-evaluations.
1. Behavioural Viability Assessment (Canon 4B)
Evaluate:
• trigger clarity
• variable reward structure
• habit formation potential
• re-engagement loop strength
Behavioural interface evaluation:
• value proposition clarity
• visual hierarchy strength
• attention retention design
• trust signal presence
• action timing alignment
Purpose:
Determine whether the offer and funnel structure support behavioural durability and sustained engagement rather than short-term curiosity clicks.
Output:
Durability Confidence Tag
2. Trust Escalation Audit (Canon 4C)
Evaluate:
• entry trust vs required trust
• trust gap
• credibility signal sufficiency
• claim-proof alignment
Output:
Trust Mismatch Flag (Yes/No)
3. Opportunity Signal Prioritisation (Canon 4D)
Evaluate:
• estimated benefit
• estimated structural opposition
• monetisation alignment
• funnel position
• authority dependency
Output:
Structural Signal Score (Advisory)
Note:
This score does not replace Velocity.
It informs sequencing and risk interpretation only.
4. Funnel Coherence and Authority Stack Audit (Canon 4E)
Evaluate:
• top funnel presence
• mid funnel reinforcement
• bottom funnel alignment
• authority stacking integrity
Output:
Authority Fragility Flag (Low / Moderate / High)
5. Promotability and Authority Acquisition Feasibility (Canon 4F)
Evaluate:
• organic authority pathways
• paid dependency
• external authority requirement
• linkability potential
Output:
Promotability Constraint Status
Lifecycle State:
Evaluated (Structural Signal Assessed)
Intent Declaration Gate
Lifecycle State:
Evaluated (Intent Defined)
This layer remains unchanged.
Layer 7 – Velocity Decision Engine
Velocity is a binary capital verdict.
Velocity remains the sole capital gatekeeper.
Structural Signal Audit does not override Velocity.
Velocity is blocked if:
• Research Integrity FAIL
• Tracking Integrity FAIL
• ANIL not logged
• Structural Signal Audit not logged
• Intent Gate incomplete
Lifecycle State:
Decision Complete
Layer 8 – Testing Definition
Purpose
Convert approved capital intent into a mechanical testing plan.
Testing Definition must declare:
• traffic source
• offer destination
• landing asset
• primary optimisation signal
• secondary verification signal
• revenue validation signal
• attribution interpretation caution, if applicable
No test is valid without a declared primary optimisation signal.
Lifecycle State:
Approved for Test
Phase 4 – Structured Testing and Stage Progression
This phase remains unchanged.
Stage 5 – Controlled Scaling (Mechanical Protocol)
This stage remains unchanged.
Layer 9 – Execution (Deferred)
This layer remains unchanged.
Execution remains deferred unless separately authorised.
Canon Gate Enforcement (C1-C11)
Structural Signal Audit must be logged before Intent Gate activation.
Updated gate list:
C1 – Intake complete
C2 – Compliance assessed
C3 – Market reviewed
C4 – Tracking Integrity Verified
C5 – Research compiled
C6 – Research Integrity OK
C7 – Narrative Intelligence Logged
C8 – Structural Signal Audit Logged
C9 – Intent Gate complete
C10 – Velocity ≥ 80
C11 – Testing defined
Failure blocks progression.
Drift Protection
The system must block:
• Velocity activation without Structural Signal Audit logged
• Structural Signal layer being used as capital override
• authority scoring being mistaken for revenue validation
• signal density being mistaken for profitability
• server-side readiness being mistaken for offer viability
Architectural Intent
Affiliate Brain is a governed capital allocation engine.
It enforces:
• measurement integrity
• research triangulation
• narrative awareness
• behavioural durability review
• trust alignment verification
• structural signal prioritisation
• intent clarity
• capital discipline
• statistical validation
• mechanical scaling discipline
• outcome-quality validation
• audit traceability
• attribution durability awareness
• signal architecture discipline
It does not execute.
It does not persuade.
It allocates capital under discipline.
Change Log
Version: v2.4
Date: 2026-03-14
Author: MWMS HeadOffice / Affiliate Brain
Change: Rebuilt page to align with MWMS document standards. Added Document Type header, replaced Linked Canon and Last Updated fields with standardised metadata, introduced Purpose / Scope / Definition / Rules structure, normalised headings, and preserved the existing architectural model and layer logic.
Version: v2.3
Date: 2026-03-07
Author: Affiliate Brain
Change: Expanded Tracking Governance layer. Integrated server-side attribution readiness review, first-party data resilience review, and consent and attribution durability review. Clarified Testing Definition requirement for primary, secondary, and revenue signals.
Version: v2.2
Date: 2026-03-07
Author: Affiliate Brain
Change: Integrated MWMS Standard Conversion Signal Ladder inside the Tracking Governance layer. Added signal architecture requirements for algorithm training and attribution resilience.
Version: v2.1
Date: 2026-03-05
Author: Affiliate Brain
Change: Integrated behavioural UI evaluation signals into Canon 4B Behavioural Viability layer. Added value proposition clarity, hierarchy strength, attention retention, trust signal presence, and action timing alignment as behavioural durability indicators.
Version: v2.0
Date: 2026-03-02
Author: Affiliate Brain
Change: Aligned to Canon v2.6. Inserted Structural Signal Audit layer (4B-4F integration). Added Structural Audit gate before Intent activation. No capital rule modification. Velocity unchanged.
Version: v1.9
Date: 2026-02-26
Author: Affiliate Brain
Change: Previous entries preserved.
END – AFFILIATE BRAIN ARCHITECTURE v2.4