# Governance

How Sruja is maintained and how decisions are made.

## Roles

- **Maintainers**: Have merge access, triage issues/PRs, and guide direction. They follow [PRINCIPLES.md](PRINCIPLES.md) and [SCOPE.md](docs/SCOPE.md) when accepting or declining changes.
- **Contributors**: Anyone who opens a PR or issue. We welcome contributions of all sizes; see [CONTRIBUTING.md](docs/CONTRIBUTING.md) and [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md).

## Decision-making

- **Code and docs**: Maintainers review PRs. Approval from at least one maintainer is required to merge. Disagreements are resolved by discussion; maintainers have final say within project scope.
- **Architecture and scope**: Significant changes (new surface area, breaking changes, or scope changes) are documented in [Architecture Decision Records (ADRs)](docs/adr/README.md). Propose an ADR for discussion before large implementation work.
- **Community**: Code of Conduct and contribution guidelines apply. Enforcement is described in [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md).

## Becoming a maintainer

Maintainers are added by existing maintainers based on sustained, high-quality contributions and alignment with project principles. There is no formal application; if you are interested, contribute regularly and discuss with current maintainers in Discussions.

## Transparency

- Roadmap and priorities are reflected in [PRINCIPLES.md](PRINCIPLES.md), [docs/SCOPE.md](docs/SCOPE.md), and [docs/DSL_ROADMAP.md](docs/DSL_ROADMAP.md).
- Security issues are handled privately (see [SECURITY.md](docs/SECURITY.md)); fixes are disclosed in releases and advisories as appropriate.
