Document Type: Flow Map
Status: Active
Version: v1.1
Authority: Affiliate Brain (Audience Flow Layer)
Applies To: Audience-state progression logic, event-based movement rules, and long-term authority development inside the Affiliate Brain audience system
Parent: Hub Definition
Last Reviewed: 2026-03-15
Purpose
Content-to-Audience Flow Map defines how published content moves individuals through measurable audience states.
It connects:
Hub
→ Engagement Events
→ Audience State Schema
→ Long-Term Authority
No emotional assumptions are permitted.
All movement must be event-based.
Scope
This flow map applies to:
• Affiliate Brain audience-state progression
• event-based movement between audience stages
• traffic-entry tracking logic
• retention and downgrade rules
• long-term authority development through measurable audience behaviour
This document governs how audience movement should be interpreted structurally inside the audience system.
It does not govern:
• capital allocation
• Velocity decisions directly
• compliance rulings
• manual override behaviour
• execution-layer automation by itself
• paid campaign governance by itself
Those remain governed by Affiliate Brain Canon, related audience systems, SIT, and other governing protocols.
Definition / Rules
Core Principle
Audience movement must be inferred from logged events, not assumptions.
No emotional interpretation, guesswork, or manual reclassification is permitted.
Flow Overview
The audience-state progression model is:
Anonymous Visitor
→ Engaged Viewer
→ Subscriber
→ Repeat Consumer
→ Advocate
→ Superfan
Progression is governed by logged events only.
Entry Points
Traffic may enter the system through:
• organic search
• direct navigation
• spoke platforms
• referral links
• newsletter clicks
Each entry must log:
• utm_source
• utm_medium
• utm_campaign
Free-text campaign names are prohibited.
Stage 0 → Stage 1
Trigger conditions:
• ≥75% scroll depth
• ≥75% video completion
• ≥2 internal link clicks
Logged events:
• scroll_depth_75
• video_completion_75
• multi_internal_click
Stage 1 → Stage 2
Trigger conditions:
• email opt-in
• download gated asset
• newsletter signup
Logged event:
• email_subscribe
Stage 2 → Stage 3
Trigger conditions:
• ≥2 sessions within 30 days
• ≥1 long-form article completion
Logged events:
• repeat_session_30d
• long_form_completion
Stage 3 → Stage 4
Trigger conditions:
• content share
• referral click
• comment participation
• mention/tag event
Logged events:
• content_share
• referral_click
• comment_repeat
• mention_tag
Stage 4 → Stage 5
Trigger conditions:
• ≥3 sessions per month
• ≥2 advocacy events within 90 days
• ≥1 long-form completion per month
Logged events:
• high_frequency_session
• advocacy_repeat
• long_form_repeat
Retention Protocol
Inactivity thresholds:
• 60 days → downgrade engaged
• 90 days → downgrade subscriber
• 120 days → downgrade advocate
No manual override is permitted.
Strategic Objective
This flow is designed to:
• increase engagement density
• increase return traffic
• increase authority perception
• lower acquisition dependency
• strengthen ANIL Authority Score over time
Boundary Conditions
Audience progression does not:
• modify capital allocation
• influence Velocity directly
• override Compliance rules
Affiliate Brain remains separate from the execution layer.
Automation Status
Flow defined.
Event logging layer pending Supabase integration.
Final Rule
Audience progression must remain event-based, measurable, and structurally governed.
If a stage change cannot be justified by logged behaviour, it should not occur.
Drift Protection
The system must prevent:
• audience-state movement based on intuition rather than event evidence
• manual promotion of users between stages
• free-text attribution data weakening structural analysis
• retention downgrades being bypassed without governance
• audience authority assumptions being made without behavioural proof
• flow-state logic drifting away from measurable event definitions
Audience-state progression must remain traceable, rule-based, and auditable.
Architectural Intent
Content-to-Audience Flow Map exists to define how audience development should be measured across the Affiliate Brain audience system.
Its role is to convert content interaction into structured behavioural progression so long-term authority can be built through observable audience movement rather than vague engagement assumptions.
Change Log
Version: v1.1
Date: 2026-03-15
Author: MWMS HeadOffice / Affiliate Brain
Change: Rebuilt page to align with the locked MWMS document standard for this cleanup pass. Added standardised document header, converted Last Updated to Last Reviewed, corrected title presentation, replaced Linked Canon formatting with Applies To structure, introduced Purpose / Scope / Definition / Rules format, and preserved the original audience-stage flow, trigger logic, event requirements, retention rules, strategic objective, and boundary conditions.
Version: v1.0
Date: 2026-02-25
Author: Affiliate Brain
Change: Initial creation of Content-to-Audience Flow Map defining stage progression, event triggers, retention downgrades, and audience authority development logic.
END – CONTENT-TO-AUDIENCE FLOW MAP v1.1