02
rules create the roles
Our rules made the roles necessary. Wars needed planning. Alliances and NAPs needed negotiation. Public forums needed people who could represent the clan. New members needed a structure that placed them somewhere.
Status followed responsibility and trust. Breaking an agreement could damage more than one player. A role mattered because the group had consequences attached to it.
03
people move between positions
In my later online communities, most roles were informal. One person answered technical questions. Another kept a conversation alive. Somebody else remembered an old resource or welcomed a newcomer.
The same person can change positions as the world changes. A defender can become a critic. A newcomer can become a historian. Repeated roles can harden into identity when the group keeps returning to the same person for the same kind of help.
04
what roles reveal
Roles show me the tribe's needs in motion. RAGE needed strategy, diplomacy, intelligence, war, and a way to develop members through levels. A Discord community needs people who welcome, explain, connect, remember, challenge, and turn a good conversation into something others can find later.
I learned the harder version too. If every answer, introduction, event, and useful resource depends on me, the group may still be valuable. It has not developed many roles of its own.
This matters beyond content. It affects leadership, moderation, conflict, product adoption, community memory, and who can find a useful place inside the group.
05
how I want to use this
When I enter a tribe, I look for the work people already recognize. Who explains? Who decides? Who protects the boundary? Who remembers the history? Who introduces newcomers? Who can challenge the group without being ignored?
Then I ask which role I have actually earned, which one people already bring me, and whether something important keeps falling between the existing roles. The language, rules, and rewards usually make the answer easier to see.