# Governance

## Governance Model

Grinta currently follows a **maintainer-led** governance model.

- Day-to-day technical decisions are made by the lead maintainer.
- Community feedback is incorporated through issues and pull requests.
- Larger or breaking changes should be discussed in an issue before implementation.

## Decision Process

1. Open an issue describing the proposed change and motivation.
2. Gather feedback from contributors and maintainers.
3. The lead maintainer records the decision and rationale in the issue or PR.
4. Implement with tests and docs updates.

## Release Authority

The lead maintainer is responsible for:

- approving release candidates,
- tagging releases, and
- publishing distribution artifacts.

## Escalation

- **Security issues:** follow `SECURITY.md`.
- **Code of conduct concerns:** follow `CODE_OF_CONDUCT.md`.
- **Project support issues:** follow `SUPPORT.md`.
