Article 10 showed how one routing choice affects the work that follows. Hermod.gg brings the same question to champion selection: what changes if we choose Ashe instead of Varus? Its public example keeps Aatrox, Master Yi, Orianna, and Shen as allies, and Renekton, Qiyana, Syndra, Xayah, and Soraka as opponents.1

The comparison follows contributions to team jobs. Varus's Living Vengeance is linked to offensive-stat enhancement and maintaining damage uptime in Protect and Convert. Ashe's Hawkshot is linked to scouting and converting a removal in Breach and Remove. These are selected paths; each champion can contribute in other ways.

The map makes those relationships visible. The timing view illustrates when the contributions might matter in a plan to approach, engage, and convert an opening.

Alternative champion contributions and schematic windows of usefulness In the Varus branch, Living Vengeance can supply offensive-stat enhancement, which can support maintaining damage uptime in Protect and Convert. In the Ashe branch, Hawkshot can supply scouting, which can support converting a removal in Breach and Remove. A dashed change-pick arrow connects the alternative mechanics. Soraka is conditional pressure: the damage-uptime link applies if the damage source can be disrupted, and the removal link applies if the enemy controls entry or the contest area. The timing view uses Approach, Engage, and Convert categories. Ashe's scouting window covers Approach; Varus's damage-uptime window covers Engage and Convert. The windows are schematic, with no seconds, ability durations, or estimated match outcomes. Relationships in the two candidate branches Varus Living Vengeance Offensive-stat enhancement Maintain damage uptime Protect and Convert Ashe Hawkshot Scouting Convert a removal Breach and Remove Soraka conditional pressure can supply can support can supply can support change pick if damage sourcecan be disrupted if enemy controlsentry or contest area Illustrative windows of usefulness Approach Engage Convert Scouting / Ashe Damage uptime / Varus Relevant information Sustain the damage window Schematic windows only; no ability durations or match outcomes are estimated.
The same contributions appear as relationships and as windows in a plan. Blue and teal compare alternative picks. The bars are schematic; no ability durations or match outcomes are estimated.

A minimal implementation stores selections separately from the relationships they activate. Copy the case, replace the selected-pick fact, and run the same rules again. Keep the other picks and model version fixed. Recompute conclusions that depend on the changed pick, including downstream conditions and pressure.

Soraka remains in both cases, but the job and condition attached to the pressure finding change. Reusing the old finding after changing only the champion's name would give the wrong explanation.

An illustrative phrase pattern is “<capability> supports <job> when <condition>.” Each finding can retain its path back to a recorded mechanic, a capability mapping, and the conditions used to derive it. That path lets a reader inspect the reasoning.

Compare the supported jobs, their conditions, and remaining gaps. Losing one contribution path does not prove the whole team lost that capability: another ally may supply it. Missing coverage should remain unresolved until checked.

This is counterfactual reasoning within a declared model: change one choice, derive its consequences, and compare the two cases. The result explains a strategic difference; it does not establish a universal ranking or predict a win.

References

  1. Source: Hermod.gg, “Change the pick. Understand the consequences.” The figures below are simplified explanatory views. ↩