SalesBlaster Darwinian Loop Theory

0. Purpose, Scope, and What This Document Is Not

Purpose

This document establishes the WHAT and WHY of the SalesBlaster Darwinian Loop - the foundational marketing theory the entire SalesBlaster organization, platform, and AI agent system is built on top of. It is the seed that every downstream marketing decision, every campaign, every offer, every test, and every AI agent prompt should trace back to.

If an AI agent, a SalesBlaster operator, or a client is about to make a campaign decision and they do not understand this document, they will make worse decisions. If they do understand it, they will make decisions that compound - small edges turn into structural advantage over time.

Scope

• The Darwinian Loop as the universal operating model for any SalesBlaster campaign across any channel.
• The Stimulus Genotype framework as the canonical way to decompose any marketing asset into testable components.
• The Six Sub-Systems of client acquisition and how they map to SalesBlaster's pipeline (§7) and the seven-phase Campaign Run Protocol (§9).
• Channel-specific applications: outbound, paid, organic.
• Cross-framework reinforcement from Kennedy, Hormozi, Brunson, and Schwartz.
• Anti-patterns and the failure modes that destroy 95% of campaigns.

What This Document Is Not

• It is not an implementation spec. The HOW (workflows, schemas, tool calls, prompts, agent definitions) lives in downstream implementation documents.
• It is not a copy library. Stimuli (subject lines, scripts, ad creative) are produced under this theory, not enumerated by it.
• It is not a list of tactics. Tactics decay. Theory does not.

Reading Order

Sections 1–4 are the core. If you read nothing else, read those. Sections 5–9 apply the core to specific contexts. Sections 10–13 are reference.

1. Executive Summary - The Loop in One Page

A SalesBlaster campaign is a system that converts strangers in a niche into closed deals through a chain of stimuli. Every stimulus in that chain is a genotype - a stack of 2–4 needle-mover variables that together either produce fitness (KPI conversion) or don't.

We do not "guess what works." We run the Scientific Method as a closed loop:

Hypothesize → Test → Observe → Iterate. One needle-mover at a time. Hold everything else constant. Repeat.

The campaign that wins is not the one with the cleverest copy. It is the one whose operator iterates the most disciplined loops in the shortest cycle time, with the highest signal-to-noise data, on the variable that actually moves the needle.

This is the Darwinian Loop. Variation → selection → inheritance → scale. Applied to marketing assets instead of organisms. SalesBlaster's entire platform exists to compress the cycle time of this loop and to industrialize the variable-isolation that makes the loop produce real signal.

The four operating laws that follow from this:

1. Fitness is binary at the KPI line, but the path to it is gradient. A campaign at 0.8% reply when KPI is 1% is one needle-mover away. A campaign at 0.05% is broken at the variable layer and needs full reset.
2. The Polaris metric is sacred. Sub-metrics are not. Optimize the downstream conversion. Never optimize a sub-metric in isolation; you will break the system non-linearly.
3. Stimuli decay (Stimulus Hypoesthesia). Theory does not. Every winning stimulus has a half-life. Plan for V2 before V1 has died.
4. Ceteris paribus or the data is fake. Iterating two variables at once means the test produced no information. You wasted the cycle.

Everything else in this document is elaboration of these four laws.

2. First Principles - Morgan's Acquisition Systems Theory

Charlie Morgan's framework is the philosophical substrate. We adopt it wholesale because it is the only model in the marketing literature that treats client acquisition as a system science rather than a tactic catalog. This section recaps it in marketing language, with SalesBlaster translations.

2.1 The Macro Equation

Human (in Niche) + Stimuli Chain (deployed via SOPs/automation) = Clients ($$$ + Metrics) All operating inside The Market (the environment).

This is the entire game. Inputs (humans), processes (stimuli chain), outputs (revenue), feedback (metrics), environment (market dynamics). Every campaign - outbound cold email, Meta ads, LinkedIn organic, podcast tour, anything - collapses to this equation.

2.2 What a Stimulus Is

A stimulus is anything we expose a human to in order to provoke an action that moves them one step closer to becoming a client. A stimulus is not just copy. It is:

• A subject line (provokes the action: open).
• A first-line hook (provokes the action: keep reading).
• A loom thumbnail (provokes the action: click play).
• A case study (provokes the action: believe it works).
• A sales discovery question (provokes the action: surface a real pain).
• A Calendly link with the right framing (provokes the action: book).
• A follow-up sequence (provokes the action: re-engage).

Each stimulus targets one specific action. The full sequence of actions a human takes from "stranger" to "wired payment" is the Micro-Action-Chain. Inverting that chain gives us the Stimulus Chain we have to build.

2.3 The Six Sub-Systems

The macro acquisition system decomposes into six sub-systems, each converting a human from one state to the next:

Critical implication: A campaign is only as strong as its weakest sub-system. A 50% open rate with a 0% reply rate is a sub-system 2 problem, not a sub-system 1 problem. Optimizing sub-system 1 here is malpractice.

2.4 The Client Acquisition Shell (Nesting Structure)

Macro System
  ↳ contains Sub-Systems (6 of them)
    ↳ contain Stimuli (many per sub-system)
      ↳ contain Variables (2–4 needle-movers per stimulus)

This nesting is the mental model. Everything we test, ship, or iterate happens at the variable layer. Everything we measure happens at the sub-system or macro layer. Confusing the layers is the #1 cause of analysis paralysis.

2.5 Throughput, Yield, Bottlenecks, Latency

