{
  "payload": {
    "appeal": null,
    "disclosure": {
      "privacyMode": "DELAYED_DISCLOSURE",
      "reasons": [
        {
          "reason": "I called the proposal. ;-)",
          "representative": "Mini | Minurva [CST]",
          "seatCode": "FOUNDER"
        },
        {
          "reason": "Clans that we reach out to should reach these minimum requirements to be affiliated with Renasca. Should any clan not be up-to-date with them, then they can be informed post-haste",
          "representative": "Chocogen",
          "seatCode": "CHAIR-01"
        }
      ],
      "representatives": [
        {
          "choice": "YEA",
          "representative": "Chocogen",
          "seatCode": "CHAIR-01",
          "seatName": "Chair 1"
        },
        {
          "choice": "NO_VOTE",
          "representative": null,
          "seatCode": "CHAIR-02",
          "seatName": "Chair 02"
        },
        {
          "choice": "YEA",
          "representative": "Mini | Minurva [CST]",
          "seatCode": "FOUNDER",
          "seatName": "Founder"
        }
      ]
    },
    "implementation": [],
    "proposal": {
      "category": "Ordinary policy",
      "contentHash": "32eea88129055d2d83cf4977f7fd50b537892cdcf399e5aff814d05f0c188b51",
      "fullText": "## Requirements\n\nTo qualify for registration, a clan must:\n\n- Maintain an official Roblox group with at least 25 members.\n- Operate under a recognizable clan identity separate from any individual member.\n- Have an identifiable leadership structure with at least one person authorized to represent the clan.\n- Exist as an organized community with some form of meaningful activity, such as events, raids, defenses, training, roleplay, development, competitions, or other community participation.\n- Provide enough information for Renasca to reasonably verify the clan, its leadership, and the group being registered.\n- Be registered by, or with the authorization of, the clan's leadership.\n\nThe membership requirement must reasonably represent an actual community. Alternate accounts, artificially inflated membership, or other attempts to technically satisfy the requirement without an equivalent community may be disregarded.\n\n## Duplicate and Related Groups\n\nRenasca should ordinarily provide one registration per underlying clan.\n\nSeparate Roblox groups belonging to the same clan, including divisions, regiments, academies, development groups, or other subdivisions, do not automatically qualify for separate registrations.\n\nA related organization may receive its own registration where it genuinely operates as an independent clan with its own identity, membership, leadership, and community.\n\nLikewise, clans are not considered the same organization simply because they are allied, share members, or have overlapping leadership.\n\n## Rebrands, Transfers, and New Groups\n\nA legitimate clan should not become ineligible solely because it has recently rebranded, transferred to a new Roblox group, reorganized, merged, or otherwise changed how its community is represented.\n\nIn these cases, the clan's history, membership, leadership, and continuity may be considered rather than relying solely on the age or membership of its current group.\n\nNewly founded clans may also register once they genuinely meet the requirements of this policy. Creating a group and adding enough accounts to meet the numerical requirement does not by itself establish eligibility.\n\n## Inactive Clans\n\nTemporary inactivity does not automatically make a clan ineligible where the organization still reasonably exists.\n\nA group that has effectively ceased functioning as a clan, has no identifiable leadership, and no longer maintains a meaningful community may be subject to review under future registry policy.\n\n## Exceptions and Disputes\n\nThese requirements establish the normal minimum standard, but unusual cases may be brought before the Renasca Council for an exception.\n\nAn exception should only be approved where the applicant clearly represents a legitimate clan community and strict application of the requirements would conflict with the purpose of this policy.\n\nQuestions involving disputed leadership, competing claims to the same clan, suspected duplicate registrations, questionable membership, or other unclear circumstances may also be referred to the Council.\n\nUntil administration of the registry is formally established by separate policy, the Council retains final authority over disputed eligibility and exceptions.",
      "id": "cmspec3b000edtx3hp8lfh2kp",
      "number": "RCC-2026-0010",
      "rationale": "Renasca planets are intended to represent actual clans and communities. A defined minimum standard prevents individual players, empty groups, duplicate organizations, and groups created solely to claim a planet from occupying space intended for genuine communities, while leaving room for legitimate clans with unusual structures or histories.",
      "requestedAction": "Approve and adopt these Minimum Clan Registration Requirements as the standard for registering clans within Renasca.\n\nUpon passage:\n\n- Future registrations must meet these requirements unless an exception is approved by the Council.\n- Renasca may request reasonable information necessary to verify eligibility.\n- Duplicate, unauthorized, or clearly ineligible registrations may be rejected.\n- Disputed or unusual cases may be referred to the Council.\n- Existing registrations are not automatically revoked by passage of this proposal.\n- This proposal establishes eligibility requirements only and does not create or assign a registry management position.",
      "state": "PASSED",
      "summary": "Establish a minimum eligibility standard for clans seeking registration within Renasca. Registration is intended for real, organized communities rather than individual players, placeholder groups, personal projects, or groups created primarily to obtain a planet.",
      "title": "Clan Registration Eligibility Standard",
      "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": "cmspm1ylh001ftx3hr6ur9yi6",
      "nay": 0,
      "noVote": 1,
      "outcome": "PASSED",
      "quorumReached": true,
      "quorumRequired": 2,
      "recused": 0,
      "yea": 2
    },
    "schema": "renasca.public-governance-record.v1",
    "sourceCreatedAt": "2026-08-12T04:50:12.965Z",
    "timeline": [
      {
        "at": "2026-08-12T01:14:08.700Z",
        "state": "DRAFT"
      },
      {
        "at": "2026-08-12T01:14:26.127Z",
        "state": "SUBMITTED"
      },
      {
        "at": "2026-08-12T01:14:26.179Z",
        "state": "DISCUSSION_OPEN"
      },
      {
        "at": "2026-08-12T01:14:26.219Z",
        "state": "READY_FOR_VOTE"
      },
      {
        "at": "2026-08-12T01:14:26.277Z",
        "state": "VOTING_OPEN"
      },
      {
        "at": "2026-08-12T04:50:12.989Z",
        "state": "VOTING_CLOSED"
      },
      {
        "at": "2026-08-12T04:50:12.998Z",
        "state": "PASSED"
      }
    ]
  },
  "verification": {
    "algorithm": "Ed25519",
    "payloadHash": "5461e8ae4407b9be6a0b0c5bf762cec320f751f38cc5039b3031201d23ede19f",
    "signature": "7ClojqaQJ-mx8GUjs7EpUYUDHNjV4Wsf5N_QxtSbeO3VwPlhGbKw-3nLtD8Xr0KCGgJtjJ1DSN34USLiBWYfDw",
    "signingKeyId": "renasca-records-2026-01"
  }
}