# RCC-2026-0012: Founder and Lead Developer Policy

Outcome: **PASSED**

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.

---

Published: 2026-08-20T02:24:00.602Z

Payload SHA-256: `e7136bdf27a09c5e5d74fbb2a826560f4b5a4b0ee7d750b12cbd9e7e13d7d8f7`

Signing key: `renasca-records-2026-01`

Signature: `RcG1P7YVLfgqwIXdoEQfgqrqpFdtEqTGw7nR0FKY1o_Mx7Y4ZnUeISN_cvS5iQOJ7ZRMJK77jOiCv4b8wcVwBw`