The framework · v2.2

Lane DNA

A three-letter language for the bot lane. It names what an ADC and support duo is, so that Jinx with Lulu and Ashe with Lulu stop being two matchups to memorise and become one lane to learn. It never names who wins.

The whole system in one paragraph

Every duo gets a family code: one letter for the ADC's fighting reach, one for how the ADC's damage is delivered, one for what the support is there to do. Jinx and Lulu are LDE: long-range, DPS, enchanter. Lucian and Leona are MBA: standard-range, burst, all-in. A matchup is one family into another, written LDE vs MBA. Three letters is the whole public vocabulary. Underneath it sits a fuller record of each duo's traits, which the codes deliberately forget.

Letter one: the ADC's fighting reach

The reach at which the ADC delivers its ordinary, repeatable fighting damage. Not the longest ability in the duo's kit, and not a support's hook.

LLong-rangeExtended attack reach is central to the identity. Ashe, Caitlyn, Jinx's rockets.

MStandard-rangeThe full package works at ordinary marksman range. Lucian, Vayne, Ezreal.

SShort-rangeThe damage needs proximity: melee mechanics or entering the opponent's space. Samira, Nilah.

Short is about proximity mechanics, not a small range number. Lucian's range is on the low side, but his complete package works at full attack range, so he is standard. Ezreal has a long poke spell and ordinary fighting reach; those are two facts, and the code keeps only the second.

Letter two: how the damage arrives

How the characteristic damage is distributed through a fight, not how much of it there is.

BBurstA bounded sequence or a concentrated window is a defining source of power. Lucian.

DDPSRepeated damage over continued contact is the engine. Jinx, Ashe, Vayne.

HHybridBoth a concentrated sequence and continued output are substantial. A positive claim, never a shrug. Samira, Ezreal.

Every marksman attacks repeatedly; that alone does not make a champion DPS. Having both attacks and spells does not make a champion hybrid. H is earned by two real damage modes, and an uncertain case stays uncertain rather than defaulting to it.

Letter three: what the support is there to do

The support's predominant contribution to this duo in an established lane.

EEnchanterAdds power or durability to an ally: buffs, shields, healing. Lulu.

PPokeRepeated ranged damage and health pressure. Damage-built Lux.

KPickCreates a catch or an isolation without committing its body first. Blitzcrank.

AAll-inStarts a fight by committing its body into enemy space. Leona.

WWardenPeel, and disrupting the opponent's engage. Braum.

A warden can still engage and an all-in support can still protect. The letter is the predominant job, and the rest lives in the duo's fuller record. When two jobs are genuinely equal, the duo gets two profiles rather than a forced answer.

Worked examples

Illustrative assignments under conventional builds. The support does not determine the type: hold Lulu fixed and the family moves with the ADC. Swap the support under Jinx and only the third letter changes.

Family	Duo	Reads as
LDE	Jinx + Lulu	Long-range DPS with an enchanter
LDE	Ashe + Lulu	Same family; Ashe's arrow lives in the traits, not the code
MBE	Lucian + Lulu	Standard-range burst with an enchanter
MDE	Vayne + Lulu	Standard-range DPS with an enchanter
SHE	Samira + Lulu	Short-range hybrid with an enchanter
LDA	Jinx + Leona	Long-range DPS with an all-in support
MBA	Lucian + Leona	Standard-range burst with an all-in support
MBW	Lucian + Braum	Standard-range burst with a warden
LDK	Ashe + Blitzcrank	Long-range DPS with a pick support
MHE	Ezreal + Lulu	Standard-range hybrid with an enchanter; the poke is a trait
LHP	Caitlyn + Lux	Long-range hybrid with a poke support

Jinx and Lulu into Lucian and Leona is LDE vs MBA: long-range DPS with an enchanter against standard-range burst with an all-in support. That sentence tells you what the lane will feel like. It does not tell you who wins, and it is not supposed to.

The rules that keep it honest

No letter implies strength. Codes describe structure. Who wins a lane depends on players, jungle, and the wave, and lives in separate, evidenced fields.
State never changes the code. Health, cooldowns, the current wave, and an existing lead are not part of the identity. A planned build or level can be; a missed spell cannot.
Uncertainty stays uncertain. An unresolved position is recorded as unresolved, never upgraded to hybrid or to a guess.
The alphabets do not overlap. Reach, damage, and support use disjoint letters, so a code cannot be misread even if scrambled.
It is tested before it is trusted. Independent raters classified 40 duos five times each. Reach, damage, and support function agreed at a level that clears the framework's own adoption gate. The internal variant layer is still being refined.

Where this goes

Lane DNA is the vocabulary Leaguio Coach uses when it writes your review: which lane you were in, what that kind of lane asks of you, and which of your flagged moments belong to the lane rather than to the champion. A companion framework for whole five-champion compositions exists on paper and ships only after this one proves itself.

See how the coach uses it →