Subtypes (Beta 4)

Probably for the next big revision of the game, I will want to look into changing the jargon pertaining to character options. Here's the current wording, explained:

• Subclass: "mandatory combat role" is how I generally refer to this. At the start of combat, you have to pick one, or else your class doesn't function. Examples: Druid [Shapeshifter/Summoner], Guardian [Shaman/Warden], Mystic [Necromancer/Warlock]
• Path: essentially your "mandatory Archetype." Paths are generally distinct classes that have been put under the umbrella of a single class, for different reasons. Examples: Cleric [Crusader/Invoker], Sage [Monk/Wizard], Rogue [Assassin/Sorcerer]
• Archetype: these basically serve to narrow a class down into a more specific "flavour" or niche; currently, Archetypes are not mechanically necessary in order for classes with them to function. Some classes can choose an Archetype in addition to a Subclass, Path, or Role.
• Role: this hews fairly close to the 4e D&D combat roles. Similarly to Archetypes, it is not mechanically necessary to pick one; they narrow the focus of your character, and can be selected at the start of combat. Currently, the following roles are used in the text: Defender, Striker, Controller, Support.

Archetypes and Paths are both locked in at character creation; Paths are mandatory, Archetypes are not.
Roles and Subclasses are both selected at the start of combat; Subclasses are mandatory, Roles are not.
It's also worth noting that Paths, Roles, and Subclasses do not overlap each other, on any class; classes with these options may, however, also have Archetypes.

I think the problem is that each of these keywords seems to convey a sense of permanency, but only two of them actually are (and one of those is optional.) "Subclass" is the word that seems the biggest misnomer. At one point, "Archetype" covered what would now include Archetypes, Subclasses, and Paths (and all were mandatory); "Subclass" was just a placeholder that was used to pull those specific options out from under the larger umbrella.

Should Subclasses be merged into Roles? It seems like one of the simpler options -- Roles would have to become mandatory to facilitate this, though, which would increase some of the complexity for those classes (Fighter, Warlord, Bard, Adventurer, and Barbarian.) The problem then becomes that the existing Subclasses don't feel like "Roles" so a new piece of jargon may need to be invented to replace them both.

Should Subclasses be reclassified as "Combat Paths" and Roles as "Combat Archetypes"? It would be nice to have one word for "mandatory" customization, and one for "optional" that could then each have a "combat" or similar tag added, to specify when those options could be invoked.

I'm going to give this all some serious consideration, and see which loadout I like most. Then, that will make its appearance in the next iteration of the rules text.