{
  "payload": {
    "appeal": null,
    "disclosure": {
      "privacyMode": "DELAYED_DISCLOSURE",
      "reasons": [
        {
          "reason": "My Propsal",
          "representative": "Mini | Minurva [CST]",
          "seatCode": "FOUNDER"
        },
        {
          "reason": "Clear breakdown of registry staff duties and how galaxy placement will work.",
          "representative": "wizzz",
          "seatCode": "CHAIR-02"
        }
      ],
      "representatives": [
        {
          "choice": "NO_VOTE",
          "representative": null,
          "seatCode": "CHAIR-01",
          "seatName": "Chair 1"
        },
        {
          "choice": "YEA",
          "representative": "wizzz",
          "seatCode": "CHAIR-02",
          "seatName": "Chair 02"
        },
        {
          "choice": "YEA",
          "representative": "Mini | Minurva [CST]",
          "seatCode": "FOUNDER",
          "seatName": "Founder"
        }
      ]
    },
    "implementation": [],
    "proposal": {
      "category": "Ordinary policy",
      "contentHash": "2f11f427db4cad30823e962944d0c841616f5d41e05b77a0557e428d3a1a12da",
      "fullText": "**1. Division of Responsibility**\n\nThe **Council** establishes registry policy, application requirements, galaxy rules, appeals, exceptions, involuntary transfers, and major structural changes.\n\n**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.\n\n---\n\n**2. Clan Applications**\n\nRegistry Staff may accept clans that meet established requirements without Council approval.\n\nIf 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.\n\nPersonal opinions about a clan, its members, leadership, or reputation are not grounds for rejection.\n\n---\n\n**3. Galaxy Organization and Placement**\n\nGalaxies 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.\n\nExamples include swords, guns, hybrid combat, racing, sports, roleplay, social groups, casual or competitive environments, and mixed communities. These are examples, not fixed categories.\n\nRegistry 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.\n\nNo 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.**\n\n---\n\n**4. Transfers and New Galaxies**\n\nGalaxy identities may evolve over time. Moving galaxies is not a promotion or demotion.\n\nClans 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.\n\nStaff may recommend a move, but contested involuntary transfers go to the Council. Transfers may not be used as discipline.\n\nRegistry 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.\n\nRegistry Staff may recommend its purpose and initial population. The **Council retains authority to create, merge, retire, or substantially restructure galaxies.**\n\nVolunteers 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.\n\n---\n\n**5. Registry Staffing and Decisions**\n\nRegistry Staff may appoint new members by internal majority without a Council vote. No member gains greater authority through seniority or founding status.\n\nStaff 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.\n\nIndividual 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.\n\nSerious disputes, misconduct, conflicts, or abuse of authority may be referred to the Council.\n\n---\n\n**6. Conflicts and Appeals**\n\nRegistry Staff and Council members must recuse themselves from matters involving their own clan, a clan they represent, a personal dispute, or their own removal.\n\nClans 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.",
      "id": "cmste9xo4002ztx3h1xqa0ket",
      "number": "RCC-2026-0011",
      "rationale": "This will establish a clear, scalable process for accepting clans, organizing galaxies, and defining the authority of Registry Staff without requiring Council involvement in routine administrative decisions. It also gives galaxies room to develop distinct identities based on gameplay, community interests, competitiveness, or other meaningful differences while preserving Council oversight for major or disputed decisions.",
      "requestedAction": "Approve the following framework:\n\n1. The Council retains authority over registry policy, appeals, exceptions, involuntary transfers, and major galaxy structure.\n2. Registry Staff collectively manage routine clan applications, acceptance, galaxy placement, voluntary transfers, and registry administration.\n3. Registry Staff operate as equal members without a permanent head or superior position.\n4. Galaxies may be organized around gameplay style, community interests, forms of combat, event preferences, competitiveness, experience, or other meaningful characteristics.\n5. No single characteristic, including skill level, is required to define how galaxies are organized.\n6. Galaxy placement should remain flexible and should primarily serve the goal of creating active, compatible, and interesting communities.\n7. Registry Staff may appoint and remove members internally without requiring a routine Council vote.\n8. The Council retains oversight where staffing, registry decisions, or galaxy changes become disputed or exceptional.\n9. Creation, merger, retirement, or substantial restructuring of galaxies remains subject to Council approval.",
      "state": "PASSED",
      "summary": "As Renasca grows, the process for accepting clans, placing them into galaxies, managing Registry Staff, and dividing authority between the Registry and Council needs to be clearly established.\n\nThe goal of this proposal is to allow routine registry work to happen without requiring a Council vote for every decision, while still keeping major policy and structural authority with the Council.",
      "title": "Clan Registry, Galaxy Placement, and Administrative Authority",
      "version": 1
    },
    "result": {
      "abstain": 0,
      "calculation": {
        "abstain": 0,
        "approvalDenominator": 2,
        "approvalNumerator": 2,
        "eligible": 3,
        "explanation": "The proposal passed. Quorum required 2 and 2 participated. The threshold was more Yea votes than Nay votes. The final count was 2 Yea, 0 Nay, and 0 Abstain (100.00% Yea among directional ballots).",
        "nay": 0,
        "noVote": 1,
        "outcome": "PASSED",
        "participation": 2,
        "quorumReached": true,
        "quorumRequired": 2,
        "recused": 0,
        "yea": 2
      },
      "eligible": 3,
      "explanation": "The proposal passed. Quorum required 2 and 2 participated. The threshold was more Yea votes than Nay votes. The final count was 2 Yea, 0 Nay, and 0 Abstain (100.00% Yea among directional ballots).",
      "id": "cmstewvj4005stx3hmt62ftbn",
      "nay": 0,
      "noVote": 1,
      "outcome": "PASSED",
      "quorumReached": true,
      "quorumRequired": 2,
      "recused": 0,
      "yea": 2
    },
    "schema": "renasca.public-governance-record.v1",
    "sourceCreatedAt": "2026-08-14T20:41:23.104Z",
    "timeline": [
      {
        "at": "2026-08-14T20:23:32.788Z",
        "state": "DRAFT"
      },
      {
        "at": "2026-08-14T20:23:48.774Z",
        "state": "SUBMITTED"
      },
      {
        "at": "2026-08-14T20:23:48.822Z",
        "state": "DISCUSSION_OPEN"
      },
      {
        "at": "2026-08-14T20:23:48.871Z",
        "state": "READY_FOR_VOTE"
      },
      {
        "at": "2026-08-14T20:23:48.949Z",
        "state": "VOTING_OPEN"
      },
      {
        "at": "2026-08-14T20:41:23.122Z",
        "state": "VOTING_CLOSED"
      },
      {
        "at": "2026-08-14T20:41:23.131Z",
        "state": "PASSED"
      }
    ]
  },
  "verification": {
    "algorithm": "Ed25519",
    "payloadHash": "79d4ce5482c6e0e33005c20ca6d59a9d9859e7e252abba7098e9f93b359f7c87",
    "signature": "LJdDv4GEzoiUulbfCxHWOvGjSLs0OM871Mntn01TBtrSecHDQFOHZG-vJSsfX0DKUn7b0n4v58RmrYyt3nm2DA",
    "signingKeyId": "renasca-records-2026-01"
  }
}