Founder and Lead Developer Policy
Defines the Founder's permanent status within Renasca, the Lead Developer position, the Founder's place on the Council, and which powers attached to those positions may or may not be removed.
passedFull proposal
Minurv, myself, and here after refered to as the Founder is the original creator of Renasca. Founder is a permanent designation recognizing the creation and continued stewardship of the project. It is not an appointed position and cannot be removed, transferred, reassigned, or granted to another person. Founder status does not provide additional votes, a general veto, or authority to override the Council. Within Council proceedings, the Founder holds one permanent Council seat and one vote, equal to any other Council member unless separately holding an elected or appointed Council office. The Founder's permanent Council seat exists to ensure that the person ultimately responsible for Renasca's creation, technical continuity, and long-term maintenance cannot be separated entirely from its governance by a temporary Council majority. The Founder may still be recused from an individual matter involving a direct conflict of interest and remains subject to Council rules applicable to its members. The Lead Developer is responsible for Renasca's technical direction and for coordinating the Development Team. The Lead Developer has final technical authority over architecture, infrastructure, security, deployment, repositories, databases, APIs, first-party Renasca software, and other systems necessary to operate Renasca. The Lead Developer position is held by the Founder unless voluntarily resigned, transferred by the Founder, or the Founder is permanently unable to perform the role. Appointment of future Lead Developers does not grant Founder status or a permanent Council seat. The Council may remove administrative permissions, officer positions, moderation powers, access to confidential information, or other privileges that are not inherent to the Founder or Lead Developer positions when appropriate under Renasca policy. The Council cannot remove or transfer: - Founder status. - The Founder's permanent Council seat. - The Founder's single Council vote. - Ownership of personally owned code, assets, accounts, domains, infrastructure, or other property. - Recognition of the Founder as Renasca's creator. - Lead Developer authority while the Founder continues to hold that position, except for temporary restrictions necessary to address an immediate and credible security threat. These protections do not place the Founder above Renasca policy. The Founder remains accountable to the same rules governing conduct within the Council and community. They instead establish a boundary between powers granted by Renasca, which Renasca may withdraw, and rights arising from the Founder's permanent relationship to the project, which an ordinary political decision cannot erase. The Founder may voluntarily surrender any active authority associated with the Council or Development Team without surrendering historical Founder status. Any amendment that would alter the permanent rights established by this policy requires the Founder's consent in addition to the normal amendment process. This prevents the protections themselves from being indirectly removed simply by first amending the policy that guarantees them.
Requested action
Adopt this policy as the standing definition of the Founder and Lead Developer positions, establish the Founder as a permanent voting member of the Renasca Council, and distinguish removable organizational privileges from the permanent rights attached to Renasca's Founder.
Rationale
I want this policy in place so there is a clear boundary between my role as the person who created and maintains Renasca and the Council’s role in governing it. I do not want being Founder to give me unchecked control over the Council, but I also do not think a future Council majority should be able to remove me from the project I created or take away the authority I need to keep its technical systems running. Defining that now means these boundaries are based on written policy rather than personalities, assumptions, or whoever happens to hold the majority at the time.
Final tally
Representative record
| Representative | Seat | Vote |
|---|---|---|
| Chocogen | Chair 1 | yea |
| wizzz | Chair 02 | yea |
| Mini | Minurva [CST] | Founder | abstain |
Published vote reasons
Mini | Minurva [CST]
This sets my own policy.
wizzz
I think it is reasonable for the founder role to be a permanent position, as this helps preserve the original values, vision, and direction of Renasca while supporting its continued development. At the same time, the founder still remain accountable to Renasca policy.
Chocogen
If the founder is still held accountable to Renasca policy, then these are reasonable suggestions that I see being good for the long term.
Status history
DRAFT
2026-08-18T21:13:13.539Z
SUBMITTED
2026-08-18T21:13:35.380Z
DISCUSSION_OPEN
2026-08-18T21:13:35.495Z
READY_FOR_VOTE
2026-08-18T21:13:35.547Z
VOTING_OPEN
2026-08-18T21:28:54.020Z
VOTING_CLOSED
2026-08-20T02:24:00.522Z
PASSED
2026-08-20T02:24:00.531Z