{ "payload": { "appeal": null, "disclosure": { "privacyMode": "DELAYED_DISCLOSURE", "reasons": [ { "reason": "This gives Council members clear authority to take initiative on behalf of Renasca while establishing reasonable limits on what any individual member can decide alone. It allows the Council to operate more independently and makes Renasca less reliant on any one person to initiate discussions, outreach, or other Council activity.", "representative": "Mini | Minurva [CST]", "seatCode": "FOUNDER" }, { "reason": "Makes sense for increasing outreach. And sensible limits of authority to individuals.", "representative": "wizzz", "seatCode": "CHAIR-02" }, { "reason": "As council members and the main leading faces of Renasca, we will need the authority and limits added to that authority.", "representative": "Chocogen", "seatCode": "CHAIR-01" } ], "representatives": [ { "choice": "YEA", "representative": "Chocogen", "seatCode": "CHAIR-01", "seatName": "Chair 1" }, { "choice": "YEA", "representative": "wizzz", "seatCode": "CHAIR-02", "seatName": "Chair 02" }, { "choice": "NO_VOTE", "representative": null, "seatCode": "CHAIR-03", "seatName": "Chair 03" }, { "choice": "YEA", "representative": "Mini | Minurva [CST]", "seatCode": "FOUNDER", "seatName": "Founder" } ] }, "implementation": [], "proposal": { "category": "Ordinary policy", "contentHash": "ead3c111500c2efe03cbf3e332b1ac89b801f2987fbeb2a8d17fa05cf3c9db3d", "fullText": "I propose that individual members of the Renasca Council be authorized to act independently in matters that do not create policy, bind Renasca to an agreement, commit Renasca resources, or exercise authority assigned to another body.\n\n## Community Representation\nCouncil members may publicly identify themselves as members of the Renasca Council and represent Renasca in ordinary conversations with clans, leaders, community members, and organizations.\n\nThey may explain Renasca's purpose, structure, established policies, services, and current activities, provided they do not present their personal views as an official decision of the Council.\n\n## Outreach\nCouncil members may independently introduce Renasca to clans and other communities, invite participation, answer general questions, and begin discussions regarding potential involvement with Renasca.\n\nPrior Council approval is not required for ordinary outreach.\n\n## Community Consultation\nCouncil members may seek opinions, information, and feedback from people outside of the Council when considering matters relevant to Renasca.\n\nThey may bring that information before the Council and invite relevant individuals to contribute their knowledge or perspective to a discussion where appropriate.\n\n## Council Initiative\nAny Council member may independently raise an issue for Council discussion, request that an issue be considered, draft or introduce a proposal, suggest changes to existing policy, or request reconsideration of an issue through whatever procedures the Council has established.\n\nNo Council member requires sponsorship or approval from another member to initiate Council business.\n\n## Information and Questions\nCouncil members may request information reasonably necessary to understand matters before the Council or to perform their role.\n\nWhere information cannot be provided because of privacy, security, safety, or another established restriction, the reason for that restriction should be communicated where reasonably possible.\n\n## Public Communication\nCouncil members may discuss established Council decisions and publicly available information about Renasca.\n\nIndividual Council members may also express their own positions on matters before the Council, provided it is reasonably clear when they are speaking for themselves rather than communicating an official position of Renasca.\n\n## Limits of Individual Authority\nUnless separately authorized, an individual Council member may not:\n- Establish or alter Renasca policy.\n- Claim that their personal position represents a decision of the Council.\n- Enter Renasca into a binding agreement or partnership.\n- Promise approval, verification, recognition, special treatment, or another official outcome.\n- Commit Renasca funds, assets, development work, or other resources.\n-;Exercise authority assigned by policy to the Council as a whole, the Development Team, or another established position or body.\n- Disclose confidential, restricted, or private information obtained through their position.\n\nWhere an action would exceed the authority of an individual Council member, they remain free to bring the matter before the appropriate Renasca body for consideration.\n\n## Nature of this Authority\nThe authorities established by this proposal are permissions, not individual obligations.\n\nCouncil members are not required to exercise any particular authority granted by this policy, and failure to do so does not by itself constitute misconduct or grounds for removal.", "id": "cmsjqahh200ajtx3hrf6k7wn1", "number": "RCC-2026-0007", "rationale": "Members of the Renasca Council should be able to meaningfully participate in Renasca without needing permission to take ordinary actions associated with their position.\n\nClearly establishing individual authority gives Council members room to take initiative, communicate with the community, gather information, introduce ideas, and represent Renasca while maintaining clear boundaries around decisions that must be made collectively.\n\nThis also provides current and future Council members with a common understanding of where individual initiative ends and formal Renasca authority begins.", "requestedAction": "Establish the authorities and limitations described in the full proposal text as the general authority of individual members of the Renasca Council.", "state": "PASSED", "summary": "Establish the authority held by individual members of the Renasca Council and clarify which actions Council members may take independently without prior approval.", "title": "Authority of Council Members", "version": 1 }, "result": { "abstain": 0, "calculation": { "abstain": 0, "approvalDenominator": 3, "approvalNumerator": 3, "eligible": 4, "explanation": "The proposal passed. Quorum required 2 and 3 participated. The threshold was more Yea votes than Nay votes. The final count was 3 Yea, 0 Nay, and 0 Abstain (100.00% Yea among directional ballots).", "nay": 0, "noVote": 1, "outcome": "PASSED", "participation": 3, "quorumReached": true, "quorumRequired": 2, "recused": 0, "yea": 3 }, "eligible": 4, "explanation": "The proposal passed. Quorum required 2 and 3 participated. The threshold was more Yea votes than Nay votes. The final count was 3 Yea, 0 Nay, and 0 Abstain (100.00% Yea among directional ballots).", "id": "cmsl5ds8a00fjtx3jh7fo2xys", "nay": 0, "noVote": 1, "outcome": "PASSED", "quorumReached": true, "quorumRequired": 2, "recused": 0, "yea": 3 }, "schema": "renasca.public-governance-record.v1", "sourceCreatedAt": "2026-08-09T01:52:26.411Z", "timeline": [ { "at": "2026-08-08T02:02:12.086Z", "state": "DRAFT" }, { "at": "2026-08-08T02:02:22.634Z", "state": "SUBMITTED" }, { "at": "2026-08-08T02:02:22.686Z", "state": "DISCUSSION_OPEN" }, { "at": "2026-08-08T02:02:22.737Z", "state": "READY_FOR_VOTE" }, { "at": "2026-08-08T02:02:22.814Z", "state": "VOTING_OPEN" }, { "at": "2026-08-09T01:52:26.429Z", "state": "VOTING_CLOSED" }, { "at": "2026-08-09T01:52:26.437Z", "state": "PASSED" } ] }, "verification": { "algorithm": "Ed25519", "payloadHash": "5fac54b49561929b34cd23e07247fb0aed25b0faed226aced4e2798e91b4666c", "signature": "6LV4iEVNx6-i2swYI5zzeAVIb5cllqfdwk0dXz31v7P917ST1X8s1Es9klh4v8w1qHeZ_c0TjS6qUUMbiC-EBw", "signingKeyId": "renasca-records-2026-01" } }