Leadership Charter

Structural, Cultural, and Leadership Alignment

I. Core Principle

This Charter establishes:

  • Clear leadership roles
  • Clear accountability
  • Rewards based on contribution
  • An open and casual membership culture
  • A defined chain of authority in urgent situations

This is a complete leadership framework for Season 2.

II. Cultural Direction

Casual by Choice, Competitive by Reward

We do NOT have:

  • Login requirements
  • Mandatory participation quotas
  • Minimum power requirements
  • Required event attendance

Anyone can join. There is no forced playstyle.

However: Rewards, rank advancement, and leadership roles will reflect contribution.
You can play casually, but rewards will reflect effort.

III. Clear Leadership Authority

Each leadership title has final authority within its assigned area. If a leader cannot fulfill their responsibilities, they must clearly communicate that so the role can be addressed appropriately.

Short-term assistance during planned absences or urgent situations is acceptable — but it must be clearly communicated within leadership.

Clear ownership prevents confusion.

IV. Executive Leadership – R5

Domain: Diplomacy & Overall Direction

Core Responsibilities:

  • All external diplomacy
  • Final authority over reward distribution
  • Discretionary R3 spots for high-value contributors who may not meet VS benchmarks
  • Setting alliance culture and long-term direction

Activity Expectations:

  • Consistent daily engagement (when possible and applicable)
  • Clear notice if unavailable
  • Ownership of alliance-wide strategy

If R5 cannot consistently fulfill these duties, leadership must address it. R5 must also be aware of the importance of their position and if they cannot maintain their duties, step down honorably.

Executive Communication Standard

R5 is expected to maintain direct, ongoing communication with each title-holding R4 individually. Routine operational discussions should not rely solely on the R4/R5 group chat.

R5 should maintain separate communication with:

  • Warlord – War goals, territory plans, battle posture, timing
  • Muse – R3 discretionary cases, ranking integrity
  • Recruiter – Growth planning, merger discussions, expansion strategy
  • Butler – Event scheduling aligned with alliance objectives

R5 serves as the primary link between all title holders. They are responsible for maintaining awareness of the time-sensitive nature of events, coordinating attack timing with the Warlord, and aligning event execution with the Butler to ensure strategic efficiency and overall cohesion.

The R4/R5 group chat is reserved for:

  • Emergency coordination
  • Discussions about major decisions
  • General discussions that should be kept off the main alliance channel

Strong leadership requires proactive guidance, not reactive group debate.

Alliance Bio

R5 is responsible for updating and maintaining the alliance bio to include information about plundering, allies, ways for members to contribute or rank up, and anything else that may be needed as agreed upon by the leadership team.

V. Warlord (R4)

Domain: War Strategy & Battlefield Execution

Responsibilities:

  • War planning and execution
  • Territory capture coordination
  • Scheduling Desert Storm (Primary)
  • Defensive mobilization
  • PvP tactical leadership
  • Real-time direction during conflict

Diplomatic matters fall under R5 authority but can be delegated on a case by case basis to Warlord. The Warlord’s focus remains operational and battlefield-specific.

VI. Butler (R4)

Domain: Event Scheduling & Logistics

Responsibilities:

  • Scheduling Alliance Train
  • Assigning Train participation
  • Scheduling Marshal
  • Scheduling Zombie Invasion
  • Scheduling Desert Storm (Backup)
  • Issuing consistent event reminders

Operational consistency maintains alliance rhythm and engagement.

VII. Recruiter (R4)

Domain: Growth & Expansion

Responsibilities:

  • Recruiting new members
  • Vetting applicants
  • Negotiating mergers with smaller alliances
  • Maintaining a sustainable growth strategy

Growth should be intentional and steady.

VIII. Muse (R4)

Domain: Performance Tracking & Rank Structure

Responsibilities:

  • Tracking weekly VS scores
  • Managing R1–R3 rank assignments
  • Monitoring alliance tech donations
  • Assisting R5 in identifying high-value contributors beyond VS

VS remains the primary activity indicator, but not the only measure of value. Final reward discretion remains with R5.

IX. Contingency Authority Structure

In urgent situations where a leader is unavailable for something that falls under their authority, another may assist temporarily. Temporary substitution does not permanently reassign responsibility. If a leader cannot consistently fulfill their duties, the position must be addressed formally.

X. Communication Expectations