• Throughput: humans flowing through the system per unit time.
• Yield: clients out the bottom.
• Bottleneck: the sub-system with the worst conversion rate. Always exists. Always the only thing worth fixing.
• Latency: the delay between input and observable output. A cold email sent today is a client signed in 2–4 weeks. A LinkedIn post today is an inbound lead in 30–90 days. Most operators kill working systems by panicking inside the latency window.

2.6 The Polaris Star

The single metric that defines whether the macro system is healthy. Everything downstream of Polaris is sub-metric. SalesBlaster's default Polaris is Closed Deal Rate per 1,000 inputs or, as a leading proxy, Booked-and-Showed Qualified Appointment Rate. Cost per opportunity (CPO) is the financial sibling.

If Polaris is in KPI, do not touch the system. Build a parallel petri dish to test improvements. Touching a winning system because a sub-metric "could be better" is how operators turn 5% closed-deal-rate systems into 1% systems.

3. The Stimulus Genotype - DNA of Every Campaign

This is the single most important conceptual unit in this document. Internalize it.

3.1 The Genotype Equation

Stimulus = Variable₁ + Variable₂ + Variable₃ (+ Variable₄)

Every stimulus is a stack of 2–4 needle-mover variables. The variables are the testable, mutable units. The stimulus is what gets shipped.

Examples:

3.2 Why "2–4 Variables" and Not 10

Most stimuli have 10+ surface-level components. Loom thumbnail color, font choice, send time, signature, the word "agency" vs "studio" - all variables, technically. But only 2–4 actually move the needle. The rest are noise inside the variance band.

Identifying the 2–4 needle-movers for a given stimulus in a given niche at a given market sophistication level is the highest-leverage skill in marketing. It is what experienced operators do unconsciously and what AI agents must be trained to do explicitly.

Heuristic for finding needle-movers: If you 10x'd this variable in either direction, would the metric move materially? If yes → needle-mover. If no → noise variable, hold constant.

3.3 Traits and Adaptability

Variables produce traits - adjectives that describe the personality of the stimulus. Example traits: punchy, soft, transparent, urgent, mysterious, formal, weird, contrarian, plainspoken, hypey.

A stimulus has fitness when its traits are adapted to the niche's current psychology at the current market sophistication level. The same trait stack ("punchy + transparent + slightly self-deprecating") may print money in an SMB plumber niche and bomb in a private-equity LP niche.

Key implications:

• Two opposite traits can both work in the same niche (humor and seriousness, formal and informal). Trait mix is non-binary.
• Trait fitness decays over time as the niche habituates (Stimulus Hypoesthesia, see §11).
• The trait of "everyone else's copy in this niche right now" has near-zero fitness by default. Contrarian trait stacks beat consensus trait stacks at every market sophistication level above 1.

3.4 Genotype Manipulation: Splicing and Cross-Pollination

Once a winning genotype is found in one stimulus, you can:

• Splice - take a winning trait from one stimulus and insert it into another stimulus's genotype. Example: a transparency frame that prints in cold email gets spliced into the sales discovery script.
• Cross-pollinate - combine winning genotypes from two different campaigns/channels into a new variant. Example: a Meta ad's hook style + a LinkedIn post's pacing + a cold email's CTA style = new outbound video script.

These are not gimmicks. They are how every long-cycle marketing organization compounds wins. SalesBlaster is built to make this systematic, not ad-hoc.

4. The Darwinian Loop - The Scientific Method as Marketing's Engine

This is the loop. This is what "Darwinian" actually means at SalesBlaster. Not "evolutionary vibes." Literal application of the scientific method to stimulus genotypes, with the rigor of a research biologist.

4.1 The Four Steps

   ┌───────────────────────────────────┐
   │                                   │
   │     1. FORMULATE HYPOTHESIS       │
   │     (define genotype, KPI,        │
   │      sample, latency, constants)  │
   │                                   │
   └────────────┬──────────────────────┘
                │
                ▼
   ┌───────────────────────────────────┐
   │     2. TEST HYPOTHESIS            │
   │     (deploy, then DO NOTHING,     │
   │      log data daily on yesterday) │
   └────────────┬──────────────────────┘
                │
                ▼
   ┌───────────────────────────────────┐
   │     3. OBSERVE RESULTS            │
   │     (verify data, gate against    │
   │      6-rule completion checklist) │
   └────────────┬──────────────────────┘
                │
                ▼
   ┌───────────────────────────────────┐
   │     4. ITERATE HYPOTHESIS         │
   │     (pick ONE needle-mover,       │
   │      pick mod level, modify,      │
   │      everything else becomes      │
   │      a constant)                  │
   └────────────┬──────────────────────┘
                │
                └────► back to step 1

4.2 Step 1 - Formulate Hypothesis (Pre-Flight Checklist)

Before any stimulus is deployed, the operator (or AI agent) must lock the following:

1. Genotype variables defined - the 2–4 needle-movers explicitly named.
2. Polaris and primary metric defined - exact KPI threshold (e.g., "Polaris = ABR; KPI = 3.5%").
3. Sample size defined - minimum sample to escape regression-to-the-mean noise. Defaults: 300 cold emails fully followed up, 30 loom views, 30 sales calls, 1,000 ad impressions (varies by channel).
4. Latency window defined - how long the test must run before observation is valid. Cold email = 7–14 days minimum. Paid ads = 3–7 days post-spend-stabilization. Organic = 30–90 days.
5. Test integrity guaranteed - deliverability checked, tracking pixels firing, automation deployed, all upstream stages functional. ("Make the test airtight.")
6. V1 of each variable created - actual copy/creative/script written.
7. Constants explicitly listed - every other variable in the system that will not change during this test.

