Document Type: Specification
Status: Active
Version: v1.1
Authority: Affiliate Brain (Audience Extension Layer)
Applies To: Audience state classification, engagement progression, event-based audience upgrades and downgrades, and anti-inflation audience governance
Parent: Audience Engine
Last Reviewed: 2026-03-14
Purpose
This schema defines measurable engagement states for Audience Engine.
It converts abstract audience growth into structured, loggable, and enforceable progression.
All states must be:
• observable
• trackable
• event-based
• non-emotional
• governed by trigger logic
No subjective classification is permitted.
Scope
This specification applies to:
• audience-state definitions
• upgrade and downgrade conditions
• event-based audience classification
• engagement progression logic
• audience measurement integrity
• anti-inflation governance for audience stages
This document governs how audience states are defined and interpreted.
It does not govern:
• paid traffic Velocity scoring
• capital allocation
• live campaign execution
• manual audience assignment
• automation deployment by itself
• ANIL scoring integration unless separately activated
Those remain governed by Affiliate Brain, HeadOffice, Finance Brain, and related audience infrastructure documents.
Definition / Rules
State Definitions
Stage 0 – Anonymous Viewer
Definition:
A user has consumed content without identifiable subscription.
Trigger:
• page view or video play
• no email captured
• no account login
Logged event examples:
• content_view
Upgrade condition:
• at least 1 measurable engagement action
Downgrade:
• not applicable, entry state
Stage 1 – Engaged Viewer
Definition:
A user has demonstrated meaningful content engagement.
Trigger, any of the following:
• at least 75 percent video completion
• at least 3 page interactions within a session
• at least 2 sessions within 7 days
Logged event examples:
• video_completion_75
• multi_page_session
• repeat_visit_7d
Upgrade condition:
• email opt-in or platform follow
Downgrade condition:
• no engagement for 60 days
Stage 2 – Subscriber
Definition:
A user has granted permission access.
Trigger:
• email opt-in
or
• verified platform follow, if the hub is external
Logged event examples:
• email_subscribe
• platform_follow
Upgrade condition:
• at least 2 content sessions within 30 days
Downgrade condition:
• unsubscribe or 90-day inactivity
Stage 3 – Repeat Consumer
Definition:
A user consistently consumes content.
Trigger:
• at least 2 sessions within 30 days
and
• at least 1 long-form completion event
Logged event examples:
• repeat_session_30d
• long_form_completion
Upgrade condition:
• share event or referral activity
Downgrade condition:
• no session activity for 90 days
Stage 4 – Advocate
Definition:
A user actively amplifies content.
Trigger, any of the following:
• share event logged
• referral link click
• tag or mention action
• comment participation at least 2 instances
Logged event examples:
• content_share
• referral_click
• mention_tag
• comment_repeat
Upgrade condition:
• repeat advocacy within 60 days
Downgrade condition:
• no engagement for 120 days
Stage 5 – Superfan
Definition:
A user demonstrates sustained high-frequency engagement and voluntary advocacy.
Trigger:
• at least 3 sessions per month
and
• at least 2 advocacy events within 90 days
and
• at least 1 long-form completion per month
Logged event examples:
• high_frequency_session
• advocacy_repeat
• long_form_repeat
Downgrade condition:
• failure to maintain engagement thresholds
Engagement Principles
- Time spent is more valuable than impressions
- Completion is more valuable than click
- Retention is more valuable than acquisition
- Advocacy is more valuable than passive consumption
- Only measurable events qualify
Logging Requirements
All engagement states must be derived from:
• server-side logging where possible
• verified analytics triggers
• Supabase-compatible event schema
No state may be manually assigned.
Escalation Rules
Audience state progression does not:
• override Affiliate Brain Velocity
• influence capital allocation automatically
• modify testing governance
Future versions may integrate engagement density into ANIL scoring.
Drift Protection
The system must block:
• state inflation
• manual override without event verification
• vanity metric substitution
• engagement without measurable trigger
SIT enforcement is required before automation.
Activation Status
Current status:
• schema defined
• automation layer inactive
• Supabase table integration pending
Architectural Intent
Audience State Progression Schema exists to turn audience development into a governed measurement system rather than a vague growth concept.
Its role is to ensure that audience stages inside MWMS are derived from observable evidence, recorded consistently, and protected from vanity inflation or subjective interpretation.
Change Log
Version: v1.1
Date: 2026-03-14
Author: MWMS HeadOffice / Affiliate Brain
Change: Rebuilt page to align with MWMS document standards. Removed duplicated title text, added standardised document header, replaced legacy metadata with compliant structure, introduced Purpose / Scope / Definition / Rules format, normalised state and trigger formatting, and preserved the original event-based state progression, upgrade and downgrade logic, engagement principles, and inactive automation status.
Version: v1.0
Date: 2026-02-25
Author: Affiliate Brain
Change: Initial creation of Audience State Progression Schema defining measurable audience states, event-based trigger logic, upgrade and downgrade conditions, engagement principles, logging requirements, escalation boundaries, and drift-protection rules.
END – AUDIENCE STATE PROGRESSION SCHEMA v1.1