All leadership roles require:

  • Daily engagement
  • Clear communication of absences
  • Ownership of assigned domain

Uncommunicated inactivity creates strain and weakens leadership integrity.

XI. Leadership Selection Reform

R4 will no longer be determined purely by general vote.

R4 Promotion Process:

  • Discussion among current R4 leadership
  • Evaluation of contribution and capability
  • Final decision by R5

No member should reach R4 without demonstrating:

  • Ability to answer member questions
  • Ability to assist lower-ranked players
  • Ability to provide strategic guidance
  • Ability to contribute consistently
  • Consistently using shields appropriately

Leadership is earned through action. These standards set the example for the lower ranked members of the alliance.

XII. R4 Accountability Standards

R4 must first be active and engaged in leadership and group discussions. As long as that engagement is present, they must also either:

  • Meet R3 performance standards
  • OR
  • Contribute in meaningful and visible ways within the alliance

Examples of meaningful contribution include:

  • Teaching mechanics
  • Answering gameplay questions in chat
  • Guiding lower-ranked members
  • Providing strategic insight

Silence or disengagement weakens authority.

R4 represents leadership through visibility, knowledge, and responsibility. In a leadership position, R4 should set the example. This includes but is not limited to plundering within server 1813, shielding up when offline on buster day, and keeping a friendly environment.

If an R4 is unable or unwilling to meet these expectations, demotion may be considered. Demotion will not occur unilaterally. A formal review process will take place, requiring a 3/5 majority vote of the Title-Holding Leadership Members.

XIII.Training & Mentorship Delegation

Non-Title-Holding R4 leadership is responsible for helping develop members.

Responsibilities include:

  • Answering gameplay questions
  • Assisting with base development
  • Teaching event mechanics
  • Encouraging tech donations
  • Educating members on how to improve contribution

Leadership must actively provide value through knowledge-sharing and mentorship.

XIV. R3 Reform – Performance-Based Tier

R3 represents the alliance’s performance tier. Members at R3 and above remain eligible for Alliance Train rewards and other performance-based opportunities.

Rather than using a fixed requirement, the VS benchmark for R3 will be adjusted as needed to maintain a meaningful performance tier and ensure rewards are not diluted.

Current Baseline Goal:

  • ~20 million VS per week
  • ~6000 alliance tech donations per day
  • Minor flexibility allowed

If a large number of members consistently reach this level, the VS benchmark may be raised in increments of 5 million points to keep the R3 tier competitive and appropriately sized.

The goal is not to create rigid requirements, but to maintain R3 as a recognition tier for the alliance’s most consistent contributors.

XV. Reward Alignment

Event Rewards (if even available for distribution):

  • Distributed based on participation
  • Announced clearly in advance
  • Non-participants receive only automatic alliance rewards

Alliance Train:

  • Reserved for R3+
  • Not permanently guaranteed
  • Earned through performance

This encourages engagement without having to enforce it.

XVI. R1 & R2 Reform

R1 – New & Inactive Members
R1 is the starting tier for new members joining the alliance and for members who are currently inactive. All new members must remain in R1 for at least one full week of the VS event to allow leadership to evaluate participation and engagement.

After this period, promotion will be considered based on activity, contribution, and participation:

  • Daily active and members that contribute to alliance tech may be promoted to R2.

  • High-performing members who exceed expectations may be promoted directly to R3 at the discretion of leadership.

Members who remain inactive for extended periods may become eligible for removal to open space for more active players.

R2 – Active Contributors
R2 is designated for members who are daily active and meet basic contribution expectations, such as daily donations to alliance tech. R2 members contribute reliably to alliance tech but may not yet meet the standards required for R3.

This structure ensures that new and less active members are guided appropriately while maintaining space and opportunities for engaged players.

XVII. Alliance Tech Visibility

Alliance tech donations are foundational to growth.

We will:

  • Improve communication explaining alliance tech
  • Clarify the 6000 per day recommendation
  • Ensure members understand how contributions impact progress

Education replaces enforcement.

XVIII. Closing Statement

Our culture is our strength, but culture without structure does not scale.

This charter protects:

  • Our casual identity
  • Our competitive standing
  • Fair and transparent reward systems
  • Leadership accountability
  • Long-term stability

We will remain open.

We will remain competitive.

We will remain structured.

This framework defines how we grow without losing who we are.