Behavioral
Behavioral

Dragon Identification Protocol

Behavioral Mechanics

Dragon Identification Protocol

Every man has one animal he's actually fighting, and most men spend years swinging at the wrong one.
developing·concept·2 sources··Jun 2, 2026

Dragon Identification Protocol

Name the Beast Before You Fight It: Desire-Dragons and Aversion-Dragons

Every man has one animal he's actually fighting, and most men spend years swinging at the wrong one.

Bell's contribution to the framework is brutally simple and weirdly clarifying. He says your primary psychological opponent — the thing that's actually running your life from underneath — is one of two kinds. Either it's a desire-dragon (it pulls you toward something that consumes you: a substance, an ambition, a person, a hit you keep chasing) or it's an aversion-dragon (it pushes you away from something you fear: rejection, failure, exposure, a conversation you won't have)1. The two dragons look different, feel different, and — this is the whole point of the protocol — require completely different strategies. Fight a desire-dragon with aversion-dragon tactics and you'll lose for years without understanding why. So before any of the real work, you do the identification: which dragon is mine?

What the Dragon Protocol Actually Is

The Dragon Identification Protocol is the second of the eight cultivation practices the framework prescribes for Stage 3, the Road of Trials — the diagnostic-and-engagement routine for naming your primary psychological opponent and building a strategy specific to its type1. It's filed in behavioral-mechanics because its cargo is operational: it's a procedure you run on yourself, not a description of an internal state. (The internal state — the daimon-soul polarity the dragon framework grows out of — lives on the psychology side, at the Daimon-Soul Map.)

The structural insight is that undifferentiated self-improvement fails because it treats all inner resistance as one thing. A man says I need more discipline when his actual problem is a fear he's never named, and discipline applied to a fear just produces a more disciplined avoidance. The protocol forces specificity. It says: stop fighting resistance in general; find the one dragon that organizes most of your stuckness, identify its type, and deploy the strategy that type actually responds to.

The Two Dragons and Their Strategies (The Internal Logic)

The desire-dragon. It pulls. The substance you keep returning to, the ambition that's eating your relationships, the validation you can't stop chasing, the person you orbit. Its signature is toward — a craving that overrides what you know. Bell's strategy for the desire-dragon is not white-knuckle suppression (which feeds it, because suppression keeps it central). It's a three-part replacement: substitution + community + meaning-making1. Substitution gives the craving somewhere else to go. Community removes the isolation the desire feeds on. Meaning-making gives the energy a higher object — the same drive, redirected upward, which is the whole framework's move with any fire. The desire-dragon is starved by redirection, not by force.

The aversion-dragon. It pushes. The fear that organizes your life by what you won't do — won't apply, won't ask, won't ship, won't confront. Its signature is away — an avoidance dressed up as prudence or busyness or not-the-right-time. Bell's strategy is the inverse of the desire-dragon's: systematic exposure + accountability1. Exposure, because the aversion-dragon only shrinks when you approach the thing it flees; it grows in exact proportion to the avoidance. Accountability, because the aversion-dragon is a master of private deferral, and it cannot survive another person watching whether you actually did the thing. You don't redirect an aversion-dragon — you walk straight at it, repeatedly, in front of a witness.

The specific variants. Bell extends the typing to particular dragons with tailored tactics: addiction (the desire-dragon strategy — substitution, community, meaning); heartbreak (grieve fully, then channel the grief into art or service); chronic illness (reframe as ordeal, maximize the agency that remains)1. The variants share the structure: name the specific beast, match the strategy to its mechanism, then confront it daily — one hour minimum, the framework says — on a timeline of one to two years per major dragon.

Information Emission (Synergies & Handshakes)

This page gives the Stage 3 architecture its aiming mechanism. Heat Channeling supplies the energy; the Dragon Protocol supplies the target. Without it, a practitioner can have enormous channeled intensity and no idea where to point it, and undirected intensity in Stage 3 tends to dissipate into general busyness.

It hands the psychology corpus a clean behavioral counterpart to the daimon-soul polarity: where the Daimon-Soul Map explains how the polarity forms and operates inside a person, this page instructs how to operate on it deliberately. And it gives the crisis-typology a triage tool — many of the seven crises resolve faster once the practitioner has typed the dragon underneath the crisis.

Analytical Case Study: The Man Who Thought He Needed Discipline

He came to the work convinced his problem was discipline. He was forty-four, talented, and stuck — a business idea he'd been about to launch for three years, a body of skill he'd never taken public. He'd read every productivity system. None of them moved him, and he concluded he was lazy.

The protocol re-typed him in one session. His dragon wasn't desire — there was no craving pulling him off course. His dragon was aversion: a fear of public failure so old he'd stopped seeing it as fear and started experiencing it as realism (the market's not ready, the product's not done, the timing's off)1. Every productivity system he'd tried had been a desire-dragon tool — substitution, redirection, willpower — applied to an aversion-dragon. They couldn't work, because they all let him keep avoiding the one thing the aversion-dragon required him to approach.

The aversion strategy was the opposite of what he'd been doing. Systematic exposure: ship something small and public this week, then something bigger, deliberately walking at the fear. Accountability: tell three brothers exactly what he'd ship and by when, so the private deferral had a witness. The first exposure was terrifying and the relief afterward was physical — the dragon was smaller the next day, exactly as the protocol predicts. Within a year the business was launched, not because he'd found discipline but because he'd finally been fighting the right animal with the right weapon. What the case shows: the entire failure was a mis-identification. He'd spent three years losing to a dragon he'd never named, with tactics built for a different beast. The naming was ninety percent of the cure.

Implementation Workflow: The Hour With the Dragon

Morning, twenty minutes before the day grabs you. You open the journal and you ask the one question the protocol is built on: what's the thing I keep not doing, or keep doing against my own judgment? You don't theorize. You write the concrete instances. The email unsent for a week. The fourth night this month you stayed up scrolling instead of sleeping. The conversation you've rehearsed and never had.

Then you sort them by direction. The scrolling pulls you toward — that's a desire-dragon's track. The unsent email and the unhad conversation push you away — aversion. You look at the pile and you find the one dragon that most of the instances actually belong to, because there's usually a primary one organizing the rest. For this man it's aversion, and naming it changes the strategy from try harder to resist to walk at the fear, with a witness.

Now the hour itself — the daily confrontation the framework prescribes1. If it's an aversion-dragon, the hour is exposure: you do the smallest version of the avoided thing, today, and you text a brother that you did it. If it's a desire-dragon, the hour is redirection: when the craving fires, you run the substitution, you reach for the community instead of the hit, you point the energy at the meaning. You log the encounter either way — not the feeling, the fact: did I approach, or did I avoid; did I redirect, or did I feed it. The log is how you'll know in six months whether the dragon is shrinking, because day to day it never feels like it is.

The Dragon Protocol Failure (Diagnostic Signs)

Mis-typing the dragon. The commonest failure — fighting an aversion-dragon with desire-dragon tools or vice versa. The man who applies willpower-and-suppression to a fear (aversion) just gets better at avoiding; the man who applies exposure-and-confrontation to a craving (desire) keeps the craving central and feeds it. The diagnostic: if the strategy isn't working after months of honest effort, suspect the type is wrong before you suspect your effort.

Naming many dragons and fighting none. The protocol says find the primary dragon. The man who lists fifteen problems and works on all of them works on none — he's diffused the confrontation into a self-improvement to-do list. The diagnostic: can you name, in one sentence, the single beast that organizes most of your stuckness? If you can't, you haven't done the identification.

Identification as substitute for confrontation. He becomes an expert on his dragon — its origins, its mechanism, its childhood roots — and never actually fights it. The naming was supposed to be ninety percent of the cure only because it enables the daily confrontation; absent the confrontation, the naming is just sophisticated self-description. The diagnostic: did you approach the thing today, or did you analyze why you don't?

Evidence / Tensions / Open Questions

Evidence. The desire/aversion split maps cleanly onto well-established behavioral distinctions — approach versus avoidance motivation, appetitive versus aversive conditioning — and the type-specific strategies track standard practice: exposure therapy for avoidance/anxiety (the aversion-dragon strategy), and substitution-plus-community-plus-meaning for addiction (the desire-dragon strategy, which is essentially the structure of effective recovery programs). The framework's contribution is the upfront typing as a triage step before strategy selection.

Tensions. The binary may be too clean. Many real opponents are mixed — an addiction (desire) that's also an avoidance of intimacy (aversion), where the craving and the fear feed each other. The protocol's insistence on a single primary type is a useful simplification that can mis-serve genuinely braided dragons. The framework's defense is pragmatic: even a mixed dragon usually has a dominant track, and fighting the dominant one first loosens the other. But the page should not pretend the binary is exhaustive.

The one-hour-daily, one-to-two-years-per-dragon timeline is asserted, not established. It's a reasonable order-of-magnitude for deep behavioral change, but the framework states it with more precision than any evidence supports.

Open questions (tracked in META).

  • For a braided desire-aversion dragon, does fighting the dominant track reliably loosen the other, or can attacking one strengthen the other (e.g., exposure to a feared thing intensifying a substitute craving)?
  • Is the primary dragon stable across the years of Stage 3, or does defeating one dragon simply reveal the next, so that the protocol is really a sequence rather than a single fight?

Author Tensions & Convergences

The dragon framework is Bell's, but it sits inside the Donovan-Billinge architecture, and the seams matter.

Bell supplies the whole typology — the desire/aversion split, the per-dragon strategies, the daimon-soul polarity it grows from12. Billinge's contribution is implicit: the channel fire upward logic that the desire-dragon's meaning-making strategy depends on (you don't kill the desire, you redirect its heat to a higher object) is the same sublimation move that runs through Billinge's whole somatic-alchemical reading. Donovan supplies the accountability leg of the aversion strategy — the brotherhood that witnesses whether you actually approached the fear is Donovan's warband doing developmental work.

The convergence is that all three reject suppression: Bell redirects the desire, Billinge sublimates the fire, Donovan's brothers force the approach — none of them say just resist. The tension is whose mechanism is primary. Bell would say the typing comes first (you can't redirect or approach correctly until you know the dragon's kind); Donovan would say the brotherhood comes first (you can't sustain any strategy alone). What the split reveals is that the protocol is load-bearing on both: the right strategy, deployed in front of the right witnesses. Either alone tends to fail — correct strategy run in isolation collapses; brotherhood without correct typing just witnesses you losing to the wrong beast.

Cross-Domain Handshakes

These domains connect because the same inner opponent can be described as a formed psychological structure, operated on as a behavioral target, or located within a specific life-crisis — and a man needs all three views to actually beat it.

  • Psychology: Daimon-Soul Map — this is the protocol's parent mechanism. The Daimon-Soul Map explains how the polarity forms and operates internally — the ascending daimon-pole and the receptive soul-pole, and how possession by either produces a characteristic distortion. This page instructs how to operate on that polarity tactically — type the dragon the possession produces, then deploy the matched strategy. Where psychology explains the internal process, behavioral-mechanics instructs the external application. The tension between them reveals something neither domain produces alone: the dragon-typing works because it externalizes an internal polarity into a nameable opponent — and that externalization is itself the first therapeutic move, turning a diffuse internal condition into a discrete thing you can walk toward or redirect. The risk the handshake exposes: a behavioral protocol that names a beast can let a man fight a symptom while the underlying soul-pole imbalance the psychology page describes goes unaddressed.

  • Psychology: Solar Hero Crisis Typology — the crisis typology maps seven distinct developmental crises; the dragon protocol is a triage tool that often sits underneath them. A man in Loss of Fire frequently has a desire-dragon (an ambition that consumed and then collapsed); a man in Exile frequently has an aversion-dragon (a fear of the rupture he's now living). The handshake produces a layered diagnosis: name the crisis (typology), then type the dragon underneath it (this protocol), then deploy the matched strategy. The insight: the crisis is the weather, the dragon is the mechanism — and treating the weather without the mechanism leaves the storm to reform.

The Live Edge

The sharpest implication. If Bell is right, most of the years you've spent failing to change yourself were spent fighting the wrong animal with the wrong weapon — and the failure had nothing to do with your willpower, your character, or your seriousness. That's simultaneously a relief and an indictment. The relief: you're not weak, you were mis-aimed. The indictment: the mis-aiming was avoidable; the typing takes one honest session, and you skipped it for years because general self-improvement let you feel like you were working without ever walking at the one thing you most needed to face. The uncomfortable third wire is that the aversion-dragon specifically disguises itself as realism — every reason you have for not doing the avoided thing feels like sober judgment, not fear, which is precisely how it survives. To run the protocol honestly you have to entertain that your most reasonable-sounding constraints are the dragon talking. That suspicion of your own good reasons is the live edge.

Generative questions.

  • If the aversion-dragon disguises itself as realism, how does a practitioner distinguish a genuine constraint from a fear wearing a constraint's clothes — is there any test other than walking at it and seeing what happens?
  • Bell's typing is binary. What would a more honest typology of inner opponents look like — and would added precision improve the strategy, or would it just give the analysis-as-avoidance failure mode more to chew on?

Connected Concepts

Footnotes

domainBehavioral Mechanics
developing
sources2
complexity
createdJun 2, 2026
inbound links8