Governance

Garnet is small and this page says so. Pretending to have a foundation and a voting council would be the opposite of the project's stated values.

Who decides

Garnet is maintained by Island Development Crew (Jon Isaac, maintainer). Final decisions on language design, releases, and what merges are the maintainer's, exercised through the Island-Dev-Crew GitHub organization. There is no separate steering committee; claiming one would be fiction.

How a change lands

1. Work happens on a branch in a fork (e.g. Navigata1/garnet).
2. A pull request is opened against Island-Dev-Crew/garnet main.
3. It must pass the dogfood-readiness gate: local verification, evidence in the PR body, a Desktop evidence bundle, and explicit deferred/out-of-scope claims. The gate rejects unqualified production-completeness claims.
4. The maintainer (org-owner account) reviews and merges. CI and the readiness ledger must stay consistent.

Proposing larger changes RFC: PLANNED

A formal RFC process does not exist yet. Today, propose a significant change by opening a GitHub issue describing the problem, the proposed design, and the falsifiable evidence that would justify it. A lightweight written-RFC template is planned; this section will change when it is real, not before.

Conduct & security

Contribution is governed by the Code of Conduct. Security issues follow the disclosure path in SECURITY.md — not public issues.

Honest status

This is single-maintainer governance for a research-grade prototype. It is enough to evaluate the project's decision path; it is not a claim of institutional permanence. As contributors arrive, this document changes with the reality, not ahead of it.