Skip to content

Governance

The founding owner is the interim steward. Repository maintainers review work in their area; responsibilities should be listed as maintainers join. This is a practical starting arrangement, not a claim of an existing foundation or elected council.

Ordinary fixes use pull request review. Changes to repository boundaries, public formats/protocols, capability policy, licensing or irreversible data migration require an RFC. RFCs progress from proposed -> accepted -> implemented, or superseded/rejected. Accepted means a design decision; implemented requires linked evidence. RFC-0001–0009 are accepted, with implementation status recorded on each.

Allow at least seven calendar days for substantive public RFC feedback unless a documented security fix needs faster handling. The steward records the outcome, rationale and dissent in the RFC/PR. Seek one relevant maintainer review in addition to the steward once available; while there is only one maintainer, record the exception. For unresolved disagreement, prefer a reversible experiment behind an explicit unstable boundary.

Consistent contributions and constructive review can lead to a scoped maintainer invitation from the steward. Maintainers can step down without abandoning their work; document ownership transfer. Release owners publish compatibility notes, test evidence and license/provenance checks. No stable API or delivery date is implied by the roadmap.

Use the Contributor Covenant and organization security policy. The conduct contact is conduct@hyprune.com and the security contact is security@hyprune.com; both reach the project steward. Report vulnerabilities privately with GitHub’s Report a vulnerability button, which is enabled on core, shell, sdk, schema, worlds and hyprune (security policy). Never post sensitive reports in public issues. No personal address is published.

RFC-0001–0009 were accepted on 2026-10-09; each status line records how far it is implemented. The HUD-style amendment remains proposed. The repositories went public on 11 October 2026. Still open: confirm repository license choices and enable private vulnerability reporting on docs and .github. These are review items, not blockers for development.