Authority is divided among three branches.

The Top-10 Council is legislative: each alliance has one equal vote and the Council adopts server rules. The Top-3 Operations Council is executive: it coordinates urgent operations and implements adopted decisions, but cannot make permanent rules or judge disputes.

Both memberships are fixed for each five-week cycle, so a few days of ranking movement do not change the government. Proposed voting rules: 7 of 10 for quorum, a simple majority for ordinary decisions, and 7 of 10 for charter or city-system changes. Decisions and reasons are published.

Major conflicts between alliances go to an independent Court of five judges, nominated by NAP15 alliances and elected by the Top-10 Council for a fixed ten-week term.

A judge cannot simultaneously serve as a Top-10 voting delegate or Top-3 operator and must recuse when their alliance is involved. The Court checks evidence, hears both sides, applies written rules and orders proportionate remedies; it cannot legislate or control cities or the capital.

Judges cannot be removed for an unpopular decision.

Removal requires an 8-of-10 Council vote and is allowed only for proven inactivity, a concealed conflict of interest or serious misconduct, after the judge has a chance to answer.

The capital holder must name a primary and backup operator with a reliable PC and the technical ability to keep the clicker available around the clock. Readiness is checked before handover; if it fails, stewardship passes to the next qualified alliance without blame.

The clicker is shared server infrastructure, not a political entitlement. Its setup and handover must be documented. The published minister queue applies equally to every alliance, and the capital holder may never reorder it to favor its own members. Capital stewardship gives responsibility, not an extra council vote.

No alliance gains permanent rights from taking cities early or from holding a rank for only a few days. The city-rotation proposal is the working basis: complete connected chains, premium rotation for the Top 10, a training chain for ranks 11–15, and rankings fixed for each five-week cycle with Expedition Madness setting priority inside a group.

A fair 1×1 may happen only by mutual agreement and council approval; it cannot cancel an already published rotation. Existing borders remain until the first ratified cycle begins. Early holders and clicker operators deserve recorded recognition, but that contribution is not a permanent ownership claim.

Open the full city-rotation proposal →

NAP15 is a non-aggression pact among the current Top-15 alliances and protects their members; it does not automatically cover every S88 account. It forbids planned attacks, burning and robbery between protected members. “Robbery” means knowingly taking another protected member’s resources or rewards by attacking their base or resource tile, or by pillaging their Train or Special Ops. Only announced combat events and mutually agreed duels are exceptions.

A misclick or confusing event incident is not automatically a NAP15 violation: stop, report it and return or compensate losses where possible. Intent, scale and repetition matter. A personal dispute follows player → R4/R5; a major unresolved conflict between alliances goes to the Server Court. Retaliation and collective punishment are prohibited while a case is reviewed.

Participation in capital defense and cross-server attacks is expected, but nobody is punished automatically for one absence, a day off or real-life obligations. Contribution may be fighting, reinforcing, operating the clicker, coordinating or supplying resources. Only repeated alliance-level refusal after a clear written request may affect next-cycle priority, and only after Council review.