If any of these seven are missing, the test will produce noise, not information. A test that produces noise is worse than no test, because it costs cycle time and produces false confidence.

4.3 Step 2 - Test (And This Is Where 95% of Operators Fail)

Three sub-rules:

1. Run the test. Deploy.
2. Do nothing. Resist every impulse to "fix," "tweak," "improve." Especially when early data looks bad. Especially when early data looks good. The whole point of a controlled test is non-intervention during the run.
3. Log data daily, on yesterday's numbers. Today is incomplete. Yesterday is closed.

The "do nothing" rule is psychologically the hardest part of the loop. It is also the most diagnostic of operator maturity. AI agents must be designed to enforce it at the workflow layer - i.e., the system should not even allow mid-test variable changes without an explicit override and a logged reason.

4.4 Step 3 - Observe (The Six-Rule Gate)

A test is only valid for observation when all six of these are true:

1. Sample size hit and outcomes attributed to source.
2. Latency window elapsed.
3. Test was airtight (no infra failures).
4. All constants stayed constant.
5. Nothing was changed during the run.
6. Data logged with 100% accuracy.

If any rule fails, discard the test and rerun. Forcing a decision off invalid data is the second-most expensive error in marketing (the first is iterating multiple variables - see §4.5).

Then determine success:

• Polaris in KPI? → Don't touch. Scale volume. Move iteration to a parallel petri dish.
• Polaris below KPI but primary in KPI? → Wait for latency on downstream variables. Do not iterate the tested variable yet.
• Polaris and primary both below KPI? → Iterate.

