Document Type: Architecture
Status: Architecture
Version: v1.1
Authority: HeadOffice
Applies To: Affiliate opportunity evaluation, rejection logging, pause decisions, retirement intelligence, and negative pattern preservation
Parent: Affiliate Brain Architecture
Last Reviewed: 2026-03-15
Purpose
This page defines the structure used to record affiliate opportunities that have been rejected, paused, retired, or structurally downgraded inside the MWMS ecosystem.
The purpose of this system is to preserve negative intelligence.
Rejected and failed opportunities contain valuable information.
This page ensures MWMS does not lose that information through memory drift, repeated testing mistakes, or undocumented rejection decisions.
Scope
This architecture applies to:
• affiliate opportunities rejected before testing
• offers paused, downgraded, or retired after review or testing
• storage of structural rejection reasoning
• preservation of negative offer intelligence inside Affiliate Brain
• future filtering and reconsideration logic for previously rejected opportunities
This document defines the negative-intelligence architecture used to preserve rejected and failed offer knowledge.
It does not govern:
• live offer approval by itself
• direct capital allocation by itself
• campaign execution by itself
• statistical validation by itself
• final governance override decisions by themselves
• real-time offer scoring by itself
Those remain governed by Affiliate Brain governance systems, Finance Brain, Velocity Decision Engine, and related operational documents.
Definition / Rules
Core Principle
A rejected offer is not wasted work.
A rejected offer is intelligence.
Every declined, paused, or retired opportunity must be recorded together with:
• the reason for rejection
• the structural weakness detected
• the decision authority involved
• the lifecycle outcome
• any future reconsideration conditions
This creates a permanent intelligence layer that improves future capital allocation decisions.
Use Cases
This page is used when an opportunity is:
• rejected before testing
• paused after review
• retired after testing
• downgraded due to structural weakness
• blocked by compliance, trust, or capital constraints
Rejected Offer Record Structure
Each rejected offer record should contain the following fields:
• Offer Name
• Affiliate Network / Platform
• Offer ID
• Vendor Name
• Date Recorded
• Lifecycle Stage at Rejection
• Reason Category
• Decision Authority
• Velocity Verdict
• Hard Fail Triggered
• Primary Structural Weakness
• Detailed Rejection Notes
• Future Reconsideration Conditions
• Related Offer Intelligence Page
Reason Categories
Each rejected or failed offer should be tagged using one or more of the following categories:
• Compliance Failure
• Trust Failure
• Weak Mechanism
• Low Demand
• Poor Funnel Structure
• Creative Fragility
• Narrative Saturation
• Capital Intensity Too High
• Insufficient Differentiation
• Vendor Risk
• Poor Testing Results
• Lifecycle Exhaustion
Lifecycle Stage at Rejection
The system must record the stage at which the opportunity was rejected or retired.
Possible stages include:
• Intake
• Evaluated
• Approved for Test
• Testing
• Paused
• Scaled
• Retired
Decision Authority
The record must identify who made the rejection or retirement decision.
Possible authorities include:
• Affiliate Brain
• HeadOffice
• Finance Brain
• Risk Brain
• Human Executive Authority
Velocity Integration
Where applicable, the record must include the Velocity Decision Engine outcome.
Examples:
Velocity Verdict: NO
Hard Fail Triggered: YES
Reason: Vendor identity missing
or
Velocity Verdict: NO
Hard Fail Triggered: NO
Reason: Score below threshold
Future Reconsideration Conditions
A rejected offer may be reconsidered only if specific conditions change.
Examples include:
• vendor improves trust signals
• market demand increases
• new creative differentiation becomes available
• compliance risk is reduced
• backend economics improve
If no realistic reconsideration path exists, the record should state:
No reconsideration recommended.
Intelligence Value
The Offer Graveyard improves MWMS by preserving:
• negative pattern recognition
• category-level failure trends
• repeated vendor weaknesses
• structural rejection history
• campaign retirement rationale
This intelligence reduces repeated mistakes and improves future opportunity filtering.
Outcome
The Offer Graveyard – Rejected Offers Intelligence system ensures that MWMS learns not only from winning offers, but also from rejected and failed ones.
This strengthens:
• capital discipline
• structural memory
• research quality
• long-term offer selection accuracy
Rejected opportunities become part of MWMS intelligence rather than forgotten dead ends.
Final Rule
A rejected offer must never disappear into memory.
If the rejection is not preserved, the intelligence value of the failure is lost.
Drift Protection
The system must prevent:
• rejected offers being discarded without structured record
• repeated evaluation of previously failed offers without archive review
• negative intelligence being treated as less valuable than positive intelligence
• pause and retirement decisions occurring without documented rationale
• reconsideration happening without clear change conditions
• vendor or category failure patterns being lost across time
Negative intelligence must remain visible, searchable, and reusable.
Architectural Intent
Offer Graveyard – Rejected Offers Intelligence exists to convert failed, paused, and declined affiliate opportunities into durable system knowledge.
Its role is to preserve structural rejection memory so MWMS can improve filtering, protect capital, and compound learning from what should not be pursued, not only from what wins.
Change Log
Version: v1.1
Date: 2026-03-15
Author: HeadOffice
Change: Rebuilt page to align with the locked MWMS document standard for this cleanup pass. Preserved the original purpose, core principle, use cases, rejected-offer record structure, reason categories, lifecycle-stage logic, decision-authority logic, Velocity integration, future reconsideration conditions, intelligence value, and intended outcome. Added Document Type, Scope, Definition / Rules structure, Final Rule, Drift Protection, and Architectural Intent sections. Normalised title to standard MWMS naming format.
Version: v1.0
Date: 2026-03-06
Author: HeadOffice
Change: Initial creation of Offer Graveyard / Rejected Offers Intelligence defining the structure for recording rejected, paused, retired, and downgraded affiliate opportunities inside MWMS.
END – OFFER GRAVEYARD – REJECTED OFFERS INTELLIGENCE v1.1