# RCC-2026-0011: Clan Registry, Galaxy Placement, and Administrative Authority Outcome: **PASSED** **1. Division of Responsibility** The **Council** establishes registry policy, application requirements, galaxy rules, appeals, exceptions, involuntary transfers, and major structural changes. **Registry Staff** handle routine applications, acceptance, placement, transfers, and registry records. All Registry Staff are equal, with no permanent head. Routine matters do not require Council votes when policy is clear. --- **2. Clan Applications** Registry Staff may accept clans that meet established requirements without Council approval. If a clan does not qualify, staff should identify the unmet requirement and allow correction where possible. Exceptions, major disputes, or situations not covered by policy go to the Council. Personal opinions about a clan, its members, leadership, or reputation are not grounds for rejection. --- **3. Galaxy Organization and Placement** Galaxies should be distinct communities, not arbitrary containers. They may be organized around gameplay, combat style, event interests, community type, competitiveness, experience, or other shared traits. Examples include swords, guns, hybrid combat, racing, sports, roleplay, social groups, casual or competitive environments, and mixed communities. These are examples, not fixed categories. Registry Staff should place clans where they best fit while maintaining healthy populations. Factors may include gameplay, events, competitiveness, experience, relationships, activity, preference, capacity, and galaxy identity. No single factor determines placement. Skill may be considered where useful, but is only **one factor among many**. Clan preferences should be considered where practical. Placement should create useful communities, **not status or prestige.** --- **4. Transfers and New Galaxies** Galaxy identities may evolve over time. Moving galaxies is not a promotion or demotion. Clans may request transfers when another galaxy better suits their gameplay, interests, relationships, or community needs. Registry Staff may approve voluntary transfers where capacity and balance allow. Staff may recommend a move, but contested involuntary transfers go to the Council. Transfers may not be used as discipline. Registry Staff may recommend a new galaxy when capacity, community differences, poor compatibility, or growth justify one. A new galaxy should generally have **at least four clans expected at launch**, unless circumstances justify otherwise. Registry Staff may recommend its purpose and initial population. The **Council retains authority to create, merge, retire, or substantially restructure galaxies.** Volunteers should be sought first when clans need to move into a new galaxy. Clans may not be relocated simply because they are unpopular, inconvenient, or unwanted elsewhere. --- **5. Registry Staffing and Decisions** Registry Staff may appoint new members by internal majority without a Council vote. No member gains greater authority through seniority or founding status. Staff may remove members by majority for inactivity, failure to perform duties, repeated disregard for procedure, loss of access, or similar reasons. A member may not vote on their own removal. Individual staff may handle routine matters where policy is clear. If Registry Staff disagree and policy does not resolve the issue, it goes to the Council. Serious disputes, misconduct, conflicts, or abuse of authority may be referred to the Council. --- **6. Conflicts and Appeals** Registry Staff and Council members must recuse themselves from matters involving their own clan, a clan they represent, a personal dispute, or their own removal. Clans may appeal where policy was applied incorrectly, information was overlooked, a conflict influenced the decision, Registry Staff exceeded their authority, or exceptional circumstances require Council review. --- Published: 2026-08-14T20:41:23.184Z Payload SHA-256: `79d4ce5482c6e0e33005c20ca6d59a9d9859e7e252abba7098e9f93b359f7c87` Signing key: `renasca-records-2026-01` Signature: `LJdDv4GEzoiUulbfCxHWOvGjSLs0OM871Mntn01TBtrSecHDQFOHZG-vJSsfX0DKUn7b0n4v58RmrYyt3nm2DA`