4.5 Step 4 - Iterate (Ceteris Paribus, or Don't Bother)

This is where the entire framework lives or dies.

1. Re-list the genotype variables.
2. Pick the single needle-mover - the one variable that, if changed, you believe would most move Polaris. Use experience, niche knowledge, and Schwartz sophistication analysis (§10). When in doubt, pick the variable furthest upstream in the stimulus chain.
3. Recognize the new constants - every other variable becomes locked.
4. Pick modification level:
   • Slight - V2 has high affinity to V1. Use when you were close to KPI (e.g., 2.7% vs 3.5% target).
   • Moderate - V2 has some affinity. Use when meaningfully off (e.g., 1.3% vs 3.5%).
   • Complete - V2 has no affinity. Use when dead in the water (e.g., 0.3% vs 3.5%).
5. Modify the needle-mover and only the needle-mover.
6. Run the loop again.

The Ceteris Paribus Law: If you change two variables at once, the test produced zero information. You cannot attribute the result to either change. The cycle was wasted. This is the single largest cause of campaign drift in the entire industry.

4.6 Cycle Time Is The Whole Game

Two operators each running the Darwinian Loop will, given enough cycles, converge on similar quality of stimuli. The one running 10 loops a month will obliterate the one running 1.

SalesBlaster's entire technical architecture is fundamentally a cycle-time-compression machine. Every engineering decision should be evaluated against: does this make the loop faster, or the data cleaner, or the iteration smarter? If not, it is over-engineering.

4.7 Initial Conditions Matter (The Butterfly Effect)

A V1 that is closer to fitness from launch reaches KPI in fewer cycles. Niche knowledge, Schwartz analysis, and competitor teardowns dramatically improve V1 quality. Skipping niche research to "just start sending" is technically a valid strategy - but you will burn 5–20 extra cycles getting to fitness compared to an operator who spent two days inside the niche first.

This is why SalesBlaster's research and segmentation step is non-negotiable, not a "nice to have."

5. The Six Sub-Systems Applied - What Iteration Looks Like at Each Stage

Each sub-system has its own genotype variables, its own KPIs, its own latency, and its own failure modes. Optimizing one without understanding its dependencies on others is malpractice.

Sub-System 1 - Attention (Latent → Attention)

• Polaris: Open rate / impression CTR / thumbnail CTR.
• Genotype variables: Hook, framing angle, named-entity reference, format break.
• Failure modes: Banner blindness, generic subject lines, "agency" language in cold email, cold-call style ad copy.
• Common needle-mover: Specificity. Niche-named, situation-named hooks beat universal ones by 3–10x.

Sub-System 2 - Interest (Attention → Interest)

• Polaris: Reply rate / video VTR / scroll depth.
• Genotype variables: Body copy structure, mechanism reveal, social proof placement, brevity.
• Failure modes: Buried lede, over-promising relative to hook, mechanism shown too late.
• Common needle-mover: Mechanism. How the result is achieved beats that the result is achievable, at sophistication levels 3+.

Sub-System 3 - Appointment (Interest → Booked)

• Polaris: Appointment booking rate (ABR) from interested.
• Genotype variables: CTA framing, calendar UX, qualifier questions, perceived commitment level.
• Failure modes: Calendar friction, over-qualification, soft CTA when prospect was ready for hard CTA.
• Common needle-mover: Commitment level of the CTA. "Reply YES" vs. "Book a 30-minute strategy session" vs. "Book a 15-minute fit call" all produce wildly different ABRs in the same prospect pool.

Sub-System 4 - Show (Booked → Showed)

• Polaris: Show-up rate (SUR).
• Genotype variables: Reminder cadence, pre-call content, agenda framing, channel diversification (email + SMS + WhatsApp).
• Failure modes: Single-channel reminders, no pre-call value, "looking forward to meeting" generic energy.
• Common needle-mover: Pre-call value drop. A useful asset delivered before the call lifts SUR by 15–40 points.

Sub-System 5 - Primed Prospect (Showed → Engaged)

• Polaris: Discovery-to-pitch conversion (qualified rate).
• Genotype variables: Agenda statement, framing of authority, discovery question sequence, listening-to-talking ratio.
• Failure modes: Pitching before priming, weak frame, asking surface-level questions, monologuing.
• Common needle-mover: Question sequence. The order of discovery questions changes how prospects self-prime by 2–3x.

Sub-System 6 - Closed Deal (Primed → Wired)

• Polaris: Sales conversion rate (SCR) and average contract value (ACV).
• Genotype variables: Pitch structure, offer architecture, price framing, objection rebuttals, payment friction.
• Failure modes: Bad offer (most common), price stated before value, objection avoidance, payment link friction.
• Common needle-mover: The offer itself. Per Hormozi: a "Grand Slam Offer" makes the rest of the system 3–10x more forgiving. We will treat offer as the highest-leverage sub-system 6 variable in nearly all cases.

6. Channel-Specific Application of the Loop

The Darwinian Loop is universal. Its parameters are channel-specific. This section locks the defaults.

6.1 Outbound (Cold Email, Cold DM, Cold Call, AI Voice)

Cycle time profile: Medium. 7–14 day test windows. Highest signal-to-noise of any channel because attribution is clean.

Default sample sizes for fitness verification:

• Cold email: 300 sends per variant, full 5–7 step follow-up sequence completed.
• Cold LinkedIn DM: 100 connections accepted + initial sent per variant.
• Cold call: 100 dials per variant.
• AI voice agent (e.g., Vapi): 50 connected calls per variant.

Polaris stack:

• Macro Polaris: Booked & Qualified Appointment Rate (BQAR).
• Sub-Polaris by stage: Open Rate (OR), Reply Rate (RR), Positive Reply Rate (PRR), Appointment Booking Rate (ABR).

Default genotypes:

• Cold email: Subject + First line + Body copy + CTA. (Loom variant: + Loom script + Loom delivery + Thumbnail.)
• Cold DM: Profile credibility signal + Connection note + Initial message + Follow-up sequence.
• AI voice: Opening line + Qualifier sequence + Pitch + Objection handling + Booking flow.

Common iteration anti-pattern: Iterating subject line when reply rate is bottlenecked. The subject line affects opens, not replies. This is sub-system confusion (§2.4).

Constraint stack to hold constant: Lead source, sender domain reputation, send volume, send time of day, follow-up cadence, profile/sender headshot. Drift in any of these invalidates the test.

6.2 Paid (Meta, Google, LinkedIn, programmatic)

Cycle time profile: Fast at the variant layer (3–7 days), slow at the offer/audience layer (2–4 weeks).

Default sample size for fitness verification: 1,000 impressions per variant minimum, $200–$500 spend per variant for cost-per-acquisition (CPA) signal.

Polaris stack:

• Macro Polaris: Cost Per Booked Qualified Appointment (CPBQA) or Cost Per Acquisition (CPA).
• Sub-Polaris: CTR, CPM, Landing Page Conversion Rate (LPCR), Lead-to-Show rate.

Default genotype:

• Meta/Google ad: Hook + Creative + Body + CTA + Audience.
• Note that Audience is a variable, not a constant, even though the platform treats it as separate. Same creative + different audience = different stimulus.

Common iteration anti-pattern: Iterating creative when audience is the bottleneck (or vice versa). Cold-traffic audiences need fundamentally different creative than retargeting audiences. Schwartz sophistication levels (§10.4) often differ across audience segments.

Constraint stack to hold constant: Landing page, offer, bid strategy, dayparting, attribution window.

6.3 Organic (LinkedIn, YouTube, X, Newsletter)

Cycle time profile: Slow. 30–90 day test windows. Highest latency, lowest signal-to-noise per cycle, but highest compounding effect when the loop produces a winner.

Default sample size for fitness verification: 10–15 posts/videos per variant style, observed across at least 3 weeks.

Polaris stack:

• Macro Polaris: Inbound Qualified Lead per post / per video.
• Sub-Polaris: Reach, Saves, Comments-from-ICP, Profile views from ICP, DM rate from ICP.

Organic iteration warning: Vanity metrics (likes, generic followers, total impressions) are not sub-Polaris metrics. They are noise. Optimizing them actively damages organic acquisition by training the algorithm on the wrong audience. Saves and ICP-comments are signal; likes are not.

Default genotype:

• LinkedIn post: Hook + Body structure + Format break + Identity frame + CTA (or no-CTA).
• YouTube video: Thumbnail + Title + Hook + Story arc + CTA + Description.
• Newsletter: Subject + First-line tease + Body structure + Sign-off.

Common iteration anti-pattern: Changing creative direction every 2–3 weeks because "engagement is down." Organic latency means a 2-week dip is inside the noise band. The Darwinian Loop here requires patience the operator usually does not possess. AI agents should enforce minimum observation windows on organic.

Constraint stack to hold constant: Posting cadence, primary platform, account positioning, bio/headline.

6.4 Cross-Channel Genotype Splicing

Wins from one channel are templates for the next. A LinkedIn hook that prints with a specific niche is highly likely to print as a cold email subject line in the same niche, with light adaptation. A Meta ad creative that wins on cold traffic often becomes the loom thumbnail for outbound. SalesBlaster's organizational advantage compounds when winning genotypes are catalogued centrally and spliced across channels.

This is what Morgan calls "Network Effect Conjugation" - and it is why running outbound + paid + organic in parallel is structurally more powerful than picking one. Each channel feeds the others' V1 quality.

7. The Pipeline - Where the Loop Lives in the Platform

The Darwinian Loop is a doctrine. The platform that executes it is a pipeline of bounded contexts - strict-boundary domain modules, each owning one state transition on the road from stranger to closed customer. Every stimulus, every metric, every iteration produced by the Loop has a home in exactly one of them.

7.1 How the Loop Flows Through the Pipeline

                ┌─── Loop feedback (sales → upstream) ─────────────────────────┐
                ▼                                                              │
  source ──► enrich ──► campaigns ──► (funnel) ──► sdr ──► crm ──► sales ────────┘
   ▲           ▲           ▲           ▲          ▲       ▲       │
   │           │           │           │          │       │       │
   └ "Polaris bottleneck this cycle was at sub-system X" ─────────┘

Loop telemetry is canonically emitted from sdr (outcome classification) and sales (the Darwinian feedback role). Every other context consumes this telemetry to inform its own iteration. Source iterates on lead-list quality based on closed-deal signal three steps downstream. Enrich iterates on personalization variables based on positive-reply signal in SDR. Campaigns iterates on stimulus genotypes based on classifier outcomes. The sales context closing the loop is what makes the system Darwinian rather than merely sequential.

7.2 What This Means Operationally

• A campaign instance does not live in one context. It spans the pipeline as a coherent operating unit.
• Bottleneck diagnosis is pipeline-scoped before it is variable-scoped. "Reply rate is low" is meaningless until you know whether the bottleneck is in enrich (bad data → bad personalization), campaigns (bad genotype), sdr (classifier mislabeling), or upstream of all of it in source (wrong ICP).
• Contexts communicate through events, never by reaching into each other's data. Iteration on one context does not mechanically break another - the architecture supports the Loop, it does not work against it.

7.3 Sub-System ↔ Pipeline Mapping

The six prospect-state sub-systems (§2.3) map to pipeline contexts as follows:

The sub-system axis is prospect-psychology-native; the pipeline axis is platform-architecture-native. Both are correct simultaneously. Operators and agents who can move between the two without losing precision are the high-leverage ones.

8. Mapping to the OCP Initiative Kernel

The Initiative Kernel is OCP's universal primitive for goal-directed work, and SalesBlaster's atomic unit of operational work. Per the kernel's recursive multi-tier structure, every campaign initiative is a Darwinian Loop wrapped in initiative-management infrastructure.

The canonical tier mapping is:

• Initiative (Tier 1) - long-horizon, quarterly. Has KPIs and scorecards. Example: "Q3 outbound for [Client]."
• Campaign = Project (Tier 2) - scoped, has definition of done. One campaign graph per project. Example: "[Client] - [Segment], V2."
• Journey - sub-project under the Project tier.
• Stage = Ticket (Tier 3) - atomic, binary completion. Single touchpoint or test cycle. Example: "Send V2 of subject-line variant to 300-prospect cohort."

This is not optional vocabulary. AI agents speak in these tier names; OCP paths follow these directories; ticket frontmatter binds a campaign node's templateRef. Operators using "campaign" and "initiative" interchangeably will produce ambiguous artifacts and the agents will produce ambiguous output downstream.

8.1 Kernel-to-Loop Mapping

8.2 What This Means for AI Agents

Every agent that participates in an initiative - whether it's the strategist agent, the copy agent, the deployment agent, the analytics agent, or any other in the agent hierarchy - must be aware of where its work sits in the loop.

• The copy agent does not "write copy." It produces a genotype-explicit V(x) for a specific variable, with the constants enumerated. Its outputs become OCP ticket content.
• The analytics agent does not "report metrics." It assesses Polaris vs. KPI and produces an iteration recommendation - needle-mover identification + mod level + V(x+1) rationale. Telemetry source is the campaign graph's node-transition events.
• The strategist agent does not "plan a campaign." It defines the initial conditions - Polaris, genotype, sample, latency, constants - that the loop will run against. Outputs become the campaign graph at publish time.

Typed agent-tool contracts enforce loop discipline at the schema layer. Tools that mutate campaign state (publish a graph version, advance a cohort, mark a sunset event) carry full invariant enforcement; tools that observe state (read metrics, query telemetry) are read-only. Agents cannot bypass the invariants by routing around them; the contracts make it impossible to ship a V2 without the V1 cohort having reached its sample size and latency window.

If an agent cannot articulate which step of the loop it is currently executing, it is hallucinating utility. Agent system prompts should make loop-position explicit.

8.3 The Initiative as a Petri Dish

Each initiative is a controlled environment. Cross-initiative contamination (running the same test on two clients simultaneously, mixing leads across campaigns, sharing senders across niches) destroys the validity of every concurrent test. Platform infrastructure must enforce initiative isolation at the data and identity layers - not as a nice-to-have, but as a scientific requirement.

9. The Seven-Phase Campaign Run Protocol

Distinct from the pipeline (§7). This is the operational discipline for executing one full Darwinian Loop cycle on a single campaign - the seven-phase pre-flight + run + iterate sequence that an operator (or a sufficiently disciplined AI agent stack) walks every time a new test launches.

SalesBlaster's seven-phase campaign run protocol is the operational expression of the six sub-systems plus the upstream research/offer phase that determines V1 quality. It is what the strategist + copy + deployment + analytics agents collectively execute, in order, for any campaign cycle.

Step 1 and Step 2 are where the butterfly effect (§4.7) is decided. Most campaign failures are decided here, before a single email is sent. Cheap V1 segmentation and weak offers force the loop to run 10–20 extra cycles. This is the single biggest place SalesBlaster invests upfront.

Step 3 is where Stimulus Genotype thinking (§3) is applied. Each stimulus in the chain gets its 2–4 variables enumerated, and V1 of each is locked. The chain is not "a cold email and some follow-ups" - it is a series of named stimulus genotypes, each with a defined micro-action target.

Step 7 is where the org compounds. Every cycle produces a V(x+1) brief that is either an iteration of a still-broken stimulus, or a scale order on a stimulus that has hit fitness. Both feed back into the campaign-asset library, where they become starting points (better V1s) for future initiatives. This is the network effect conjugation that makes SalesBlaster's output quality improve over time, structurally.

10. Cross-Framework Reinforcement

Morgan's framework is not in conflict with the canonical direct-response literature. It is the systems-level abstraction underneath it. Here is how the major frameworks map.

10.1 Dan Kennedy - No B.S. Direct Marketing

Kennedy's Message-Market-Media triangle is Morgan's macro equation in different language:

• Market = niche (input pool).
• Message = stimuli chain.
• Media = deployment method.

Kennedy's obsession with measurability and ROI tracking is the same discipline as the Darwinian Loop's data-logging requirement. His insistence that lead generation is a discipline, not an event is the latency principle. His advocacy of Magnetic Marketing (attract a specific psychographic, repel everyone else) is contrarian-trait selection (§11.3).

SalesBlaster mapping: Kennedy's "no B.S." stance is operationally enforced by the six-rule observation gate (§4.4). No vanity metrics, no "I think it's working," no anecdote-driven decisions.

10.2 Alex Hormozi - $100M Offers and $100M Leads

The Hormozi Value Equation:

\text{Value} = \frac{\text{Dream Outcome} \times \text{Perceived Likelihood of Achievement}}{\text{Time Delay} \times \text{Effort & Sacrifice}}

This is a stimulus genotype for the offer stimulus, with four explicit needle-mover variables. It maps perfectly to §3.1 and is the recommended default decomposition for any offer SalesBlaster designs.

Hormozi's $100M Leads four-prong model (warm outreach, cold outreach, paid ads, content) is the channel framework in §6. His "more better new" iteration heuristic is the modification-level decision in §4.5.

SalesBlaster mapping: Use the Hormozi Value Equation as the canonical Step 2 (offer architecture) decomposition. Make all four variables explicit before designing any stimulus chain.

10.3 Russell Brunson - Funnels and Hook-Story-Offer

Brunson's Hook-Story-Offer is the three-variable genotype for any persuasive asset:

• Hook = sub-system 1 stimulus (attention).
• Story = sub-system 2 stimulus (interest, mechanism, social proof).
• Offer = sub-system 6 stimulus (close).

His traffic temperature model (cold/warm/hot) is a mapping of audiences to sub-systems and to required Schwartz sophistication levels (§10.4).

His Dream 100 is contrarian attraction at the channel-selection level - go where attention is concentrated and competition is structurally low.

SalesBlaster mapping: Hook-Story-Offer is the default minimum-viable genotype for any net-new asset where deeper variable decomposition has not yet been done. It is a strong V1 default.

10.4 Eugene Schwartz - Market Sophistication

Schwartz's five levels of market sophistication are the canonical framework for why a stimulus genotype's traits work or don't in a given niche at a given time:

This is the diagnostic framework for trait selection (§3.3) and contrarian attraction (§11.3). Most B2B niches SalesBlaster works in are at level 3 or 4. Most coach/agency niches are at level 4 or 5. Diagnosing the level wrong by even one tier produces stimuli that fail at fitness despite being competently written.

SalesBlaster mapping: Step 1 of the Campaign Run Protocol (§9, niche/segment definition) must include an explicit Schwartz-level diagnosis per segment. The diagnosis directly drives V1 trait selection in Step 3.

Worked example - category creation as the Level 4→5 escape (Novu ACI, 2026-06): The notification-infrastructure market is saturated (Knock, Courier, MagicBell, SuprSend - direct "best notifications" claims are exhausted, i.e. Levels 2–3 are spent). Novu's response is the textbook high-sophistication move executed on both available levers at once: (1) it coins a new mechanism-category - "ACI" (Agent Communication Infrastructure), given a noun, a pronunciation, and a one-sentence definition, manufacturing a fresh Level-1 market to escape the saturated one; and (2) it borrows an existing belief by framing ACI as "the third leg of the agent triad" alongside MCP and A2A - mechanisms the prospect already accepts - so the new category arrives pre-credentialed. That is Level 4→5 in motion: when you cannot out-claim, you either name a unique mechanism or attach to who-the-prospect-is-becoming, and Novu does both. SalesBlaster parallel: "AI SDR" is sprinting from Level 3 ("ours is better") toward Level 4–5 saturation; the escape hatch is already named - the Darwinian Loop is our proprietary-mechanism category-creation play, and Charlie Morgan's Acquisition Field Theory is our borrowed-belief substrate. Watch the ACI launch as a live template for how to introduce and own a named mechanism: the definitional landing page, the triad framing that borrows credibility, the "we've done the hard part for years" proof. Run that exact motion for the Darwinian Loop when niche sophistication forces the move (§3.3 trait selection, §11.4 contrarian window).

10.5 Why These Frameworks Don't Replace Morgan

Each of the above is a partial map - Kennedy's strongest at media/measurement, Hormozi's at offer architecture, Brunson's at funnel structure, Schwartz's at copy psychology. Morgan's framework is the systems-level container that makes all of them composable. We use them as specialized tools inside the larger loop, not as alternatives to it.

11. Anti-Patterns and Failure Modes

These are the failure modes that destroy 95% of campaigns. They are not theoretical. Every one of these has cost SalesBlaster (or its predecessors, or its peers) months of cycle time. Memorize them.

11.1 Stimulus & Strategy Hopping (vs. Fundamental Seeking)

The Stimulus Hunter chases the latest copy template, the latest growth hack, the latest "proven script." Short-term wins, long-term decay. The Fundamental Seeker uses the loop to produce their own genotypes from first principles. SalesBlaster operators and agents must be Fundamental Seekers by default. Tactic libraries are starting points, not endpoints.

11.2 Stimulus Hypoesthesia (Niche Numbness)

Repeated exposure of a niche to similar stimuli causes the niche to go numb to those stimuli. The "best practice" cold email template that worked 18 months ago is now stimulus-hypoesthetic in most B2B niches. Decay is structural, not a copy-quality problem. The fix is contrarian iteration, not "writing better" within the same trait stack.

11.3 Classical Conditioning (Niche Burned)

Worse than hypoesthesia: when a niche has had bad past experiences with similar stimuli, they actively avoid them. Marketing-agency-style cold emails sent to e-commerce founders in 2024 trigger immediate negative response - not because the copy is bad, but because the genre has been classically conditioned negative. The fix is to avoid the burned genre entirely, even if your offer is technically in it.

11.4 Cyclical Stimulus Effectiveness - The Contrarian Window

Stimuli decay (10.2 + 10.3) but eventually rebound as niches forget. The operator who notices a previously-burned-out genotype recovering before the consensus does captures an asymmetric window. Contrarian attraction is the explicit strategy of betting on the recovery, against current consensus. Example: returning to text-only cold emails in a niche saturated with video.

11.5 Iterating Multiple Variables (Ceteris Paribus Violation)

Already covered in §4.5. Listed here because it is the single largest cause of campaign drift industry-wide. If you change two things and the result changes, you produced no information.

11.6 Premature Iteration (Latency Violation)

Killing a working campaign during its latency window because early data looks bad. Cold email with a 14-day full follow-up cycle cannot be judged at day 4. Operators do this constantly. Automated workflows must enforce minimum observation windows before allowing iteration commands.

11.7 Sub-Metric Optimization (Non-Linear Damage)

"Open rate is low, let me make the subject line more clickbaity." Result: open rate up, reply rate down, ABR down, Polaris destroyed. Sub-metrics live inside non-linear systems. Optimizing one in isolation can destroy the whole. Always optimize against Polaris, not against intermediate metrics.

11.8 Vanity-Metric Optimization

Particularly virulent in organic. Likes, follower count, total impressions are noise unless they correlate to inbound qualified leads. Optimizing for them trains algorithms on the wrong audience. The Polaris on organic is qualified inbound, full stop.

11.9 The 30-Call Trap (Regression to the Mean)

Distributions are clumpy. A 20% close-rate sales rep can lose 20 calls in a row and it is statistically normal. Operators panic at clump 12, change the script, destroy a working system, and the rep never recovers their original conversion rate because the constants were broken. Sample sizes exist to escape this trap.

11.10 Over-Engineering the Loop Infrastructure

A specific failure mode for SalesBlaster as a technical org. Building elaborate scientific-method infrastructure before any campaign is producing revenue is a way to feel productive while not generating clients. The loop runs on Google Sheets and a calendar reminder if it has to. Build infrastructure when its absence is the bottleneck - not before. Ship the loop. Then compress its cycle time.

11.11 Refusing to Sunset

A campaign graph that fails to recover after 3 consecutive cohort windows missing CFA must be archived, not nursed. Operators (and emotionally attached founders) frequently iterate a dead campaign past the sunset criteria because "we're so close" or "the next variant will fix it." This is a category error: the cycle has produced enough information to conclude the campaign cannot fund its own acquisition cost in the current market state. Resource reallocation - sunset, then return to the loop with a different segment, offer, or channel - is the correct move. The campaign graph version history is preserved for case-study analysis; nothing is lost by archiving except sunk cost.

12. Operating Principles - The 12 Commandments

Compressed for memorization. Every one of these is derived from sections above; they are the runtime checks an operator or AI agent should self-apply before any decision.

1. Polaris is sacred. Decisions are made against Polaris, not sub-metrics.
2. Genotypes are explicit. Before shipping any stimulus, name its 2–4 variables.
3. One needle-mover per cycle. Ceteris paribus or no test.
4. Hold the constants. Drift in constants invalidates the test.
5. Hit the sample size. Smaller samples are noise.
6. Wait the latency. Premature iteration kills working systems.
7. Do nothing during the run. Discipline beats intuition mid-test.
8. Log daily, on yesterday's data. Closed days only.
9. Fitness in KPI? Don't touch. Scale or petri-dish iterate.
10. Decay is structural. Plan V2 before V1 dies.
11. Splice winners across channels. Never let a winning trait sit single-channel.
12. Diagnose Schwartz level before writing any copy. Sophistication mismatch is the silent killer.

13. Glossary

• ABR - Appointment Booking Rate. Booked appointments / interested prospects.
• Adaptability - The fitness of a stimulus's traits relative to the niche's current psychology.
• BC (Bounded Context) - A strict-boundary domain module. SalesBlaster's pipeline (§7) is a chain of them: source · enrich · campaigns · funnel · sdr · crm · sales.
• BQAR - Booked & Qualified Appointment Rate. SalesBlaster's default outbound macro Polaris.
• Bottleneck - The lowest-conversion sub-system. Always exists. Always the only thing worth fixing.
• CampaignGraph - The aggregate root that represents a campaign as a DAG of nodes and outcome-labeled edges. Versioned, immutable after publish.
• CFA (Campaign-Funded Acquisition) - The criterion that a campaign graph must demonstrate it can fund its own acquisition cost. Failure across 3 consecutive cohorts triggers Sunset.
• Ceteris Paribus - Latin for "all else equal." The discipline of holding all variables constant except the one being tested.
• Classical Conditioning - A niche actively avoiding stimuli they associate with past negative experiences.
• Constants - Variables in the system that are explicitly held fixed during a test.
• Contrarian Attraction - The strategy of deploying stimuli opposite to current consensus to exploit cyclical stimulus effectiveness.
• CPBQA - Cost Per Booked Qualified Appointment. SalesBlaster's default paid macro Polaris.
• Cross-Pollination - Combining winning genotypes from two campaigns/channels into a new variant.
• Cycle Time - The duration of one full loop execution. The variable SalesBlaster's tech stack exists to compress.
• Cyclical Stimulus Effectiveness - The pattern by which stimulus genotypes lose effectiveness through over-exposure and recover after dormancy.
• Darwinian Loop - SalesBlaster's name for the scientific-method-driven iteration cycle on stimulus genotypes.
• Fitness - A stimulus's measurable conversion against KPI.
• Genotype - The variable stack that defines a stimulus.
• Initiative Kernel - OCP's canonical recursive multi-tier work-unit primitive: Initiative (Tier 1) > Project (Tier 2) > Ticket (Tier 3) > Sub-Ticket (Tier 4, optional). Campaigns are Project-tier instances.
• KPI - Key Performance Indicator. The threshold against which fitness is measured.
• Latency - Delay between input and observable output.
• Latent Conditions - Dormant situational/psychological state that makes a human a candidate prospect.
• Loom Cold Email - Outbound stimulus combining email + personalized loom video.
• Macro Polaris - The single revenue-attached metric for the campaign as a whole.
• Modification Level - Slight, Moderate, or Complete change to the needle-mover variable.
• Needle-Mover Variable - A genotype variable whose change materially moves Polaris.
• OCP (Organizational Context Protocol) - The canonical standard for organizing knowledge artifacts as markdown-in-git with frontmatter contracts. This document is an OCP-conformant note artifact.
• Petri Dish Test - A parallel-environment iteration of a working system to avoid disturbing the production version.
• Polaris (Polaris Star) - The single most important metric to optimize for, against which fitness is measured.
• PRR - Positive Reply Rate.
• Schwartz Sophistication - The five-level model of market consciousness state, governing trait selection.
• Six Sub-Systems - Latent conditions → attention → interest → appointment → show → primed prospect → closed deal. Prospect-state axis; orthogonal to the pipeline axis (§7.3).
• Splicing - Inserting a winning trait or variable from one stimulus into another's genotype.
• Stimulus - Anything exposed to a human to provoke a specific micro-action.
• Stimulus Chain - The full sequence of stimuli that move a human from latent to closed.
• Stimulus Hunter - An operator who copies tactics without understanding fundamentals. Anti-pattern.
• Stimulus Hypoesthesia - Niche numbness from over-exposure to similar stimuli.
• Sub-Polaris - A stage-level conversion metric within a sub-system.
• Sunset - The terminal phase of the Darwinian Loop: a campaign graph that cannot recover after N iterations is archived rather than nursed.
• SUR - Show-Up Rate.
• SCR - Sales Conversion Rate.
• templateRef - The field on a campaign node that points to an OCP ticket file by path. The bridge between the Content layer (markdown-in-git) and the Structure layer (the runtime CampaignGraph).
• Throughput - Volume of humans flowing through the system per unit time.
• Traits - Adjective-level descriptions of a stimulus's character (e.g., punchy, transparent, mysterious).
• Variation - Calculated or random changes introduced to a needle-mover variable to produce V(x+1).
• V(x) - Version label for a stimulus genotype iteration (V1, V2, V3, …).
• Yield - Total clients out the bottom of the system per unit time.

14. Source Materials

• Charlie Morgan / Imperium - Acquisition Field Theory, Morgan's Acquisition Systems Theory, Iterative Darwinian Acquisition, Antifragile System Design, Scientific Method Step Summary, The Client Acquisition Shell, Sub-Systems Visualizer. Origin of the conceptual stack this document operationalizes for SalesBlaster.
• Cross-framework primary sources - Dan Kennedy, No B.S. Direct Marketing; Alex Hormozi, $100M Offers and $100M Leads; Russell Brunson, DotCom Secrets and Expert Secrets; Eugene Schwartz, Breakthrough Advertising; Chris Voss, Never Split the Difference.

15. Final Note on This Document's Status

This is v1.0. It is a seed. The expectation is that it will be extended, refined, and made more precise as SalesBlaster's campaigns produce more data and as the agent system matures. Section headers above are stable; content beneath them extends. Future versions add detail; they do not restructure.

The most dangerous version of this document would be one that became more elaborate without the Loop at its center generating revenue. If that ever happens, this document has become over-engineering, and a future maintainer should aggressively cut it back to the four operating laws in §1 and rebuild from there.

The Loop is the point. Everything else is scaffolding.

In-field proof content participates in this loop: the content produces client results, and those results become the denser proof injected into the next content cohort, so each cohort converts better than the last.

• End of Document v1.0